My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
06-20-2005 Planning Commission Packet
Orono
>
Planning Commission
>
2005
>
06-20-2005 Planning Commission Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/4/2012 11:34:51 AM
Creation date
4/4/2012 11:34:28 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.
/
418
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
#OS-3112 <br /> May 16,2005 <br /> _ P1ge 7 of 8 <br /> Structur�►t Coverage <br /> Lastly, the applicant is requesting a strtictural coverage variance to permit 16.5% when <br /> 15% is normally allowed. The percentlge proposed is based on acceptance of the lot line <br /> rearrangement where 17% structur�l coverage would be proposed with no lot line <br /> rearrangement. The footprint proposed is 2,233 s.f-. which would meet 15%, however <br /> with the addition of the 230 s.f. deck, a variance is needed. StafF would recommend <br /> denial of this request as the house footprint can be reduced to allow for a deck. The <br /> existing struchu•al coverage level is conforming at 13.8%. <br /> I,OT�INE�ARRANG�iVIEN'T. __ _ _ _.. <br /> In an effort to construct an �ttachecl garage, the applicant has proposed a lot line <br /> rearrangeinent that would result in 393 s.f. of area being added to the applicant's lot and <br /> 389 s.f. of area is subtracted from 1190 Wildhurst Trail, which is the lot to the direct <br /> north. Staff has suggested that equal amounts of area be traded so that neither lot <br /> becomes more or less non-confortning in area than the othei• lot. This reinains staf�s <br /> reconunendation. <br /> An additional concern with the proposed lot line rearrangement is that the applicant's lot <br /> will be losing 2' of width at the lake where 140' is normally required and 56' would be <br /> proposed. The lot to the ilorth will be gaining 2' of lakeshore where a non-conforming <br /> width of approximately 57' ct�rrently exists. Staff would recommend that a <br /> rearrangement be explored whereby no lakeshore is traded, or equal arnounts are traded, <br /> as both widths are clirrently non-conforming. <br /> The rearrangement as proposed also results in an increase in 1190 Wildhurst Trail's 75'- <br /> 250' hardcover slightly. There are no variance records on file for this lot and staff would <br /> hesitate to reconunend that the City fornially grant a variance permitting almost 46% <br /> hardcover when 25% is normally allowed. <br /> Lastly, because a lot line rearrangement reql�est is considered a subdivision, staff would <br /> reconunend that a utility easement be obtained over the existing sewer line. A force main <br /> and gravity line run parallel to each other and an easement 20' centered over the two lines <br /> should be required. This includes both lots involved in the lot line rearrangement. The <br /> applicant should be questioned on whether 20' easements can be obtained over both lots. <br /> Obtaining a 20' easement centered over the line puts the southeast corner of the proposed <br /> lakeward addition within the easement. This should be revised as no new struct�ire <br /> should come within 10' of an existing sewer line. <br /> ISSUES FOR CONSIDERATION <br /> 1. Should this application be reviewed as a rebuild? <br /> 2. Can structural and hardcover reductions be attained? <br /> 3. Should the location of an existing structure that is being remodeled act �ts a hardship <br /> for locating new structure? rurther, could a more unobstructed front yard be attained <br /> if the applicant approached the project as � rebuild? <br /> 4. Should equal amounts of area �Zd width be traded so that no lot becomes more or less <br />
The URL can be used to link to this page
Your browser does not support the video tag.