My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
04-17-2017 Planning Commission Minutes
Orono
>
Agendas, Minutes & Packets
>
Planning Commission
>
Minutes
>
2010-2019
>
2017
>
04-17-2017 Planning Commission Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/18/2018 4:23:22 PM
Creation date
1/18/2018 4:23:14 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
48
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).
View images
View plain text
MINUTES OF THE <br /> ORONO PLANNING COMMISSION MEETING <br /> Monday,April 17,2017 <br /> 6:30 o'clock p.m. <br /> Larson stated in her opinion it would create more of an obstruction to the neighbor than it currently does. <br /> If the house is rotated, due to the low level of the site,the drainage that occurs on the northwest part of the <br /> site would be reduced and it would be harder to mitigate the water. <br /> Charles Fendlayer, Landscape Architect, noted the site is a very complex site and there have been a lot of <br /> issues with the complexity of how the house is situated on the property. Fendlayer stated this is basically <br /> an unbuildable lot. The highest point on the property is out towards the lakeside where there is the ridge <br /> at about the 100-year floodplain,which is where the previous home used to sit. Soil boring testing closer <br /> to the wetland has found peat and other unstable soils in that area. <br /> One of the main requirements and challenges was to mitigate stormwater onsite. Fendlayer noted they <br /> have been working with a civil engineering firm to create a stormwater management plan, which was one <br /> of the requirements from the Minnehaha Creek Watershed District. Approximately two-thirds of the site <br /> is located underneath the floodplain area and subject to flooding. The proposed design mitigates the same <br /> volume and then some over the requirements of the MCWD. The MCWD has reviewed the plan and <br /> have given a green light to proceed forward with the improvements. <br /> From a landscaping standpoint,the proposed house is set back from the previous proposal and further <br /> away from the western property to help maintain a natural outlet to Lake Minnetonka. The majority of <br /> the existing trees on the property will be maintained and additional trees will be planted on the property. <br /> The infiltration areas will essentially be one giant rain garden and a good portion of the site will be <br /> restored to become a natural meadow to help with mitigation. Fendlayer stated because a lot of the <br /> existing site is right at the water table level,there is not much infiltration currently but the prairie should <br /> help with that. <br /> Landgraver asked if one of the neighbors had concerns with vegetation. <br /> Fendlayer indicated they will be working with that neighbor to address their concerns with vegetation but <br /> the final plans for the site have not yet been finalized. <br /> Chair Thiesse opened the public hearing at 8:55 p.m. <br /> There were no public comments regarding this application. <br /> Chair Thiesse closed the public hearing at 8:55 p.m. <br /> Curtis read the following e-mail received from Christopher Jones: <br /> "To the Orono Planning Commission Members: <br /> I am responding to the Notice of public hearing regarding several properties that directly affect the Long <br /> lake and Lake Minnetonka watersheds, and therefore,the water quality of these watersheds. <br /> Specifically: 17-3918 seeks variances for lot area, lot width, lake setback, average lake setback, and a <br /> 0-75 foot hardcover variance. The details of this request is not included in the Public Notice so it is <br /> difficult to assess their individual impacts. <br /> Page 22 of 48 <br />
The URL can be used to link to this page
Your browser does not support the video tag.