My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 12/07/2017
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2017
>
Agenda - Planning Commission - 12/07/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:29:18 AM
Creation date
12/28/2017 8:47:52 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
12/07/2017
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.
/
271
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
Superior St. <br />Erie Ct <br />EA 50'Setback <br />30'Setback <br />December 21 <br />Winter Solstice <br />that no toes are stepped on or barriers <br />created to an efficient workflow. Comparing <br />proposed processes to existing ones can <br />lead quickly to intuitive assessments of any <br />new regulations. The inclusion of something <br />like a completeness review process, for <br />instance, can come as a relief to staff who <br />may often find themselves in the position of <br />Ontario St. <br />attempting to assemble the missing pieces <br />needed to process an application. <br />Project Testing <br />Project testing is where it all comes together. <br />Whereas the previous types of testing primarily <br />involve specific tuning of regulations to ensure <br />they each achieve their specific intent, project <br />Camiros, Ltd. zoi7 <br />testing can help to ensure <br />that they work together <br />to create the type of <br />new development that a <br />community is looking for. <br />As such, it is a valuable <br />tool for communicating <br />the impact of such <br />regulations to a variety of <br />stakeholders, the public, <br />and elected officials. This <br />type of testing can be <br />very involved (essentially <br />executing hypothetical <br />projects under the <br />proposed regulations, from <br />design through application <br />and approval) or relatively <br />simple, depending <br />upon the desires of the <br />community and the time <br />�—•—� and capacity available <br />too zoo within a project scope. <br />The most common, <br />easily executed, and <br />helpful type of project <br />testing, however, is <br />a before -and -after <br />comparison of a <br />development or development type —what could <br />occur under the existing regulations versus <br />what could occur under new regulations. <br />Testing could be based on real or <br />hypothetical development: Do we want to <br />evaluate a real project against new regulations <br />to see how it may be different, or do we want <br />to create a hypothetical project and show the <br />impact of existing regulations versus new <br />regulations? Both avenues can be helpful in <br />communicating key changes between an old <br />ordinance and a new one, and the answer to <br />the real versus hypothetical question may <br />be different from community to community <br />based upon the desire or hesitancy to second- <br />guess or reevaluate existing development. <br />In cases where existing or "real -world" sites <br />are used to conduct testing, we must be <br />sensitive to the implicit difficulty in labeling <br />existing developments as either "good" or <br />"bad," and be sure to choose sites based on <br />quantitative characteristics or similarities <br />to other undeveloped locations, rather than <br />a qualitative judgment of a development as <br />something deserving of a "redo." <br />Project testing can be most helpful <br />to illustrate new regulations as they relate <br />ZONINGPRACTKCE 11.17 <br />AMERICAN PLANNING ASSOCIATION [page 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.