My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03-28-1988 - Agenda Packet City Council - regular meeting
Orono
>
City Council
>
1988
>
03-28-1988 - Agenda Packet City Council - regular meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/12/2026 10:57:02 AM
Creation date
8/19/2025 11:35:28 AM
Metadata
Fields
Template:
Administration
Admin Doc Type
Agenda Packet City Council
Section
City Council
Subject
regular meeting
Document Date
3/28/1988
Retention Effective Date
8/19/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.
/
496
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 #11.223 <br />March 23, 1988 <br />Page 2 of 3 <br />D. The Planning Commission did not address approval or denial of the <br />method of piping roof drainage directly to the lakeshore bank in their <br />recommendation. <br />The majority of the Planning Commission generally felt that the <br />additional excavation to create a 3' deep cut extending to the foundation <br />wall was not appropriate. It was sugges=ed that a less extensive cut that <br />would blend with the grade to the property to the north might be <br />appropriate visually. The minority opinion was that since the impact on <br />lake water quality is neutral and that the visual impact with this method <br />was relatively minor, and that this method is supported by the Hennepin <br />Soil and Water Conservation District, that this was an approp-iate method. <br />Staff has noted in its memo of March 8th that from a technical <br />standpoint, the ultimate effect on lake water quality and run-off quality <br />is essentially neutral with this proposed method as compared to other <br />possible methods of bank restoration. The issue then comes down to one of <br />visual impact and general character of the shoreline. The majority of the <br />Planning Commission members present felt that the impact would be <br />significant, and they obviously felt: that the visual impact was a <br />significant issue. The visual impact issue is validated in the Community <br />Management Plan in the General Lane Use Policy No. 6 and Urban Land Use <br />Policy No. 13 (both appear on page 4 of the previously proposed denial <br />resolution), which discuss shoreland areas as "sensitive environmental <br />features with significant impact on . . . aesthetic values", and "espouse <br />limiting the impact of urbanization as visible from the lake." <br />Regarding the roof run-off question, you may recall that applicant has <br />extended a solid pipe from the outlet of his rain gutters to the edge of <br />the lake: pore bank, which is intended to remove the roof run-off from his <br />yard area and avoid a recurrence of the major erosion caused by saturation <br />of the soil at the top of the bank. From a technical standpoint there is <br />no reasonable way to measure the relative value of the reduced propensity <br />for soil to become saturated versus the reduction in run-off water quality <br />by not having it percolate through the flat yard area. From a policy <br />standpoint, it has been the City's philosophy that maximizing ground <br />infiltration of run-off waters will enhance lake water quality. However, <br />because applicant's roof run-off water did soak into the ground, his Lake- <br />shore bank slumped into the lake, having a negative impact on lake water <br />quality probably equivalent to many years of normal run-off carrying its <br />normal sediment lrad. Presuming whatever "pollutants" from the roof run- <br />off may have absorbed into the yard area over the years, some of them ended <br />up in the lake anyhow. <br />
The URL can be used to link to this page
Your browser does not support the video tag.