My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
05-18-2015 Planning Commission Packet
Orono
>
Planning Commission
>
2015
>
05-18-2015 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/12/2016 10:24:05 AM
Creation date
1/12/2016 10:23:25 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.
/
309
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
' ' 15-3720 <br /> ?9 March 2015 <br /> Pape 7 of 9 <br /> Lot 1, Block 3: The lot is shown to have 3.01 total acres and 2.85 dry, buildable acres in area. It <br /> is proposed to have appzoximately 220 feet of frontage on Hunter Drive where it wi11 gain <br /> access. It appears that all building setbacks could be met for a principal structure on this <br /> lot. Much of this lot is covered with established prairie vegeta.tion; there is a wetland on <br /> the eastern lot line. <br /> Applicant's Conservation Design Report Comments: Prairie grass preservation area <br /> over the first ISO'from the western boundary going east except for septic usage. 30' <br /> preservation from the eastern boundary for prairie also. Buffer trees are also to be <br /> planted by developer. Lot is accessed from Hunter Drive. <br /> Lot 2, Block 3: Like Lot 1, Block 3, this lot will front and gain access via Hunter Drive. It is <br /> shown to have approximately 270 feet in width and has 2.95 total acres of which 2.61 are <br /> dry. It also is currently primarily established prairie vegetation and has a wetland along the <br /> rear (east) lot line and along the south lot line. It appears that building setbacks can be met <br /> for a principal structure on this property. <br /> Applicant's Conservation Design Report Comments: Prarie grass preservation over the <br /> �rst I50'from the western boundary going east except for septic ptcrposes.Also a 40' <br /> southern boundary and a 30'easterly boundary shall be in place to further preserve <br /> the prarie. The developer is to plant trees to protect and preserve the valuable view <br /> corridor that's been enjoyed for S0+years.Access is from Hunter Drive. <br /> Road Layoat and Standards <br /> There aze two proposed private road comdors (Outlot E and Uutlot N') serving the proposed <br /> subdivision. Both are shown to be 50 feet in width. Both proposed roads are shown with a 100' <br /> diameter cul-de-sac as required by the Subdivision Ozdinance and the CMP for a local private <br /> road. The standard paved width for the road in Outivts E and F would be 24 feet with an 80 foot <br /> diameter paved cul-de-sac. Proposed Outlot F appears to require significant filli.ng&grading and <br /> has potential impact on the septic sifies for Lot 5. Total length of mad in Outlot F is abaut 1550', <br /> exceeding the code standard maximum length of lOQO'. The driveway to serve Lot 2 Block 2 <br /> adds an additional 604 feet. While applicant has suggested that use of the existing roadbed is <br /> desired, the minimum width for the entire road should be no less than 24 feet, as noted in the <br /> City Engineer's comments. <br /> The 30' access corridor shown for Lot 2 Block 1 would function as the access to the back lot. For <br /> Lot 2 Block 2 the access corridor has been widened to allaw for flexibility in driveway <br /> placement to avoid tree removal. <br /> Road Improvements and/or Easements Needed <br /> The City will require a Road, Drainage and Utilities Easement over the private roads. Standard <br /> perimeter drainage and utility easements will be required along all property boundaries in the <br /> plat as well as Conservation and Flowage Easements over any delineated wetlands and <br /> drainageways. <br />
The URL can be used to link to this page
Your browser does not support the video tag.