My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 07/11/2007
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2007
>
Agenda - Planning Commission - 07/11/2007
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:41:53 AM
Creation date
7/5/2007 3:11:31 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
07/11/2007
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.
/
212
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
<br /> <br />All planned unit development districts should be recorded on the zoning map, and all documents associated with the planned <br />unit development, including the development plan, should by filed with a recordkeeping office in the land-use agency. These <br />documents should include agreements with other public agencies, sLlch as the highway agency, which may not be part of the <br />public record for the planned unit development. Computer and GIS programs can be installed that can organ!z:" and maintain <br />these documents. Staff must, however, provide overview and supervision if this system of monitoring is to be effective, <br /> <br />The following is an outline of a possible recordkeeping: <br /> <br />.. Assign each planned unit development a planning case number, create a project file, and place any documents relating to <br />the development in that file, <br /> <br />-$- Record all planned unit development districts on the zoning map, <br /> <br />... Fiie all documents associated with the planned unit development in a public recordkeeping office in the land-use agency <br /> <br />.. Record, to the extent possible, the final development plan and any associaTed documents, such as subdivision pial and <br />common open space documents, with the recorder's office so they will show up in the chain of title. <br /> <br />... Consider site plan review for developments within the planned unit development as thl?y occur. <br /> <br />. Monitor development of the project and do inspections through building, grading, and other permits for compliance with <br />the development plan and other requirements. <br /> <br />... InstaU a computar program to keep track of project development and relate it to building permits, <br /> <br />because this plan does not usually include <br />the engineering details for streets and other <br />facilities that are required by the subdivi- <br />sion ordinance. Many developers prefer not <br />to provide these details at this stage, and <br />prefer to deal with subdivision issues at a <br />later stage under the subdivision ordinance. <br />Engineering plans of this kind are expensive <br />to produce, and there may not be enough <br />commitment to the project even at the pre- <br />liminary development plan approval stage <br />to justify their preparation. <br /> <br />DEVELOPMENT AGREEMENTS <br />It is common in many areas for local govern- <br />ments to execute development agreements <br />with developers of planned unit develop- <br />ments, especially for master planned commu- <br />nities. There are a number of reasons for <br />doing this. One of the most important is that, <br />unlike a rezoning ordinance ora'development <br />plan, a development agreement establishes <br />obligations that cannot be modified unless <br />the agreement authorizes this. Another is that <br />the agreement can give the developer an enti- <br />tlement, or a vested right, to complete the <br />development under the land-use regulations <br />in effect at the time the development plan <br />was approved. Subsequent changes in the <br />regulations would not apply. The agreement <br />can also establish other obligations, includ- <br />ing developer exactions, allowable uses and <br />other project elements, the formation of spe- <br />cial districts to finance infrastructure, and the <br />preservation of natural resources. A develop- <br />ment agreement can be long-50 to 70 pages <br />or more. Coordination with provisions in the <br /> <br />122 <br /> <br />development plan and with conditions <br />attached to the rezoning, if any, is necessary. <br /> <br />DEVELOPMENT PlAN AMENDMENTS <br />Change is inevitable, and one ofthe most <br />important issues in the drafting of ordinances <br />for planned unit developments is to provide <br /> <br /> <br />authority for the amendment of development <br />plans. Changes in the market, or changes in <br />the developer's objectives for the develop- <br />ment,can require changes in an approved <br />plan. Change can also occur because neigh- <br />bors or residents who move in early in the <br />project may object to nonresidential develop- <br />mentthat was in the plan from the beginning <br />but which they believe is not compatible with <br />their residential living environment. <br />A restrictive approach to amendments <br />would limit them only to unforeseen <br />circumstances. This type of provision does not <br />allow for changes required by proposals to mod- <br />ify the development. The usual approach for an <br />,ordinance that authorizes this kind of change is <br />to distinguish between major changes, which <br />require new legislative action, and minor <br />changes that do not.An ordinance can simply <br />state that a change is major if it is "substantial," <br />or it can provide a list of changes and indicate <br />which are substantial and which are not. A <br />detailed listing is preferable because it removes <br />the need to exercise discretion on what is and <br />what is not "substantial," and provides pre- <br />dictability on what can and cannot be changed <br />and how such determinations will be made. <br />Minor changes can be approved administratively <br />by the planning director and staff, or they can be <br />approved by the planning commission. If <br />approval is required by the planning commission, <br />an application should be required but the com- <br />pleteness, notice, hearing, and decision proce- <br />dures need not apply, Chapter 10 of the <br />Legislative Guidebook has a provision in for <br />administrative review without a record hearing <br />that can be used for these decisions. <br /> <br />ZONINGPRACTlCE 6.07 <br />AMERICAN PLANNING ASSOCIATION I page 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.