My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09-15-1997 Planning Packet
Orono
>
Planning Commission
>
1997
>
09-15-1997 Planning Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/6/2023 10:10:36 AM
Creation date
9/6/2023 10:01:59 AM
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.
/
476
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
Planning Commissioners/August 14, l997/p.2 <br />Both t mcs we have come before the Planning Commission (1991 and now), Lyman <br />Avenue seems to be to major point of concern Feelings range from “slightly <br />uncomfortable to highly hostile ” to the road we all call home. With that in mind, we tried <br />to do what we could, within our property limits to alleviate some of the concerns. We <br />moved the drive into the property (Outlot B) to the w est side of the property, which <br />allow s most of the new traffic to have direct access to the public right-of-way on Lyman <br />and rot onto the private road. The outlot includes a cul-de-sac which both staff and <br />Planning Comi^ission Members wanted for ease of turn-around for fire trucks and plowing <br />equipment .Another cul-de-sac could be created at the end of Lyman when the <br />Depirtment of Transportation takes one of the houses at the end for the Highway 12 <br />upg' ade. Three quarters of the land needed for that cul-de-sac at the end of Lyman has <br />already been dedicated <br />To comply with your concerns about the w idth of L>-man, we are dedicating a portion of <br />our property (Outlot A) to allow space to widen Lyman Avenue, and without a need to <br />piece any additional fill to the southeast side of the road. This will allow some flattening <br />of the famous curve and improve sight lines. Bonestroo, Rosene, Anderlik & Associates <br />stated in their report on the subdivision (June 11, 1997) that “a 20-foot paved surface may <br />bt: an acceptable access.” VVidening Lyman will take away concerns about the access to <br />a-id from Lot 4 "^he sewer project will allow an opportunity to both build the sewer and <br />upgrade Lyman tfom Smith (now 12-15 feet wide in the public part of the road) and then <br />assess the benefiting property owners <br />Unfortunately, complying with your request to provide a cul-de-sac within the property <br />and load new traffic on the public part of Lyman (Outlot B) eliminates the second septic <br />system site for lot 4 The site that meets Orono ’s septic system design requirements is <br />under the cul-de-sac We are hoping that you will take into consideration the fact that we <br />are trying to do those things that will alleviate your concerns for safety on Lyman and that <br />you will grant us Lot 4 as a buildable lot with only one septic site, knowing that public <br />sewer will abut that lot within one or two years and be available for hookup should the <br />primary system fail. <br />Someone raised the question about our current house being ser.ed by a driveway not <br />entirely on our property. We do have a formal easement across the property we do not <br />own for the existing driveway, signed and registered with Hennepin County, as Document <br />#1203061, which was filed on Decemb**r 15, 1976. Although the driveway could be <br />moved onto our property and we have shown this design on the proposal, it will <br />necessitate the removal of a large number of large trees It has existed for 30 years in its <br />current spot without any traffic incidents at its egress. The vacated driveway would be a <br />large scar in the landscape for many years to come. 1 hope some of you will have the <br />chance to look at the two locations and then decide the best approach.
The URL can be used to link to this page
Your browser does not support the video tag.