My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-20-2018 Planning Commission Packet
Orono
>
Planning Commission
>
2018
>
08-20-2018 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/15/2020 8:45:39 AM
Creation date
1/15/2020 8:25:42 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
89
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
FILE # LA18-000068 <br />August 20, 2018 <br />Page 2 of 5 <br />As a sketch plan review, any comments or suggestions to the applicants are non-binding <br />but will be extremely helpful as the project moves forward. <br />Analysis <br />Frontage. The property does not have direct frontage on a public or private right of way; <br />the home on the point is accessed via a driveway through 1376 Baldur Park Road. It is <br />assumed an easement exists, a copy of this easement has not been provided. It will need <br />to be reviewed to ensure it does not prevent platting or the extension of utilities. Remedy: <br />Provide copy of easement. <br />Cul de sac length. Baldur Park Road is currently approximately 990 feet from its <br />intersection with Birch Lane (the maximum length is 1000 feet). Baldur Park Road ends <br />without a turn around or cul de sac. The lack of frontage onto Baldur Park road prevents a <br />cul de sac within Baldur Park Road right of way, unless additional right of way is platted <br />(and connection to Baldur Park Road established.) Recently, the city approved the Ivy <br />Place Plat; the developer there provided on site turnarounds and agreed to sprinkler the <br />buildings, in part to offset the challenges imposed by a long road ending in a dead end. <br />The commission should consider this factor in its' review of the plat. Remedy: Verify <br />connection to right of way, Provide cul de sac. <br />Land locked parcels. Secondly, platting the lot creates a lot, and because the parcels further <br />at the end of the point would be land locked, creates an "Easement Back Lot", which is <br />prohibited by Section 82-256 (c). Platting the project consistent with the City Code would <br />require the provision of a 30 foot wide access outlot, thereby establishing the home on the <br />point as a back lot, and the subject parcel as a front lot. Remedy: Provide 30 foot wide <br />outlot, adjust lot configuration accordingly. <br />Lot area. Chapter 82 of the City Code, in defining lot area, excludes public and private <br />rights-of-way, vehicular or pedestrian easements, surface areas below the ordinary high <br />water mark of any surface water ,wetlands or areas at or below the floodplain elevation <br />for a specific property), and have legal access to the building site without encroachment <br />of a wetland or floodplain area. The 0.5 acre parcel described will need to be adjusted to <br />accommodate access and or right of way/ outlots serving the lot at the point. The wetland/ <br />floodplain location may restrict the ability to plat the property without a waiver. Remedy: <br />Confirm location without encroaching into wetland or floodplain area, Adjust lot size <br />if necessary. <br />Conformity with the Orono 2030 Community Management Plan. Assuming modifications <br />to the lot size to accommodate access requirements and exclusions identified above, and <br />confirmation of the access question, the use and the density are consistent with the 2030 <br />Comprehensive Plan. <br />Site Grading. At this sketch plan stage no grading plans have been submitted. However, <br />to accommodate a home in the flood plain, grading will likely be necessary. A conditional <br />use permit will be required to permit that activity. Remedy: Develop grading plan, verify <br />floodplain impacts. <br />
The URL can be used to link to this page
Your browser does not support the video tag.