My WebLink
|
Help
|
About
|
Sign Out
Home
Search
05/08/2002 P&Z Packet
LinoLakes
>
Advisory Boards & Commissions
>
Planning & Zoning Board
>
Packets
>
2002
>
05/08/2002 P&Z Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/5/2014 3:38:34 PM
Creation date
6/5/2014 12:04:14 PM
Metadata
Fields
Template:
P&Z
P&Z Document Type
P&Z Packet
Meeting Date
05/08/2002
P&Z Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
59
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 />• <br />Planning & Zoning Board <br />April 10, 2002 <br />Page 11 <br />Staff explained the current status of the City's 2001 Comprehensive Plan and the <br />associated MUSA allocation prevented the City from moving forward with this <br />application. He stated, in addition, there were several preliminary plat issues that needed <br />to be resolved, including the review by Rice Creek Watershed District. <br />Staff recommended tabeling the action on the MUSA allocation, Rezoning, and <br />Preliminary Plat requests to obtain additional information and modifications as contained <br />in staff's report. <br />Ms. Lane asked how the Comprehensive Plan had this area zoned. Mr. Grochala replied <br />it was zoned Low Density sewered residential, and this plan met that zoning requirement. <br />Mr. Rafferty asked what MUSA meant and the importance f MUSA. Mr. Grochala <br />explained what MUSA meant and why it was <br />Chair Schaps asked why this project was outsides oratoriu . , - ,'Grochala stated <br />when the City Council was approving the mora u n <br />this develc�pia�'tent application had <br />been submitted that day. Council elected to ace' lications received as of <br />January 14, 2002 and therefore, this development was ai roved to come through. <br />Mr. Rafferty stated it appeared the Ano "o ® 4cern was regarding the speed <br />limit and the amount of additional traf e e would this development affect <br />the current residents in the area. <br />Gr -�ch. eph �HOne of the purposes of getting a <br />street through was to provide acce o the d ant to the east. He indicated by <br />providing the street at the parts k location rovide for two access points to a <br />future development. He stated fh wetlands might also create a problem for street access. <br />He indicated they at a�: He stated their major plan would be to put a <br />sign up indicatin;a goFs at some point in the future. He stated in the <br />past, the prob residents occurred when the residents did not know <br />that the road planned to go' gh. <br />Mr. Rafferty ask !as a con e pt to connect east Holly to west Holly. Mr. Grochala <br />replied it was a concern it would provide a good connection through the City. <br />He stated the problem wi h Street was that there was no other alternative road to <br />use. If east Holly and west 'Iolly were connected at some point in the future, this would <br />create another traffic alternative. <br />Mr. Corson asked if the Met Council wanted the future land plans be consistent with the <br />zoning, there would be no action taken for several months. Mr. Grochala stated this was <br />a decision they would have to make. He stated he was not comfortable at this time <br />making this kind of a decision. <br />Mr. Corson stated considering the land use plan had not been approved, they should not <br />be making any decision on this development until that issue had been resolved. <br />Mr. Corson asked who would take care of the wetland buffers signs. Mr. Grochala stated <br />that would need to be worked out with the developer. They would be responsible for the <br />installation and reseeding of the wetland areas. He stated the City would not replace <br />DRAFT MINUTES <br />
The URL can be used to link to this page
Your browser does not support the video tag.