A new, powerful Citizen Portal experience is ready. Switch now

Councilors ask staff to explore policy for sweet gum tree removals after safety complaints

November 22, 2025 | University City, St. Louis County, Missouri


This article was created by AI summarizing key points discussed. AI makes mistakes, so for full details and context, please refer to the video of the full meeting. Please report any errors so we can fix them. Report an error »

Councilors ask staff to explore policy for sweet gum tree removals after safety complaints
Council Member Fuller asked the council to consider a formal policy for removing or managing sweet gum trees after recounting several incidents in which tree roots and seed pods damaged sidewalks and caused injuries. Fuller said a resident in Ward One fell and broke a toe on sweet gumballs and described a case in which the city removed a large, apparently healthy sweet gum at a resident’s request.

Fuller said private removal costs can be “exorbitant,” citing a neighborhood estimate of $2,000–$3,000, and described a Springfield, Illinois, program where a resident who had a tree removed paid a fee (cited in the discussion as about $250) to replace the tree. “We have a huge number of sweet gum trees,” Fuller said, and asked staff to examine options for a policy that balances walkability, public safety and canopy replacement.

A staff speaker replied that the incoming parks and recreation director should review the city’s work plan and coordinate with the forestry commission to scope a policy and schedule for potential removals and replacements. Council members suggested linking any program to the city’s existing tree plan and to prior work, including Emerald Ash borer eradication efforts, to identify funding and timelines.

Council members emphasized the need to preserve canopy where possible, to communicate replacement plans to neighborhoods, and to consider whether removal programs should prioritize public facilities (businesses, churches) or private yards that present a public‑safety risk. No formal motion or vote was taken; staff was asked to evaluate options and to include the item in future work‑plan discussions.

View the Full Meeting & All Its Details

This article offers just a summary. Unlock complete video, transcripts, and insights as a Founder Member.

Watch full, unedited meeting videos
Search every word spoken in unlimited transcripts
AI summaries & real-time alerts (all government levels)
Permanent access to expanding government content
Access Full Meeting

30-day money-back guarantee