My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
07-15-2002 Planning Packet
Orono
>
Planning Commission
>
2002
>
07-15-2002 Planning Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/16/2023 4:04:08 PM
Creation date
2/16/2023 4:00:05 PM
Metadata
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.
/
384
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).
Show annotations
View images
View plain text
II. Concept Plan Review Process <br />GOALS OF CONCEPT PLAN REV IEW <br />Planning Commission's concept plan review on July 15 should focus on both general and detail <br />aspects of the development plan. The developer has presented the City with a concept plan that <br />includes a level of detail which should allow Planning Commission to begin to visualize and <br />understand the various plan elements. <br />Planning Commission ’s goal should be to identify issues and concerns related to the Concept Plan, <br />and define for the applicants (and for the City Council) the positive and negative aspects of the plan. <br />It would then be appropriate to define a goal or intent for each aspect. These goals and should then <br />be discussed with the intended result that you provide specific direction to the applicant as to how <br />the issue should be resolved. <br />For example, in identifying issues, you might conclude that “the concept plan does not provide <br />adequate separation between buildings”. There might be a variety of functional and aesthetic reasons <br />for that conclusion, ranging from the need to provide sidewalks for adequate pedestrian access and <br />landscaping around the buildings, to the concept of maintaining an ‘open’ feel that is so central to <br />Orono ’s primarily rural character. In addressing these issues, the City needs to provide the developer <br />with clear direction as to how you expect the issue to be resolved. <br />Such direction could result in one of two actions: <br />revision and resubmittal of the concept plan to reflect all required changes, so that <br />the concept plan that is approved already incorporates the changes that have been <br />directed and is completely acceptable to the City; or <br />insertion of the direction into the concept plan approval resolution as a condition to <br />be met before the City will grant final development plan approval, such as “In order <br />to gain final development plan approval the developer shall provide a plan that shows <br />the separation between the two-story lownhome units at 25 feet rather than 10 feet”. <br />WHEN SHOULD CONCEPT PLAN APPROVAL BE GRANTED? <br />Staff and the applicant’s consultants have had some difference of opinion regarding at what level of <br />the review process concept plan approval should be granted. This is to some extent due to conflicting <br />wording and intent between the PUD and RPUD ordinances. The basic divergence of opinion is to <br />what extent the City has committed to the development upon granting of Concept Plan Approval. <br />Staff sees it as similar in scope to the preliminary plat approval, based on the wording of the PUD <br />ordinance (10.53) and discussions with the City’s planning consultants. 10.53 Subd. 8 clearly states <br />that the concept plan approval requires a public hearing by Planning Commission and a 4<'5 vote by <br />the Council. Contrast this with the classic subdivision sketch plan review, where no hearing is held <br />and no vote is taken. <br />#02-2789(Revisecl) Dahhtrom Development M.C <br />July 12, 2002 <br />Page 3 of 13
The URL can be used to link to this page
Your browser does not support the video tag.