My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
05-29-2007 Council Packet
Orono
>
City Council
>
Agenda Packets - Historical
>
2000-2009
>
2007
>
05-29-2007 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/9/2015 2:16:54 PM
Creation date
4/9/2015 2:13:43 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
162
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
MINUTES OF THE <br />ORONO CITY COUNCIL MEETING <br />Monday, May 14, 2007 <br />7:00 o’clock p.m. <br />_____________________________________________________________________________________ <br /> <br />PAGE 2 <br /> <br />(Public Comments – Terry Johnson, Continued) <br /> <br />Murphy questioned whether this matter should be discussed with Staff rather than with the City Council. <br /> <br />Johnson indicated he did speak with Planner Curtis and a couple of the Council members. The first issue <br />deals with the overhang being 24 inches rather than 18 inches and that as a result, it encroaches into the <br />side yard setback. The 24-inch overhang has always been included on their plans from the beginning of <br />their application. The second issue relates to the stoop on the left side of the stairway, which goes out 19 <br />inches into the 10-foot setback. <br /> <br />Johnson stated they had the understanding that their building plans had been approved and that <br />they did not realize these two items were an issue until they went to apply for a building permit. Johnson <br />stated the overhang encroaches four to five inches. <br /> <br />Curtis stated the City allows 18 inches to extend into the setback to accommodate roof drainage and that <br />anything further than that must meet the setback. <br /> <br />Johnson reiterated that these two items have been included on all of their plans and was never brought up <br />as an issue. <br /> <br />McMillan inquired whether Staff reviews all of the tiny details of a building plan. <br /> <br />Curtis stated Staff does attempt to review all of the details of the plan and that it becomes difficult when <br />they have to review multiple reiterations of plans. Staff’s biggest concern with this property dealt with <br />the height of the home and the number of stories. Curtis stated there were no building plans attached to <br />the resolution because the plans were to be changed and that it was the understanding of Staff that once a <br />plan was approved for height, grading and the number of stories, they would bring that before the Council <br />if necessary. <br /> <br />McMillan stated it is her understanding that at the time the applicants obtain their variances, the <br />applicants are required to modify their plans to comply with the variances granted. <br /> <br />Curtis stated the building plans need to meet the requirements contained in the resolution. <br /> <br />Rahn inquired whether there is a legal encroachment with the stairway. <br /> <br />Curtis stated if it exits into the setback, it would be allowed. <br /> <br />Johnson stated they had the understanding that these were final plans and that they have not changed <br />since December. Johnson stated they have already ordered the materials and that the two-foot overhang is <br />more aesthetically pleasing and would help with potential mold issues. Johnson noted most other cities <br />allow a two-foot overhang. <br /> <br />Murphy stated shortening the overhang would also impact the pitch of the roof. <br /> <br />Bremer stated the overall height of the structure could be changed rather than the pitch of the roof. <br /> <br />Rahn stated two feet is a standard overhang. <br />Item #02 - CC Agenda - 05/29/07 <br />Approval of Council Minutes 05/14/07 [Page 2 of 27]
The URL can be used to link to this page
Your browser does not support the video tag.