My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
12-12-2005 Council Packet
Orono
>
City Council
>
2005
>
12-12-2005 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/12/2023 2:21:47 PM
Creation date
1/12/2023 1:59:26 PM
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.
/
302
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
MINUTES OF THE <br />ORONO PLANNING COMMISSION MEETING <br />Monday, July 18,2005 <br />6:00 o’clock p.m. <br />(#05-3131 Steve Bohl, Continued) <br />lots served by a new cul-de-sac road accessing to Willow Drive directly across from Elm Lane. Gaflron <br />noted a portion of the church prt^rty is located in the City of Long Lake but that all new residential lots <br />would be located in Orono. <br />This area is guided in the Orono 2000-2020 Community Management Plan for single-family residential <br />housing at a density of two to three units per acre. The area has never been rezoned to match the <br />Community Management Plan guided density and the application includes a request for rezoning. The <br />property is currently zoned RR-IB Single Family Rural Residential District, requiring a 2.0 dry buildable <br />acres per lot and a 200’ lot width. <br />Gafhron indicated the proposed SFR development for nine new homes has an average dry buildable lot <br />area of slightly over 15,000 square feet, with no new building lots less than 14,000 square feet as <br />reconanended by the Planning Commission at the sketch plan stage. This fits into the general range of lot <br />sizes in the surrounding neighboriiood. <br />The property contains wetlands at the south end, which would have to be protected by a Conservation and <br />Flowage Easement. Lot 9 and a small sliver of Lot 10 contain a small wetland that the developer <br />proposes to fill, with mitigation to occur on Lots 3,9,10, and 11 in order for Lot 9 to be viable. Gaflron <br />stated the City’s cun^t wetland moratorium, which expires in approximately one month, and in-process <br />ordinance changes may have some impact on how this wetland will be treated. The applicant is <br />investigating whether this fill/mitigation will be possible with the MCWD. Staff does have a concern <br />regarding die location of homes so near the proposed stormwater ponding on Lots 10 and 11. <br />Oaffion stated the proposed development is required to provide stormwater management systems <br />including ponding. Easements for the natural drainageway along the south end of the site will be <br />required. The entire property, including wetlands and the Williamson resident lot, will be subject to the <br />Storm Water and Drainage Trunk Fee established for 2005. The Planning Commission should decide <br />whether the church parcel and Lot 3 should be exempt from the Stormwater and Drainage Trunk Fee. <br />If this site is developer! under the RPUD standards, and depending on whether the road becomes public or <br />private, it may be appropriate to place the wetlands and ponds into a community owned outlot, which <br />would have an impact on the gross lot area for Lots 9,10, and 11. <br />Gaflron stated at the sketch plan review the Planning Commission concluded that the RPUD standards for <br />SFR development are generally appropriate for this site, with a few minor revisions. The RPUD <br />standards are sununarized as follows: <br />I.A 15,000 square foot minimum dry buildable lot area. The Planning Corrunission had indicated <br />that a 14,0(W square foot minimum was acceptable. <br />2.A 90-foot minimum lot width at the sedmek line. All nine new lots do meet this using a 30-foot <br />street setback. <br />PAGE 19 <br />ll <br />1
The URL can be used to link to this page
Your browser does not support the video tag.