My WebLink
|
Help
|
About
|
Sign Out
Home
Search
01/21/2009 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2009
>
01/21/2009 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/20/2014 2:10:59 PM
Creation date
5/19/2014 1:51:53 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
01/21/2009
Council Meeting Type
Work Session Special
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
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
DRAFT <br />Growth Management Policy <br />In addition to the tools described above, the Comprehensive Plan Advisory Committee discussed <br />the development of a revised Growth Management Policy for the city. The Growth Management <br />Policy should provide a clear basis for efficient development staging as well as flexibility to <br />respond to market conditions. The new policy must work in conjunction with the staging plan to <br />establish the criteria for moving from one staging area to another. <br />The 2009 Growth Management Policy will include the following elements: <br />1. The City will create a fully integrated Comprehensive Plan and keep it up to date with <br />biannual reviews. The City will perform an intensive review at least once every five years to <br />ensure the plan addresses changing needs and conditions. <br />2. The Comprehensive Plan will include a staging plan defining development staging areas sized <br />to accommodate forecasted growth. <br />3. The City will monitor the l0rr staging areas and annually determine if adequate land <br />remains available. <br />4. All development must be located within the current 10-yrr staging area unless a <br />Comprehensive Plan amendment is approved that redefines the current 10-yr staging area. <br />5. All development must be phased within each 10 -yr staging area in accordance with the <br />staging plan unless the City Council determines, by resolution, to redefine the location of the <br />current 5 -yr phase. <br />6:6. Prior to reaching the time threshold for the next 10 -yr staging area, or 5 -yr phase within a <br />10 -yr staging area depicted on the staging plan, the City Council will determine by resolution <br />if the next area is to be opened to development. The following criteria will be used to <br />determine where and when to open up the next 10 -yr staging area, or 5 -yr phase within a <br />staging area, in accordance with the timing indicated on the staging plan: <br />a. Adequate infrastructure must be available to support development. Appropriate analysis <br />will determine if adequate infrastructure is available and what utility extensions and <br />transportation improvements are required to support new development. If infrastructure <br />is not available and cannot be made available in a timely manner to support expanding <br />into the next 10 -yr staging area or 5 -yr phase within a staging area, the city may refrain <br />from opening up the next staging area, or portions thereof. <br />b. Different areas of the city can be considered independently. A decision to open one area <br />of the city to development does not automatically open a different area of the city. <br />Decisions to open new areas to development should clearly define and map the area <br />being opened. <br />c. This process does not require a comprehensive plan amendment because it is in <br />accordance with the timing indicated on staging plan. <br />677,The following criteria will be used to determine if the city should allow a specific development <br />project to occur early in a j -yr staging area, or 5 -yr phase within a staging area, prior to the <br />timing indicated on the staging plan. <br />
The URL can be used to link to this page
Your browser does not support the video tag.