My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2001 Planning Commission Packets
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Agenda Packets
>
2000-2009
>
2001
>
2001 Planning Commission Packets
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/29/2012 9:14:03 AM
Creation date
2/27/2012 4:13:01 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.
/
932
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
___ <br />i • <br />Mounds View Planning Commission <br />Regular Meeting <br />June 4, 2401 <br />Page 11 <br />Dave Tillmann, 5166 Longview Drive, stated he is across from Lot 3. He stated he walkeeo le <br />through the proposed properiy and his shoes were muddy from it. He didn't think many p p <br />would want to buy a home in 9 feet of dirt, then have it filled 5 feet higher. <br />Joseph Rivers, Woodale Drive, raised a concern about the quality of the roads in future years. <br />He stated that currently in the winter, the road resembles a wave due to the.�fill under the ., <br />blacktop. -' ". <br />;� <br />Mike Loregori, 28Q1 Woodale Drive, stated he shared the �Qncern�for the trees. He stated he � <br />understood theze was a sink hole on Woodale Drive, and that le� �iim to question what the fill <br />will be under the streets in this development. He stated he wqul�:l.ike to be assured it was going <br />to be done right. ��'` � ��� ' ' <br />t� <br />Directar Ericson stated the building engineer will be invol��d; The Rice =Creek V�atershed <br />District will also be involved as far as deterniinin��the �tn�act to the water,table; the <br />neighborhood and the drainage. Their engmeex s;�vi�l <br />impact to drainage, it won't be approved. Tlii�s plan <br />Watershed to move forward. The City Council will <br />does not approve it. <br />Director Ericson further explained the Rice <br />.� that is responsible for the oversiglit of this � <br />�:. <br />. Creek Watershed may, however, call in oth <br />Director, �ncson clanfied�ther� aie neighbc <br />suggested th�,` City�;learn wFien the Rice{ Cre <br />noted the piiblic �s a1�?vays welco:'�ne a�th�v <br />Richard Fomess,�51F7� <br />covenant,should be inc <br />the affecied owners. T <br />The�?City has a right to <br />of;�ie lot responsible. <br />Ericson <br />lots and <br />plan. If there is a negative <br />�ed b� �he Rice Creek <br />'he.Rice Creek Watershed <br />atershed,is tbe only local governxnental unit <br />They are not DNR-protected wetlands. Rice <br />es 'at some point. <br />i`�d meetings to keep the public informed. He <br />Watershed meets, and the inform the public. He <br />;:. �� �'�;�� °:'. <br />k�d �pak Dn�e; ;suggested if the development is allowed, a restrictive <br />,., � <br />z�1ed �liat contains a performance bond to help water proof basements o <br />e Git�zen:stated the developer is responsible for any changes that happen. <br />���t_��=r.est'rictive covenant an those lots, making the develoger and owner <br />�d the property is zoned properly. He added that stipulations could be put <br />be discussed to add to the developer agreement. <br />''F��' t�+ �i:::.$K >1T ��;-�V <br />`1�It� ��`ar���d s,'tated he does not want to affect properties negatively. His goal is to have a posihve <br />'effect �:`.He will have engineers working with the builders throughout ihe project. He will address <br />any questions as they come up. He stated that if this project is not going to work, then he will <br />not press the issue. <br />Director Ericson suggested the residents let their concerns be known to the Rice Creek <br />Watershed District either by writing letters or attending their meetings, which are open to the <br />-. _ � public. <br />
The URL can be used to link to this page
Your browser does not support the video tag.