My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
RPUD Ordinance Final Draft for Adoption
Orono
>
Property Files
>
Street Address
>
W
>
Wayzata Boulevard West
>
2040 Wayzata Boulevard West - 34-118-23-21-0036 - (Orono HRA)
>
Land Use
>
2040 Wayzata Blvd Land Use - Dunbar
>
Staff Memos & Correspondence - File Cabinet 1
>
RPUD Ordinance Final Draft for Adoption
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/22/2023 4:55:48 PM
Creation date
10/7/2021 10:18:08 AM
Metadata
Fields
Template:
x Address Old
House Number
2040
Street Name
Wayzata
Street Type
Boulevard
Street Direction
West
Address
2040 Wayzata Boulevard West
Document Type
Land Use
PIN
3411823210036
Supplemental fields
ProcessedPID
Updated
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
29
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
To: Mayor Peterson and Councilmembers <br /> Ron Moorse, City Administrator <br /> From: Mike Galion, Planning Director <br /> Date: February 23, 2001 <br /> Subject: #2631 RPUD Ordinance Final Draft for Adoption <br /> List of Exhibits <br /> A - Final Ordinance Draft in Adoption Format <br /> B - Summary Ordinance for Publication <br /> Council tabled this item on February 12 for additional review at the February 22 work session. <br /> Councilmembers had a few concerns regarding applicability of the RPUD District to Shoreland <br /> properties, and about the potential RPUD impact on future development in the City. These were <br /> reviewed in the memo of February 16 which was discussed at the work session. Councilmember <br /> Flint also suggested some relatively minor changes which were incorporated into a 6"'draft that was <br /> distributed at the work session. As a result of the discussions, since the February 12 version the <br /> ordinance has been revised as follows: <br /> 1. Subd. 5(A)2 on Page 3: 5-acre Minimum. For the second potential finding which would <br /> allow Council to allow RPUD zoning for a parcel of less than 5 acres, "public street" has <br /> been substituted for"right-of-way"in terms of defining adjacency to an existing RPUD zone. <br /> 2. Subd. 5(A) on Page 3: Shoreland Applicability. Council concluded that no property nor <br /> portion of a property within 250' of the shoreline of a protected lake or tributary may be <br /> rezoned to RPUD. The language has been revised to allow RPRD development within the <br /> Shoreland District but not within 250' of the shoreline. <br /> 3. Subd. 5(E) on Page 4: Incentives. The language allowing the use of incentives for <br /> affordable and moderate cost housing has been revised to require a 20-year assurance rather <br /> than merely a "specific period of time" for keeping units affordable. <br /> 4. Subd. 5(F) on Page 5: Hardsurface. Maximum hardsurface coverage for a"High-density <br /> residential" (>6 units per acre)RPUD site has been reduced from 70%to 50%,matching the <br /> standard for low/medium density residential(the senior housing site plan is currently at about <br /> 45% and may end up slightly lower depending on final road configuration). <br /> 5. Subd. 5(G)2 on Page 6 and Subd 5(H)8 on Page 7: Height of Buildings. The height <br /> standard language has been revised to omit the 2-1/2 story requirement, since the language <br /> "30 feet or 2-1/2 stories"was confusing and difficult to interpret. For multi-family buildings <br /> {Subd. 5(G)6} the height standard will be 30 feet, but for properties currently zoned or <br /> guided in the CMiP for commercial use, height may exceed 30 feet but may not exceed 3 <br /> stories. For single-family uses in RPUD {Subd. 5(H)8}, building height will be limited to <br /> 30 feet.Note:Staff will be proposing a similar Code change to the height standard for all other <br /> districts in the near future! <br />
The URL can be used to link to this page
Your browser does not support the video tag.