My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-10-2015 Council Minutes
Orono
>
City Council
>
Minutes
>
2010-2019
>
2015
>
08-10-2015 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/1/2015 9:52:36 AM
Creation date
10/1/2015 9:51:31 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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, August 10, 2015 <br />7:00 o'clock pm. <br />7. #15-3763 CHRISTOPHER W. BOLLIS, 200-350 STUBBS BAY ROAD NORTH — <br />PRELEMINARY PLAT (continued) <br />McMillan stated her thought was to mitigate whatever infringes on the buffer. McMillan stated the City <br />could waive the 10 -foot requirement that the City has, but that will still not help them. McMillan stated <br />with a mound system, they will not really be planting buffer vegetation on there. <br />Rusty Olson, Septic Designer, stated there are many different types of grasses that the state says can be <br />planted in a buffer area and one of them is basically prairie grass. Olson stated that would be suitable in <br />this scenario. <br />Levang asked if he is amenable to speaking with the Watershed District about the buffer averaging. <br />Bollis stated he can look into that but that he is under the understanding that they meet the septic setbacks <br />of 50 feet for this project. Bollis stated he does not see anywhere in the Code where it says 85 feet. <br />Gaffron noted they are speaking of the Watershed District requirements and that he will need to obtain <br />their approval. <br />Bollis stated to his understanding their requirements are zero and that it can be within the buffer area. <br />Bollis indicated they are meeting state code at 0 and city code at 50. Bollis stated to his knowledge the <br />75 -foot buffer is for building and not septic. Bollis stated to his understanding they meet the Watershed <br />District's requirements since they allow them in buffers. <br />Gaffron asked if he has had discussions with the Watershed District about the plat in general from an <br />engineering standpoint. <br />Bollis indicated they have seen the plat. <br />Printup stated in this view this is one of the items that can be ironed out and tweaked further down the <br />road. Printup stated he is comfortable with that portion of the application but that he would like to learn <br />more about what the City requires and what the Watershed requires. Printup stated he is hearing that the <br />City does not require a 75 -foot setback and the Watershed District does not require that and so he would <br />like to error on the side of the homeowner. <br />Gaffron stated when the City gave up their authority relating to buffers, one of the things the City wanted <br />to accomplish was to avoid a situation like Stone Bay where the homes are built right up to the buffer <br />setback. The City wanted to have a 10 -foot setback to buffers for structures, wells, and septic systems. <br />The question then becomes whether the City is really concerned about meeting a 50 -foot setback or a <br />75 -foot buffer for a septic system. If the Watershed District does not prohibit having septic systems in a <br />buffer and simply requires a maintenance plan for the wetland and wetland buffer, it then becomes a <br />question of whether the City wants to have in their code that someone needs a greater setback. Gaffron <br />indicated he would be in favor of removing septic systems from the portion of the code that talks about a <br />50 -foot buffer plus ten feet. <br />Walsh stated they do not want to get buffers and setbacks confused and that this is a buffer. Walsh noted <br />the developer is meeting the setbacks. <br />Page 14 of 32 <br />
The URL can be used to link to this page
Your browser does not support the video tag.