Laserfiche WebLink
<br /> <br />Lexington Tree Commi?ee <br />Minutes of Special Mee?ng <br />11.26.23 <br />Held in the large common room <br />Lower level, Cary Public Library <br /> <br />1.Mee?ng called to order at 3:15 PM <br /> <br />2.Present: Mark Connor, co-chair, Pat Moyer co-chair and minutes, Gerry Paul, member, Nancy Sofen, <br />member, Todd Rhodes, Dan Miller, Alicia Morris, Ingrid Klimoff, Charles Hornig, Peter Kelley. <br /> <br />3.Pat laid out the process she hopes to follow during the first mee?ng of the Bylaw Enforcement <br />Working Group (BEWG): introduc?ons, consensus on the goal, establishment of mee?ng ?me and <br />schedule, and ground rules. <br /> <br />4. The major agenda item being fleshing out all of our understanding of current issues with enforcement, <br />Nancy was asked to lead point by point discussion which Pat moderated and to which Gerry <br />contributed.. <br /> Current lookback period for developers is 36 months, but is difficult to enforce unless we have <br />data, lot by lot, about what trees came before. Par?al data exists in stump measuring, Google <br />Earth. <br /> Permit applica?on, use by developers. Improved use, improved correct and complete use, with <br />resul?ng accurate $$ calcula?ons, in last month. Issues: what caused improvement--?was there a <br />mee?ng with developers? Can IT glitch be fixed? Does building commissioner seamlessly get <br />tree warden approval? How to ensure this improvement is durable? <br /> Current process of no?ng trees le? and trees removed during construc?on is corrupted by <br />informal, post permi?ng informa?on, by trees being removed without any no?fica?on, and by <br />difficul?es both with a clunky, tree by tree no?fica?on process, and with difficul?es reading the <br />pre-and post plot plans. Could a spreadsheet help? How to ease the process for developers. <br /> Overuse by staff and developers of “hazard tree” designa?on. THIS IS FELT TO BE A PROMINENT <br />PROBLEM. Na?onal standards for hazard designa?on should be followed, with cer?fied arborist <br />involved in each tree. Should goal be for TW to be a cer?fied arborist and to be full-?me? <br />Community feels trust broken with town on this issue. <br /> Tree protec?on during construc?on. Bylaw states fencing per Tree manual (ie at dripline) to be <br />up before and during. This is flagrantly disregarded. How to enforce? Could enforcement be <br />moved to building inspector? Could fencing be placed at the ini?al mee?ng with TW? Can the <br />building inspector/ TW be authorized to use stop work order when bylaw disregarded? If <br />dripline imprac?cal, can we insist arborist consult on trees affected? Should we require <br />developer to take out a bond on protected trees? Should guidelines for variances be se?led at a <br />friendly mee?ng before construc?on begins? (Kelley) <br /> Fee payment is haphazard and some?mes wrong. <br /> Tree warden is at ?mes inexact in specifying what he means—recommended plan?ng list vs. <br />large shade tree list, eg. <br /> ? <br /> Removing of town/setback trees occurs and the consequences of this viola?on o?en not clear to <br />public. Full transparency needed. Access to Viewpoint Cloud limited. (as an aside, should be <br />given to all members of BEWG). <br /> <br />