My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09-13-2004 Council Packet
Orono
>
City Council
>
1950-2024
>
2000-2009
>
2004
>
09-13-2004 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2023 1:14:58 PM
Creation date
1/25/2023 12:18:28 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.
/
212
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
1335 Tonktwt - Height Issue <br />September 2,2004 <br />Pages <br />2.In reviewing the proposed roof system, it became immediately clear that there are windows <br />and habitable spaces within the pyramidal roofsystem, along with a variety of sizes and shapes <br />ofdonners and incorporated gables. Using the policy we have consistently followed, the upper <br />measuring point was taken as a point halfway between the top of the upper level windows and <br />the peak. This yields an upper measuring point 9 ’ above the window edge and 9' below the peak, <br />at elevation 972.9. (See Attacbmeot F) <br />Height Calculation <br />The defined height then is the difference between the upper measuring point (972.9') and the lower <br />measuring point (936.3'). The defined height is then 972.9 - 936.3 = 36.6 ’, exceeding the 30' limit. <br />If the 939.5' low point is used, 972.9 - 939.5 ’ = 33.4'. hi cither case, the 30' height limit is exceeded <br />Applicant ’s Argument <br />The applicant is basically stating that because the City’s height measurement policy is not in ordinance or <br />resolution form, his architect was not aware of it, and it’s unfair that hi.s architect spent considerable time <br />and money designing a house in reliance upon his own interpretation of the code, winch design City staff <br />now find to be out of compliance with City requirements. Applicant requests that Council allow the height <br />measurement as depicted in Attachment B. <br />StafPs Response to Applicant ’s Argument <br />If we adhere strictly to the literal language of the ordinance, we should use the defined lower measuring <br />point based on existing grade (936.3') and the average height of the “highest gable ”. It is stafT s position <br />that the highest continuous gable must be reasonably considered as that gable on the nortli side of the house <br />that starts 26.4 feet below the peak, at elevation 955.5' (see Attachment G). The average height of that <br />gable is then 13.2 feet below the peak, at elevation 968.7'. The heiglit going strictlyby the Code definition <br />is then 968.7 ’ - 936.3 ’ = 32.4 ’. This still exceeds the allowed height by 2.4', and the peak will have <br />to he reduced by 4.8' in order to meet the 30'height limit. Staff does not agree with this method of <br />calculation, as it docs not match the long-standing policy, but it is presented to illustrate that even when the <br />policy is not used, the building height is non-compliant. <br />Options <br />Tlicre is no valid hardsliip to allow the excess height, in staff s opinion. Applicant has suggested changing <br />the peak to a ‘cupola ’ design, which might qualify for a Conditional Use Permit under Section 78-1 366 <br />if the Council concludes any negative impacts of the excess height can be suitably mitigated. Staff is very <br />reluctant to support such an application, based on a past history of fielding complaints by residents. Planning <br />Commissioners and Council members about excessive residential building heights in the City. <br />r
The URL can be used to link to this page
Your browser does not support the video tag.