My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packet Cc - regular meeting 10/23/1989
Orono
>
City Council
>
1989
>
Agenda Packet Cc - regular meeting 10/23/1989
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/6/2025 10:14:45 AM
Creation date
8/1/2025 1:40:34 PM
Metadata
Fields
Template:
Administration
Admin Doc Type
Agenda Packet CC
Section
City Council
Subject
regular meeting
Document Date
10/23/1989
Retention Effective Date
8/1/2025
Retention
Permanent After File Date
Protection
Public
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.
/
547
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
Zoning File #1411 <br />September 1, 1989 <br />Page 6 of 9 <br />Please review Exhibit L, -he Dixon letter dated June 26, 1989 <br />Items 1 through 6. Staff feels that Items 1 through 3 and 5 and <br />6 have been answered by either staff or the applicant's <br />consultant. The issue raised in Item 4 deserves to be expanded <br />on. Many of the neighbors have expressed the same concern <br />"this has been a very dry period for the last few years and the <br />lake level is down 3 to 4 inches and i the developer providing <br />the appropriate drainage plan tLat ca., address drainage needs <br />during wet years". Calculations provided in the drainage plan <br />and in the drainage calculations submitted for the Watershed <br />District and the City Engineer's office deal with established <br />standards for areas at defined flood periods. Please note <br />that the drainage plan where detention ponds are defined show not <br />only the normal water elevation but a flood elevation. It is the <br />responsibility of the Minnehaha Creek Watershed District and the <br />City per its flood plain and wetlands ordinances to insure that <br />increased run-off resulting from development will not impact the <br />surrounding existing development with flooding during heaving <br />rains. The guidelines for such drainage reports are standards <br />established by Federal and State authorities and agencies. In <br />this specific review the 100 year and 1 year phenomena forr+at <br />was addressed. The proposed drainage plan will clearly function <br />without a negative impact in wetter years. <br />Please refer to Exhibit Q. A group of concerned neighbors have <br />submitted a 15 lot plat drafted by BRW for consideration. <br />Unfortunately, the City staff has no authority to review the <br />proposal as the current owner of the property has not given staff <br />permission. A representative or the neighbors may clearly <br />present this proposal to the developer, but once again staff has <br />no authority to address this proposal under the review of <br />application #1411 Sussex Square Development. The neighbors are <br />%elcome to contact the developer and if the developer wishes to <br />z.dopt any of the elements of the plan, that is the developers <br />option. Aj to the second issue, staff must once again remind <br />members we are not dealing with an LR District, this is a rural <br />residential subdivision and hardcover is not a consideration. I <br />advised the neighbors that very often the larger lots receive <br />more intense development. Staff does not understand the <br />statement that claims this area is particularily sensitive to <br />soil erosion and run-off because of the ponds and low areas. <br />Erosion usually takes place where there are extreme variations in <br />elevations. This is predominatly a moderate to flat area that <br />is under consideration for development. The presence of ponds or <br />ponding areas does not suggest erosion problems. I think the <br />third issue has been addressed by staff and the applicant. <br />
The URL can be used to link to this page
Your browser does not support the video tag.