My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09-23-2019 Council Packet
Orono
>
City Council
>
1950-2024
>
2010-2019
>
2019
>
09-23-2019 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/30/2019 11:31:39 AM
Creation date
10/30/2019 11:29:01 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
179
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, September 9, 2019 <br />7:00 o’clock p.m. <br />_____________________________________________________________________________________ <br /> <br />Page 5 of 10 <br /> <br />Planning Commission. From the beginning the City Council has been pretty clear that they do not want <br />to make any major changes. <br /> <br />Walsh recommended keeping the existing language but adding the exception that the average lakeshore <br />setback line shall not go through the principal structure of the adjacent lot, and if it does, then the nearest <br />point that does not go through the adjacent lot shall be used as the starting point for the average lakeshore <br />setback line. When it goes through its own house, Staff has to find the next point where it does not go <br />through the house so it has a view that would be protected. <br /> <br />Walsh stated whenever the City adopts new codes, they do not always know if there will be issues with <br />certain lots. The Planning Commission recommended a few wholesale changes, but the Council would <br />like to just tweak that particular section. <br /> <br />Johnson stated he understood from the work session that they were going to leave it as is and deal with it <br />on a more one-to-one basis and that he was surprised by the changes recommended by the Planning <br />Commission. Johnson indicated he is in favor of keeping the code as is. Because it is a complex issue, <br />for the few times that it comes up, it is good for it to come before the City Council. <br /> <br />Walsh stated if they can tweak something that is obvious, it would eliminate the need to bring it before <br />the City Council. <br /> <br />Greg Hueler, 2715 Pence Lane, stated they were looking at the blue line, which was recommended by the <br />Planning Commission, and a lot of people are confused about Staff’s recommendation and the <br />recommendation of the Planning Commission. <br /> <br />Kelly Hueler asked if the Planning Commission voted and recommended this. <br /> <br />Seals stated they recommended the blue line. <br /> <br />Kelly Hueler stated one of the options showed their house, with the Dunkley project and the Vogstrom <br />project being highlighted. If you look at the blue line, their understanding was that it was basically saying <br />that if you do the average calculation between the Dunkley home, which exceeds the 75-foot setback and <br />is 29 feet from the lake, and their home, which is 100 feet of setback from the lake, the middle home <br />could come out closer to the lake. <br /> <br />Walsh stated the City Council is voting on their own option and not the recommendation of the Planning <br />Commission. <br /> <br />Hueler stated they have not heard these options. <br /> <br />Walsh stated he would never tell anyone they could put a house there. <br /> <br />Greg stated the way he understood the blue line, he would be able to move his house closer to the lake. <br /> <br />Walsh stated one of the reasons why it is discussed at the Planning Commission and work sessions is to <br />have these types of conversations and to look at different options. The City Council is not looking to <br />make wholesale changes to the ordinance, and it does not mean the City Council has to accept the <br />recommendation of the Planning Commission.
The URL can be used to link to this page
Your browser does not support the video tag.