My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-12-2013 Council Packet
Orono
>
City Council
>
2013
>
08-12-2013 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/18/2019 2:23:18 PM
Creation date
4/7/2015 2:12:08 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.
/
576
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, July 22, 2013 <br />7:00 o’clock p.m. <br />_____________________________________________________________________________________ <br /> <br /> Page 15 of 20 <br />(10. CITY LAKE ACCESSES/FIRE LANES, Continued) <br /> <br />Bremer indicated she is aware of a fire lane where the adjoining property owner planted a number of very <br />small trees just along the fire lane, and when the property was sold not that long ago, the people who <br />purchased it found out that there lot was not as big as what it appeared to be. Bremer noted the City has <br />not decided to clean up the trees in that situation. Bremer stated the question then becomes how much <br />ownership should the City claim over them, which implies that the City would then assume the <br />responsibility of maintaining them. <br /> <br />Gaffron stated there are one or two fire lanes where they run down the middle of two homes and the <br />owners of those properties functionally have to utilize the fire lane. Gaffron stated the idea that people <br />can come through an area that is 15 feet wide between two homes is difficult for the property owners to <br />accept. <br /> <br />McMillan asked whether something should be included in resolutions when properties abut fire lanes. <br /> <br />Gaffron stated Staff has been looking at that. Gaffron stated when an application was submitted on Ivy <br />Place, the fire lane was looked at and the adjacent property owner was required to remove some of the <br />items that were placed in the fire lane. Another application on Highwood dealt with the rebuild of a <br />house, and while there were no private improvements located in the fire lane and it was very obvious that <br />people have been using the fire lane, the person had questions on how to keep them off their property. In <br />different situations the City has allowed the property owner to put vegetation or some other demarcation <br />along the area and in some situations the people maintain the fire lane as yard, which is usually fine with <br />the City. <br /> <br />Levang stated in her view at the time a survey is required, that would be a good time to mark the area. <br />Levang commented since each case is unique, a trigger point could perhaps be when a building permit is <br />applied for. <br /> <br />Gaffron stated that is one time Staff is focusing on and that there have been two or three applications <br />recently where there have been encroachments into the fire lane. <br /> <br />Anderson asked if the property owners are aware that there is a fire lane when they purchase the property. <br /> <br />Gaffron stated they should be and that the City has sent out notices to the property owners as well as <br />realtors informing them of the fire lane. <br /> <br />Levang stated that should be an automatic trigger. <br /> <br />Gaffron stated Staff is sometimes not made aware of the property being sold until after the sale is <br />completed. <br /> <br />Bremer stated quite a bit of this information is public information and that it is not necessarily the City’s <br />responsibility to notify the new property owners of the fire lane. <br /> <br /> <br /> <br /> <br />Item #03 - CC Agenda - 08/12/2013 <br />Approval of Council Minutes 07/22/2013 [Page 15 of 20]
The URL can be used to link to this page
Your browser does not support the video tag.