Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Big Tree Protection topic
No spam. Unsubscribe anytime.
Atlantic Beach tree subcommittee presses staff for better data as it sharpens 'big tree' protection recommendations
Summary
The EFC tree subcommittee pressed staff to improve monthly and semiannual tree-report data and debated the draft 'big tree' ordinance (terminology, DBH thresholds and species scope); the group moved to support a relocation concept and asked staff to adopt Alachua County-style infeasibility language.
Get email alerts on the Big Tree Protection topic
No spam. Unsubscribe anytime.
Atlantic Beach’s Environmental Stewardship Committee (tree subcommittee) spent much of its May 27 meeting pressing staff to fix data and process gaps in monthly and semiannual tree reports as the city prepares draft "big tree" protection language for the City Commission.
City staff and Peyton Jamieson (staff member) told the subcommittee that tree-permit reporting can be misleading because permits are frequently applied early in a project and closed much later; arborist letters sometimes are emailed rather than entered into the permitting portal, so they do not flow into automated reports. Peyton said staff is reviewing how to capture the status of permits, whether removals are tied to new construction or accessory projects, and whether added fields could make monthly data more actionable. "We're working on trying to come up with a better way to refine the data that is being presented," Peyton said.
Members urged a pragmatic approach: keep producing consistent monthly figures while staff develops higher-quality semiannual reports for the June 29 packet. Several committee members asked staff to break recent removals into species and size bands (suggested ranges: under 20, 20–24, 25–30, 31–36, >36 inches DBH) so the subcommittee can model how different DBH cutoffs would affect the number of trees subject to the new protections.
The meeting also centered on proposed "landmark" (staff draft used the term "champion") tree protections. Staff suggested a 20-inch DBH threshold for maritime species; several members pushed back, arguing 20 inches would capture many small, relatively young trees. Debate focused on two linked questions: which species should be included (live oaks only or all maritime species) and what DBH should trigger the higher protection level. One member said the matrix staff shared showed an average removal DBH of about 14 inches, which supported raising the cut-off if the goal is to protect truly large specimens.
On policy mechanics, the subcommittee voted to add a relocation concept to its recommendations: the city would have first right of refusal to relocate a qualifying tree (relocation would be at the owner's expense and used as a mitigation option). The motion passed on a voice vote after members discussed the logistics and cost uncertainty of moving large trees. "It'd be great if they could [relocate large trees]," a member said; others warned about long-term watering and maintenance costs.
Separately the subcommittee moved and approved language asking staff to model the Alachua County approach to requiring proof of "no feasible alternative" (no other location, site conditions or design alternatives) plus pruning and other mitigation steps before permitting removal of a landmark tree. Members said such language would give staff and the commission a clear standard for evaluating variances and appeals.
Next steps: staff will (1) prepare an updated semiannual report for the June 29 commission packet (with a clear note about data limitations if needed), (2) produce species-by-size tables and consider adding the recommended permit fields, (3) return with a short decision-tree/process proposal for when staff handles removals and when cases should be escalated to the commission, and (4) provide a short memo on why staff recommended 20 inches for maritime species and on implementation options for the relocation concept.
The subcommittee adjourned after directing staff to bring the requested data and process recommendations back at the next meeting.
