My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03-09-1998 Council Packet
Orono
>
City Council
>
1998
>
03-09-1998 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/5/2024 1:59:00 PM
Creation date
6/5/2024 1:53:10 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.
/
407
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
r <br />Zoning File #2324 <br />January 13, 1998 <br />Page 4 <br />about 32% of the 75-250' zone. The creation of a conforming cul-de-sac actually would result in <br />more hardcover than the City's development standard for lakeshore lots. This impact could be <br />reduced by making the cul-de-sac diameter smaller, or eliminating it all together. The question then <br />is whether cul-de-sac is strictly necessary. The code would require such cul-de-sac for public safety <br />purposes primarily, i.e. for emergency vehicle ingress and egress, for ease of access for residents, <br />perhaps to provide additional neighborhood parking, and for ease of maintenance. However, without <br />the cul-de-sac the most distant home (Lot 1) would have a driveway 250' in length, which is not <br />extremely unusual in rural Orono, not as common in the urban area of the City. <br />The cul-de-sac likely would be desirable from a fire fighting staging standpoint. The public cul-de- <br />sac layout also eliminates the need for homeowners' association and concerns about road <br />maintenance. On the down side, though, such a large cul-de-sac will unquestionably change the <br />visual character of the immediate neighborhood, and if this is a public road, there may be concerns <br />about its use as a turnaround by boat trailer traffic when the Maxwell Bay access across the road is <br />full. If this is a public road, the City should not restrict its use by the public. If it becom.ee a private <br />road, the property owners would have greater control of its use in exchange for assuming <br />maintenance responsibility. <br />Staff Recommendation <br />The intent of this sketch plan review is to provide the applicant with direction as to what type and <br />magnitude of variances might be granted for development of this property, and to provide direction <br />regarding how the road access should oe developed. Staff recommends as follows: <br />1.Option C most clearly meets the City's standards for providing access to urban density <br />properties. Option C with a 24' private road with 80' diameter private cul-de-sac preserves <br />the emergency access needs at the expense of eating up slightly more hardcover, and limiting <br />the development capability of each lot due to hardcover. Making the cul-de-sac a private <br />road preserv es the property owners' rights to control the use of that road, especially given the <br />probable pressure on it by boating traffic. <br />2.Option A is less attractive from the public safety standpoint, but provides each lot somewhat <br />greater flexibility. Option A requires variances to the City's road standard (3 lots requires <br />a developed road) and also requires back lot area variances for Lots 1 and 2. Also. Lots 1 <br />and 2 would have somewhat less flexible building envelopes due to the 15' side setbacks <br />required because they are both back lots. The angle of the shoreline suggests that the houses <br />will also be angled as compared to the side lot lines. <br />3.Option B is the least attractive to staff because it forces the creation of a separate access <br />driveway onto the County Road for Lot 3. Lot! vnder Option B is still a backlot and subject <br />to the 15' side setbacks which limit the shape of any house to be developed. Lots ! 'd 2
The URL can be used to link to this page
Your browser does not support the video tag.