My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-27-2014 Council Packet
Orono
>
City Council
>
2014
>
01-27-2014 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/15/2015 4:44:55 PM
Creation date
4/6/2015 1:13:23 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.
/
369
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 1 <br /> #13-3637 <br /> January 24,2014 <br /> Page 2 <br /> l. A revised landscaping plan, indicating additional trees and screening along Willow Drive <br /> and along abutting property boundaries. <br /> 2. Draft covenants for protection of wetlands and woodlands, maintenance of stormwater <br /> facilities, etc. with an eye toward consolidating the conservation easements rather than <br /> having multiple or overlapping easements. <br /> 3. Conceptual floor plans and site plans for individual lots indicating how they might or <br /> might not fit a 15% lot coverage limitation (as a percentage of entire lot or just the dry <br /> contiguous area...). Show how the intended 3-car attached garages fit into these sites. <br /> Staff to consider options for defining lot coverage and/or massing limitations, with a goal <br /> of defining standards for all lots rather than for individual lots (example: "lesser of x s.f. <br /> or x %"). <br /> 4. Plan showing how rain gardens might be located in single lots rather than straddling lot <br /> lines. <br /> 5. Plan showing positive measures for protection of wetlands, tree areas, etc. during <br /> development and construction; i.e. barriers, fencing, signage, etc. <br /> Additional Information Received <br /> The applicant has provided the following additional information: <br /> - Lot-by-lot analysis of lot coverage percentages vs FAR - See Exhibit A(1) <br /> - Revised landscape plan showing additional buffering - See Exhibit A(4) <br /> - Revised grading plans depicting rain garden relocations - See Exhibits A(3) <br /> - Site protection narrative - See Exhibit A(2) <br /> -Narrative in response to neighbor comments - See Exhibit A(2) <br /> Additionally, staff received a comment letter on January 10 from adjacent neighbor Steve Kelley <br /> of 2340 Watertown Road (Exhibit B) with diagrams of some suggested revisions. The applicant <br /> has provided a response to those comments in Exhibit A(2). <br /> Lot Coverage Analysis <br /> Please review the lot analysis table provided by the applicant, Exhibit A(1). The intent of this <br /> analysis was to look at each lot in terms of massing potential, and establish a standard for how <br /> much house should be allowed. The lots range in area from 0.40 acre to 0.88 acre. Because the <br /> intent of a lot coverage standard is to limit the overall visual density, staff would suggest that <br /> � visual density is a function of the overall site, such that the entire lot area should be included in <br /> the analysis, not just the contiguous dry buildable. <br /> The developer has suggested the maximum size of 2-story house he intends for the site would be <br /> a 2,820 s.f. footprint including house/garage/deck/screen porch, translating to 5,180 s.f. floor <br /> area including finished interior spaces/basement/garage/screen porch. For ramblers, the potential <br /> maximum intended footprint expands to 3,820 s.f. and floor area goes up to 5,280 s.f. <br /> Based on the total lot areas, use of the RPUD standard 0.50 FAR (Floor Area Ratio) yields <br /> allowable floor areas ranging from 8,700 s.f. to 19,000+ s.f. Use of the 0.50 FAR for the <br /> development would potentially allow much larger homes than developer anticipates. Staff does <br /> not recommend use of the 0.50 FAR standard. <br />
The URL can be used to link to this page
Your browser does not support the video tag.