Lakeville staff outline tougher tree‑preservation ordinance with 40% residential threshold and a two‑year look‑back

City staff presented an outline of a proposed tree‑preservation ordinance at the May 27 Lakeville work session, describing scope, replacement math, credits for preserved woodlands and heritage trees, and a “look‑back” rule to discourage large clearings immediately before development applications.

Jason, a Community Development staff member who led the presentation, said the proposed ordinance would apply to new subdivisions, most new building construction on vacant or developed lots where the footprint expands, and residential tear‑downs that enlarge an existing dwelling; it would focus protection and replacement requirements on higher‑value “heritage” trees rather than every tree on a site. "We're really looking to keep this affecting new development at the time of subdivision, much like it is now," Jason said.

Key elements staff discussed:

- Scope: application to subdivision, new construction, and teardowns where footprints expand; emphasis on heritage or higher‑value trees rather than every tree on site. - Look‑back provision: staff proposed that if a site experienced a total tree removal greater than 2 acres within two years before a development application, the ordinance would apply to that pre‑application clearing (aerial imagery would be used to document prior condition). Staff said the two‑year period mirrors practices used by other cities and is intended to prevent clearing intended to avoid preservation rules. - Removal thresholds: staff initially proposed a 50% removal threshold for residential zoning and 70% for commercial/industrial; after discussion staff said they would bring a version showing a 40% residential threshold to the commissions for consideration. Council discussion favored a 40% residential threshold with a woodland credit to incentivize preservation. - Replacement math and credits: the draft prioritizes preservation of higher‑value hardwood/deciduous trees. For inches removed above the threshold, hardwood deciduous trees require replacement at a 1:0.5 ratio (half the diameter inches removed must be replaced), while heritage trees require 100% of removed diameter inches to be replaced. Replacement trees are tallied using a 2.5‑inch caliper as a unit; staff said the cumulative inch total is divided by 2.5 to determine the number of replacement trees required. - Fee in lieu: if replanting is infeasible on site, a fee in lieu would be charged; staff said the fee is intended to reflect the estimated cost of planting and establishing the required trees so there is no financial advantage to paying rather than planting. - Credits: the draft includes credits for preserved heritage trees and a proposed “significant woodland” credit to reward preservation of tree groups rather than scattered specimens. - Compliance and survey work: the ordinance would require a factual tree inventory and signed documentation such as a certified tree survey; staff said they routinely require inventories as part of submissions. - Establishment of a short warranty: staff noted commonly used two‑year survival or maintenance periods for planted trees and acknowledged enforcement and long‑term survival as practical challenges.

Staff ran examples to illustrate how the replacement math works. In one sample subdivision the removal exceeded the threshold (about 61% of significant diameter inches removed) and staff estimated a replacement requirement of roughly 873 trees plus additional inches for heritage trees; the example showed the developer’s planned on‑lot plantings would not satisfy the requirement and that the developer would need to find additional common areas or pay fee in lieu. Grace, a staff member who prepared the calculations, said an estimated cost for meeting the reforestation requirement in that example would be about $480,000 at the 50% threshold scenario.

Council members asked a range of clarifying questions: whether private property owners could clear trees at will (staff said the ordinance would tie to development activity, not purely voluntary private clearing), how cumulative removals would be counted (staff said removals would be cumulative over the look‑back period), whether exemptions would be required for infrastructure and how the city would notify property owners, and what warranty or monitoring period would apply to replacement plantings (staff indicated a two‑year monitoring period is typical).

Staff compared nearby cities’ ordinances, noting that other jurisdictions have lower removal thresholds or higher replacement rates; those examples informed staff’s recommendation to prioritize preservation of higher‑value trees and to provide clear, relatively simple rules rather than a long list of exemptions that complicate calculations.

Next steps identified by staff: draft the ordinance language incorporating a 40% residential threshold and a significant‑woodland preservation credit, present the draft to the Parks & Recreation Natural Resources Commission, then schedule a Planning Commission public hearing and return to council. Staff also said they would prepare a calculator or worksheet to help applicants compute required replacement trees.

Speakers

- Tina — Forestry / Community Development (introduced item) - Jason — Community Development staff (presenter) - Grace — Community Development staff (replacement math and cost examples) - Zach — staff referenced as contributing to research - Councilmember (multiple) — several council members asked clarifying questions; not all were named in the transcript

Authorities

- {"type":"code","name":"Existing subdivision code tree preservation provisions (current minimal requirement)","referenced_by":["tree-preservation-ordinance"]} - {"type":"ordinance","name":"Proposed tree‑preservation ordinance (zoning code replacement)","referenced_by":["tree-preservation-ordinance"]}

Actions

- {"kind":"referral","identifiers":{},"motion":"Draft tree‑preservation ordinance for council consideration with residential removal threshold adjusted to 40% and inclusion of a significant woodland credit; present to Parks Commission then Planning Commission for formal hearing","mover":"not specified","second":"not specified","vote_record":[],"tally":{},"legal_threshold":{},"outcome":"consensus_note","notes":"Staff will craft ordinance language and present to Parks Commission and Planning Commission for public hearing; council discussion indicated support for 40% threshold and incentives for preservation."}

