My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-11-1988 - Agenda Packet City Council - regular meeting
Orono
>
City Council
>
1988
>
01-11-1988 - Agenda Packet City Council - regular meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/12/2026 10:57:01 AM
Creation date
8/12/2025 10:40:44 AM
Metadata
Fields
Template:
Administration
Admin Doc Type
Agenda Packet City Council
Section
City Council
Subject
regular meeting
Document Date
1/11/1988
Retention Effective Date
8/12/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.
/
398
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 #1223 <br />November 11, 1987 <br />Page 2 <br />3. Hardcover 0-75' Zone: <br />Existing - 1107 s.f. per applicants calculations (or 19.7%) <br />Proposed - Applicant proposes to remove the house portion <br />of the hardcover by installation of gutters and a sealed <br />pipe straight to the lake. He also proposes reducing the <br />area of steps to the lake as a result of the grading of a <br />portion of the bank. 'Additional hardcover proposed is a 165 <br />s.f. deck, and an additional 19 s.f. of steps through <br />retaining walls. Applicant suggests that this results in a <br />net removal of 700 s.f. of hardcover in the 0-75' zone <br />resulting in a final hardcover of 7.2%. <br />Staff would note that the direct transportation of roof <br />runoff water to the lake through a pipe is directly <br />contrary to the City's philosophy that all roof and other <br />hard surface runoff should travel over and through the <br />ground surface for filtration purposes prior to reacting the <br />lake. Under current City philosophy, applicant's proposal <br />merely lnc:reases the 0-75' hardcover from 19.7% to 22.1 % <br />calculated as follows: <br />834 <br />s.f. <br />of roof area <br />127 <br />s.f. <br />deck near the lake <br />43 <br />s.f. <br />concrete half circle <br />54 <br />s.f. <br />steps to the lake <br />164 <br />s.f. <br />deck prc p& s-vd <br />19 <br />s.f. <br />of stews through retaining Nall <br />1241 s.f. + 5625 s.f in 0-75' zone = 22.1% hardcover <br />Discussion - <br />Applicants situation is similar to many others around the lake <br />where steep lakeshore banks have suffered severed bank erosion <br />over the summer due to the "super storm". The City Engineer has <br />viewed this site and feels it is no different than any other <br />situation along the lake where steep banks have erodes'. Ile <br />states that there are numerous methods of repair to this <br />lakeshore bank that would not require grading out of a walkout <br />area for the house. I would ask ycu to read applicants letter of <br />request. I would also ask you to read the memorandum from the <br />Conservation District, and then ask you to read the City <br />Engineer's letter which recommends denial of the request to <br />create the walkout. Staff would note that the majority of <br />existing properties in the neighborhood have not created a <br />walkout by cutting down the lakeshore bank in the manner <br />proposes? An exception to this is the Backstrom residence at 1973 <br />Fagerness Point Road which was excavated out some years ago, <br />apparently prior to the 1975 adoption of current lakeshore <br />ordinances. <br />In addressing certain of the applicants concerns and hardships, <br />staff would note the following: <br />I. Staf f agrees that a system of vertical retaining wa 1 1 s <br />along the entire slope would be aestheticaliy less pleasing <br />from the lakeshore view than a grassy vegetated slope <br />without vertical retaining walls. <br />
The URL can be used to link to this page
Your browser does not support the video tag.