Get AI Briefings, Transcripts & Alerts on Local & National Government Meetings — Forever.
University Park council reviews tree-policy recommendations after citywide inventory
Loading...
Summary
City staff presented results of a public-tree inventory and a set of recommended changes to University Park’s tree policies, seeking council feedback on parkway maintenance responsibilities, an approved species list, permitting for parkway plantings, and potential requirements for private development.
City staff on Tuesday briefed the City Council of University Park on a multi-department review of the city’s tree policies and a recent inventory of public trees, asking council members for feedback before drafting ordinance language.
The presentation covered an inventory of 9,582 public trees completed in late summer 2024, preliminary recommendations from consultants and staff, and proposed changes grouped into two code articles: rules for trees in public spaces (parkways) and rules affecting private development. Staff emphasized the recommendations are for council discussion only and no ordinance action was requested at the meeting.
Why it matters: the inventory and proposed rules aim to preserve established canopy, reduce conflicts between trees and city infrastructure, and set clearer responsibilities for residents and developers. Staff described the work as a phased process tied to goals from the city’s Centennial Master Plan to preserve streetscapes and establish measures that protect mature trees while maintaining water and sewer infrastructure.
Key facts and staff recommendations - Inventory: City staff reported 9,582 trees were inventoried on public property between Aug. 26 and Sept. 13, 2024; about 8,206 (roughly 86%) of those were located in parkways. Staff said hazardous or diseased trees identified in the inventory have already been removed. - Parkway maintenance: Staff proposed retaining the longstanding requirement that the abutting property owner maintain parkway trees but strengthening the language from a permissive to a mandatory form (changing “has the responsibility” to “shall maintain”). The recommendation includes a public-education list of “what it means to maintain” a parkway tree (pruning standards, avoiding girdling, irrigation guidance and similar best practices). - Parkway planting permit and species list: Staff proposed an application and review process for new parkway plantings, using an approved-species list maintained in a tree technical manual rather than only in the ordinance. The manual would be updated by staff as conditions or best practices change. - Private-development requirements: The city’s current requirement for new construction was described as two 6-inch-caliper trees; consultants recommended the city consider switching to two 2-inch-caliper trees (staff said smaller-caliper trees often have higher survival rates in construction environments and increase species diversity). Staff also discussed keeping the existing exception for single-family attached lots narrower than 50 feet (one tree) and allowing limited staff discretion or deferred planting timing in some circumstances. - Fee-in-lieu option: Advisory committees raised the idea of allowing a monetary contribution instead of on-site planting when a site cannot reasonably accommodate required trees. Staff requested council direction on whether to include a fee option and, if so, how it should be applied.
Council discussion and staff follow-up Council members welcomed the inventory and the phased approach. One council member emphasized encouraging parkway plantings to preserve the city’s tree canopy and questioned whether a fee-in-lieu would deter planting; staff said the fee is intended as an option where planting is genuinely impracticable and described the development-review process as collaborative. Council members asked who would determine whether a lot truly lacks space; staff said that determination would be documented during development review and, when needed, supported by professional arborist documentation from the applicant.
Council members also asked whether the tree inventory would be published; staff said the city intends to present the inventory and ordinance package together rather than piecemeal, but that making the inventory available could be part of the public-education effort and staff would follow up. Staff reiterated that no ordinance vote was requested and that formal code language would be drafted and returned to council after additional review with the city attorney and advisory boards.
Ending Staff asked council members for direction on the specific topics raised—parkway permit process, approved-species list in a technical manual, tree-caliper sizing for new construction, fee-in-lieu options, and public education—and said they would return with draft ordinance language after council input and additional advisory committee discussion.
