My WebLink
|
Help
|
About
|
Sign Out
Home
2015_1116_CCpacket
Roseville
>
City Council
>
City Council Meeting Packets
>
2015
>
2015_1116_CCpacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/21/2015 3:07:16 PM
Creation date
11/12/2015 4:19:40 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.
/
300
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).
View images
View plain text
Attachment B <br />49 Mr. Rehder responded that any species could be multi-stemmed and required a method to calculate their <br />50 DBH, using Boxelder Trees cut down multiple times as an example that would require a protection zone. <br />51 Mr. Rehder stated that this language attempted to address anomalies with multi-stem trees, clarifying <br />52 that if a single trunk was large enough, it would still fall into the heritage tree category and have potential <br />53 as a preservation tree providing justification for doing so. <br />54 Page 1, line 22-25, Member Bull referenced examples of trees with 4" caliper inch being not measured, <br />55 questioning therefore if anything under 6" would be considered or rated as one 12" tree. <br />56 Along those same lines, Member Cunningham further questioned if the main tree trunk is at breast <br />57 height and then splits after that, would it still be considered one tree. <br />58 Mr. Rehder responded affirmatively, that the height would typically be used (above breast height). Mr. <br />59 Rehder further noted that generally multi-tem trees already had a strike against them depending on <br />60 whether or not trunks were pushing together, as they were considered not ideal trees, and would be <br />61 difficult to consider as a heritage tree if they already had a pre-existing condition making them non- <br />62 preferred heritage trees. <br />63 Member Daire cited an example of a tree immediately outside his property that had split into two <br />64 branches (e.g. monkey-stemmed tree) and had done that split at a height of approximately 52" — 54" and <br />65 questioned where the measurement would start in that case or what variables applied. <br />66 Mr. Rehder responded that, while it may depend on who measured it as there were different <br />67 approaches, as an example with an Oak tree at 26" that may be found in the development process, it <br />68 would be worthy of preservation, even though it may stick out as not in the heritage category, but an <br />69 effort should be made to preserve it. <br />70 Member Daire opined that language should be added that before removal, it would be necessary to have <br />71 a recommendation from a certified forester or arborist as to whether a tree should be preserved or <br />72 definition of which breast height diameter is appropriate. <br />73 Mr. Rehder noted it is often a judgment call made in the field and often dependent on the overall <br />74 inventory of a site. <br />75 Page 1, line 28, Chair Boguszewski suggested adding language Bogus to the first sentence to read, <br />76 "...4.5' (54") above the ground(� �or as determined by a certified arborist.]" <br />77 As referenced by Chair Boguszewski as to a trigger, Page 3, lines 83 — 93, Mr. Gozola noted that staff <br />78 had recommended language triggered by application for a building, demolition or grading permit, or for <br />79 platting or any lot division not qualifying as a minor lot subdivision, allowing staff the ability to address <br />80 any private property owners attempting to skirt the issue and not abide by the parameters of the tree <br />81 ordinance in removing more trees than would be allowed. <br />82 Further reference was made to line 94 specific to any other attempt to remove a significant number of <br />83 trees before applying for a permit, and recourse available for the City and/or homeowners. Discussion <br />84 ensued related to potential issues, criminal activity reported to the Police Department as applicable if <br />85 trees were removed from a neighboring property, and reasonable explanations versus blatant attempts <br />86 to circumvent regulations. <br />87 Even with Member Bull noting that an appeal process in place, Member Murphy expressed concern that <br />88 language in line 94 needed to be strengthened. <br />89 Mr. Gozola noted lines 97-98 attempted to address that, and suggested aerial photography was one <br />90 source from around the metropolitan area that could be used to compare previous and existing tree <br />91 coverage on a site if needed for evidentiary information. <br />92 At the request of Chair Boguszewski, City Planner Paschke confirmed that the Variance Board process <br />93 could come into play in some cases, but if staff administratively determined a variance was not <br />94 supported based on hardship criteria, a property owner still had the appeal process for the City Council <br />95 against that administrative decision. <br />96 Page 3, line 92, Member Bull asked if that was intended to be "cubic" rather than "square" feet; with Mr. <br />97 Gozola advising that after consultation with staff, that had been taken from existing ordinance language. <br />98 Community Development Director Paul Bilotta suggested that language could be modified if so desired. <br />
The URL can be used to link to this page
Your browser does not support the video tag.