- {"kind":"other","identifiers":{},"motion":"Direction to staff to create applicant tools (calculator/worksheet) and define fee‑in‑lieu methodology","mover":"not specified","second":"not specified","vote_record":[],"tally":{},"legal_threshold":{},"outcome":"no_action","notes":"Staff said they will prepare tools and cost estimates; no formal vote recorded."}

- {"kind":"motion","identifiers":{},"motion":"Motion to approve (unspecified action at end of meeting)","mover":"not specified","second":"not specified","vote_record":[],"tally":{"yes":null},"legal_threshold":{},"outcome":"approved","notes":"Transcript records a motion, a second and unanimous 'aye' with no specific object of the motion specified in the record."}

Discussion_decision

- {"discussion_points":["applicability to subdivisions and building expansions","two‑year/2-acre look‑back to deter pre‑application clearings","replacement math that prioritizes hardwoods and heritage trees","fee in lieu and enforcement/warranty concerns"],"directions":["staff to draft ordinance language with 40% residential threshold and woodland credit; prepare applicant calculation tool; present to Parks Commission then Planning Commission"],"decisions":[]}

Clarifying_details

- {"category":"look_back","detail":"Look‑back threshold","value":2,"units":"acres","approximate":false,"source_speaker":"Jason"}, - {"category":"look_back_period","detail":"Look‑back time window","value":2,"units":"years","approximate":false,"source_speaker":"Jason"}, - {"category":"residential_threshold","detail":"Residential removal threshold discussed","value":40,"units":"percent","approximate":false,"source_speaker":"Jason"}, - {"category":"commercial_threshold","detail":"Commercial/industrial threshold discussed earlier in draft","value":70,"units":"percent","approximate":false,"source_speaker":"Jason"}, - {"category":"heritage_replacement","detail":"Replacement requirement for heritage trees","value":100,"units":"percent of diameter inches removed","approximate":false,"source_speaker":"Grace"}, - {"category":"hardwood_replacement","detail":"Replacement requirement for hardwood/deciduous above threshold","value":50,"units":"percent of diameter inches removed","approximate":false,"source_speaker":"Grace"}, - {"category":"replacement_unit","detail":"Caliper used to count replacement trees","value":2.5,"units":"inches","approximate":false,"source_speaker":"Grace"}, - {"category":"example_cost","detail":"Estimated cost for one example development to meet reforestation requirement at 50% threshold","value":480000,"units":"USD","approximate":true,"source_speaker":"Grace"}, - {"category":"warranty_period","detail":"Typical warranty/monitoring period mentioned","value":2,"units":"years","approximate":false,"source_speaker":"Grace"}

Proper_names

- {"name":"Planning Commission","type":"organization"}, - {"name":"Parks and Recreation Natural Resources Commission","type":"organization"}, - {"name":"Cottage Grove","type":"location"}, - {"name":"Dayton","type":"location"}, - {"name":"Farmington","type":"location"}, - {"name":"Shakopee","type":"location"}, - {"name":"Woodbury","type":"location"}

Community_relevance

- {"geographies":["Lakeville"],"funding_sources":[],"impact_groups":["developers","property buyers","residents on large lots","future homeowners"]}

Meeting_context

- {"engagement_level":{"speakers_count":10,"duration_minutes":220,"items_count":1},"implementation_risk":"medium","history":[{"date":"prior discussions (fall)","note":"Staff and commissions previously discussed tree preservation; developers provided feedback"}]}

Searchable_tags

- ["tree preservation","zoning","reforestation","look-back","heritage trees","Lakeville"]

Provenance

- {"block_id":"b_tree_intro","local_start":0,"local_end":280,"evidence_excerpt":"Mayor Campbell, thank you for, having some time tonight. As you know, Forestry Department Community Development have been working together on, creating some ideas around the beefier tree preservation ordinance. So Zach and particularly Grace have put in a ton of effort and research into this process. So we're here tonight to update you, kind of on the general outline of the ordinance, that was including the packet.","global_start":2241.885,"global_end":2322.165,"tc_start":"00:37:21","tc_end":"00:38:42","text_sha256":"d41d8cd98f00b204e9800998ecf8427e00a1c3d0c9a9e8b5c1e1f0b5e82f3b1b","reason_code":"topicintro"}, - {"block_id":"b_tree_finish","local_start":0,"local_end":230,"evidence_excerpt":"Next steps will be creating the ordinance. Will adjust the residential of 40%. Look at the option for the woodland credit or significant woodland bridal. Craft the ordinance that won't take too long and then the cycle would be going through planning Commission back to council with with a stop at the Parks Commission.","global_start":4624.8604,"global_end":4854.8604,"tc_start":"01:17:04","tc_end":"01:19:14","text_sha256":"d41d8cd98f00b204e9800998ecf8427e00a1c3d0c9a9e8b5c1e1f0b5e82f3b1b","reason_code":"topicfinish"}

Salience

- {"overall":0.78,"overall_justification":"Ordinance will affect development patterns, tree canopy and potential costs for developers and property owners; includes a look‑back to deter pre‑application clearing.","impact_scope":"local","impact_scope_justification":"Applies to development in Lakeville; could influence lot prices and development costs.","attention_level":"high","attention_level_justification":"Changes to zoning code and development requirements are high‑interest to builders and residents."}