My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 1992/07/13
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
1990-1999
>
1992
>
Agenda Packets - 1992/07/13
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:48:59 PM
Creation date
7/17/2018 6:32:45 AM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
7/13/1992
Supplemental fields
City Council Document Type
City Council Packets
Date
7/13/1992
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
86
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
Mounds View City Council Page Seven <br /> "pular Meeting July 13, 1992 <br /> would make guarantees on behalf of mother nature. This development will not <br /> impact waterflow characteristics of this site one bit. This development <br /> provides more storage area. The watershed volume is increased, not <br /> decreased. <br /> Kay Weseman, 7807 Bona Road, stated she was very disappointed with the City <br /> as only four years ago the City had gone through the same action and that <br /> this proposal doesn't look significantly different, in her opinion, than the <br /> one rejected by the City Council in 1988, other than Harstad is asking for <br /> 13 lots instead of 17 or 18. Ms. Weseman stated that, in her opinion, this <br /> developer_has-not met the intent -of- the-ordinance at all. -Ms-. Neseladn <br /> stated her frustration that when persons went to the Planning Commission <br /> with concerns and nothing was done to respond to these concerns with this <br /> development, they weretreated with tokenisms and told that it was not their <br /> job to change the proposal. Ms. Weseman stated that this from the leader of <br /> the Planning Commission on down is reprehensible. Ms. Weseman found out <br /> that Peter Sabee was working with the developer in order that he could <br /> comply with the City's wetland ordinance. <br /> Kay Weseman asked how many times the public has to sign petitions and answer <br /> surveys that are paid for by the taxpayers money questions that we do not <br /> want to see wetlands encroached upon. Wetland boundaries should not be <br /> (banged. Do boundaries change over time? Are the boundaries the same as <br /> stand here now. Ms. Weseman asked if the boundaries had been resurveyed <br /> since 1987 to see if they are still in tact. <br /> Sabee, Barr Engineering, responded that the boundaries established in 1987 <br /> have not been resurveyed. Sabee further stated that if there is a <br /> significant change in watershed, such that on an average basis a lot more <br /> water was moving through this wetland a lot more often, a boundary could <br /> change. If some type of alteration were done within a wetland where a ditch <br /> outlet was constructed that could have an impact on the boundaries. Also, <br /> if the elevation were raised or lowered. The method of measuring the <br /> wetland by the Corps of Engineers is based on things or features in the <br /> field that donotchange rapidly such as communities of vegetation, soil <br /> markings indicating saturation, groundwater levels or water on top. <br /> Kay Weseman inquired about ditch cleaning and drought having a significant <br /> impact on the boundaries of the wetland if they had occurred previous to a <br /> site inspection. <br /> Sabee stated that drought would not change features that would be looked for <br /> in a vegetative community or in the soils. There would be a predominance of <br /> species but it would not change as rapidly. Perhaps it would not have a <br /> good season, but would still be there. <br /> Kay Weseman asked if it would change during a 10 year dry cycle in weather <br /> otterns. <br />
The URL can be used to link to this page
Your browser does not support the video tag.