Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, October 7, 2015 <br />Page 2 <br />broad goals brought forward at the initial July 2015 meeting, purpose for the ordinance, <br />45 <br />and desire to provide incentives to preserve trees in the community without <br />46 <br />overburdening individual property owners while ensuring proper oversight of this valuable <br />47 <br />community asset. <br />48 <br />Mr. Gozola reviewed attachments included in the meeting packet, including Attachment D <br />49 <br />providing a clean copy of the draft tree preservation ordinance for tonight’s review and <br />50 <br />public comment. Mr. Gozola reviewed cover memoranda related to tonight’s discussion <br />51 <br />providing explanations of each section as well as areas where additional feedback was <br />52 <br />being sought based on reviews to-date at various levels. <br />53 <br />Previous Ordinance 1011.04 <br />54 <br />Mr. Gozola advised that language retained from the previous Tree Preservation <br />55 <br />Ordinance was not incorporated into Section 4 of the new draft ordinance and outlined in <br />56 <br />the Memorandum to Attachment D dated October 6, 2015 related to this proposed final <br />57 <br />draft. <br />58 <br />Mr. Gozola advised that note item to note was revision of “specimen” trees to “significant” <br />59 <br />trees. <br />60 <br />Mr. Gozola also noted that Attachment A had been mission specifics for “cash in lieu of” <br />61 <br />payments as an option for tree locations or relocations as applicable, with Attachment B, <br />62 <br />lines 344 – 346 now addressing that area based on best practices and guarding against <br />63 <br />claims that fees may be deemed unreasonable. Ms. Gozola noted that in accordance <br />64 <br />with the City of Roseville’s policy to establish fees by policy or resolution rather than in <br />65 <br />specific ordinances, fees were not included in the proposed draft ordinance. <br />66 <br />In an effort to provide examples of practical application of the ordinance using previous <br />67 <br />developments in Roseville (e.g. Cherrywood Point, Pulte Homes), Mr. Gozola reviewed <br />68 <br />how those comparisons would address tree inventories and differentials between the two <br />69 <br />ordinances, including how numbers would be impacted or exemptions applied, even <br />70 <br />though he admitted it was difficult to compare apples to apples in those cases. <br />71 <br />For discussion purposes and to avoid confusion, Mr. Gozola suggested using the draft <br />72 <br />ordinance provided as a bench handout (Revised Attachment B) as the reference going <br />73 <br />forward. <br />74 <br />Commission Discussion/Questions <br />75 <br />Page 1, line 27, Member Bull questioned multi-stem trees (e.g. Birch) and rationale for <br />76 <br />measuring them as one tree using the diameter breast height (DBH) of the largest stem <br />77 <br />only. <br />78 <br />Mr. Rehder responded that any species could be multi-stemmed and required a method <br />79 <br />to calculate their DBH, using Boxelder Trees cut down multiple times as an example that <br />80 <br />would require a protection zone. Mr. Rehder stated that this language attempted to <br />81 <br />address anomalies with multi-stem trees, clarifying that if a single trunk was large <br />82 <br />enough, it would still fall into the heritage tree category and have potential as a <br />83 <br />preservation tree providing justification for doing so. <br />84 <br />Page 1, line 22-25, Member Bull referenced examples of trees with 4” caliper inch being <br />85 <br />not measured, questioning therefore if anything under 6” would be considered or rated as <br />86 <br />one 12” tree. <br />87 <br />Along those same lines, Member Cunningham further questioned if the main tree trunk is <br />88 <br />at breast height and then splits after that, would it still be considered one tree. <br />89 <br />Mr. Rehder responded affirmatively, that the height would typically be used (above breast <br />90 <br />height). Mr. Rehder further noted that generally multi-tem trees already had a strike <br />91 <br />against them depending on whether or not trunks were pushing together, as they were <br />92 <br />considered not ideal trees, and would be difficult to consider as a heritage tree if they <br />93 <br />already had a pre-existing condition making them non-preferred heritage trees. <br />94 <br /> <br />