Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, October 7, 2015 <br />Page 9 <br />Mr. Paschke noted that may depend on tree classification numbers, suggested some <br />397 <br />changes were needed in that section, including tree ranges and whether or not they were <br />398 <br />considered significant; and suggested staff take a look at those numbers to ensure their <br />399 <br />consistency. <br />400 <br />Chair Boguszewski noted a number of grammatical corrections needed throughout the <br />401 <br />document prior to final presentation to the City Council; and to ensure tabulated <br />402 <br />formatting was consistent. <br />403 <br />Page 4, Section E (tree classifications), line 129, Member Murphy suggested changing <br />404 <br />“common” trees to “significant trees with measurements of 12’ tall or greater based on his <br />405 <br />personal interpretation of language as written. <br />406 <br />Page 7, line 220, Member Daire noted if an additional column is added to the table of <br />407 <br />calculations, it also needed to bee reflected in that line, (table starting at line 313). <br />408 <br />Mr. Gozola noted that line 220 text referenced the summary table and its intensions and <br />409 <br />the number of trees removed in each category. <br />410 <br />In that case, Member Bull suggested that the table should reflect 8’ rather than greater <br />411 <br />than 8’ in, opining that the calculations in the table (line 313) were shown backwards. <br />412 <br />Page 10, Section J.2.a, line 309, Member Bull stated his preference that the text state 3 <br />413 <br />DBH replacement inches and move on in increments from there, with Member Murphy <br />414 <br />questioning if this rationale was based on science or personal preference, with Member <br />415 <br />Bull stating it was based on his experience with coniferous trees and their typical height. <br />416 <br />Member Murphy sought feedback from Mr. Gozola and Mr. Rehder based on their <br />417 <br />expertise in the field and how 6’ was originally derived at. <br />418 <br />Based on his field experience, Mr. Rehder responded that for larger measurements he <br />419 <br />had worked backwards, but he recognized the point made by Member Bull as having <br />420 <br />merit and that measurements should not be based one to one all the way across; but <br />421 <br />should indicate measurements for each species and show representative values for <br />422 <br />those height ranges accordingly. <br />423 <br />Consensus of the Commission, staff and consultants was to revise the table at line 313 to <br />424 <br />more closely reflect that experience at lower height ranges. <br />425 <br />Member Bull clarified that this would reflect changes in Section J.2.a to start at 3’ versus <br />426 <br />6’; with the consultants verifying that intended change. <br />427 <br />Page 11, Section K (tree protection required), line 347, Member Bull sought additional <br />428 <br />information on ramifications if the area around a tree in the protection area was not <br />429 <br />properly protected; with Mr. Rehder responding that the potential for a stop work order for <br />430 <br />the developer was one option if they were found in violation; and if necessary staff would <br />431 <br />enforce that if such a situation arose. Member Bull noted there may be damage to the <br />432 <br />root system that may not be as evident as damage to the tree above ground. <br />433 <br />Mr. Bilotta noted this was the reason for including the unplanned loss protection since <br />434 <br />with those trees assigned a slightly higher replacement rate to discourage working in <br />435 <br />proximity to them. Mr. Bilotta advised that the forester would make a determination at that <br />436 <br />point if he found the intrusion significant enough that would cause eventual tree loss <br />437 <br />(unplanned loss), using the 2 year warranty period and field inspection with negotiations <br />438 <br />as needed. <br />439 <br />Member Bull questioned if there was sufficient language in the draft ordinance for the <br />440 <br />forester to make that determination. <br />441 <br />Mr. Bilotta responded affirmatively, noting that field issues happen all the time and <br />442 <br />negotiations are part of the process for a condition of approval of other mechanism in <br />443 <br />place throughout city code for those type of responses throughout a normal construction <br />444 <br />process. <br />445 <br /> <br />