My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-13-2020 Council Packet
Orono
>
City Council
>
2020
>
08-13-2020 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/1/2020 11:26:53 AM
Creation date
12/1/2020 11:21:26 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
170
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 PLANNING COMMISSION <br />Monday, June 15, 2020 <br />6:00 o’clock p.m. <br />_____________________________________________________________________________________ <br /> <br />Page 9 of 12 <br /> <br />Libby clarified that he should have said municipality of Orono. He asked, referencing the other <br />Commissioners’ recommendations, where the language came from. He noted the language was from <br />someone who felt there might have been a level of expertise at the City and that perhaps now the <br />language needs to be more general with authoritative expert opinions getting involved. <br /> <br />Barnhart said that part of the code is in place currently. The only change is removing “ash” from the list. <br /> <br />Libby asked if it was old code that has probably been around for a long time. <br /> <br />Barnhart said that is probably the case. He stated he would find a resource for appropriate street trees and <br />will work that into the next draft, because there may be trees that are appropriate in the Central Minnesota <br />region that are not appropriate in a street/right-of-way environment. For example, you don’t want <br />evergreens right next to the street to create vision issues. <br />Libby stated the DNR’s credentialed arborists are quite astute at making those recommendations. <br /> <br />Barnhart said he would find the reference and include it in the next draft. <br /> <br />Bollis commented that they should refer to the soil conditions on the site; for instance, an oak thrives in <br />sandy soil but is not going to work well in clay or black dirt. He has seen where they will put in 200 oaks <br />on a hillside in Orono and they die within the first year. <br /> <br />Libby noted a credentialed arborist would understand the soil combination. <br /> <br />Ressler stated, as far as having specific trees, if somebody plants a honey locust and it develops a disease, <br />then the City has to amend the text. If the City's code is simplified to have it redirected to someone that is <br />an expert that is going to be keeping up with the different species that can be added or subtracted, that is <br />something the Planning Commission can be mindful of. <br /> <br />Libby noted it can cost $4,000 to take down a cottonwood tree that has lived out its life expectancy to 90 <br />feet tall and is ready to come across the community’s power lines. <br /> <br />Ressler said he is not in favor of tabling the matter. The feedback provided has been documented and <br />hopefully useful for Barnhart and the City Attorney at their discretion for review at the Council. The <br />Planning Commission can leave it up to the Council if they deem it necessary to come back to the <br />Planning Commission. <br /> <br />Bollis referenced Line 1746 requiring additional frontage specifically for outlots or lots. <br /> <br />Barnhart stated lot frontage is measured for lake lots at the lakeshore and 75 feet back. That is how you <br />get to the lot width. There is no minimum requirement for that access on the public street, creating some <br />problems, notably at Casco Point. The language allows for 18 feet minimum. This is an eight-foot wide <br />driveway and five feet on either side, the minimum setback for hardcover in most residential zoning <br />districts. <br /> <br />Bollis asked whether the current minimum is nine or eight feet. <br />
The URL can be used to link to this page
Your browser does not support the video tag.