My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 03/06/2003
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2003
>
Agenda - Planning Commission - 03/06/2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:30:21 AM
Creation date
6/4/2003 10:56:32 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
03/06/2003
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
219
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
i <br /> I <br /> I <br /> I <br /> I <br /> I <br /> I <br /> I' <br /> I <br /> I <br />I <br /> I <br /> <br /> I <br /> I <br /> I <br /> I <br /> I. <br /> <br />.(3) <br /> <br />(4) <br /> <br /> 3 <br />Front, rear and side yard building setback Regulations. <br /> Building setbacks from all property lines' which form the perimeter of the total <br /> property in the P.U.D. shall be planned to provide an acceptable transition <br /> between different land uses. No Planned Unit Development application shall be <br /> approved if it reduces building setbacks for the lots directly abutting existing <br /> residential neighborhoods. - <br /> <br />Building Height Regulations. <br /> Height limitations for any building in a P.U.D. shall be as shown on the approved' <br /> P.U.D. Plan. <br /> <br />Subd. 4. Building and Site Design, Construction and Maintenance Regulations. <br /> <br />(!) The overall appearance and compatibility of individual buildings to other site elements or <br /> to surrounding development will be given primary considerations in the review stages of <br /> the Planning Commission and City Council. <br /> <br />(2) <br /> <br />(3) <br /> <br />(4) <br /> <br />No building permit shall be granted for any building on land for which a plan for a P.U.D. <br />is in the process of review or which does not conform to the approved fina plan or for <br />one phase of the final plan. <br /> <br />Staging of Developments. <br /> <br />ao <br /> <br />Any P.U.D. Plan proposed to be constructed in stages shall include full details <br />relative thereto and the Planning Commission and City Council may approve or <br />modify where necessary any such proposals. <br /> <br />The staging shall include the sequence and the proposed time for beginning and <br />completion of each stage. Such sequence and/or schedule may be modified by <br />the Planning Commission and City Council~on the showing of good cause by the <br />developer. <br /> <br />Co <br /> <br />The land owner or developer shall make such easements, covenants and other <br />arrangements and shall furnish Such performance bond or bonds as may be <br />determined by the City Council to be reasonably required to assure performance <br />and completion of private streets and utilities, landscaping and privately owned <br />and maintained recreational facilities in accordance with the plan and to protect <br />the public interest. <br /> <br />Open Space. <br /> <br />A primary function of P.U.D. provisions is to provide developments which will <br />preserve and enhance the worthwhile, natural' terrain characteristics and not <br />force intense development to utilize all portions of a g~ven site. In evaluating <br />each individual proposal, the recognition of this objective will be a basic <br />consideration in granting approval or denial. <br /> <br />The public or private open space shall be consistent with the Comprehensive <br />Plan, Park and Trail System and with the stated purpose of preserving natural <br />site features. All open space shall be labeled on the P.U.D. Plan as to intended <br />use and ownership. <br /> <br />3 <br /> <br />37 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.