Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Environmental Review Riverwalk topic
No spam. Unsubscribe anytime.
Council reviews Riverwalk environmental worksheet; members press for stronger protections on wells, species and runoff
Summary
Dayton City Council pulled the Riverwalk Fourth Edition environmental assessment (EAW) for discussion and asked staff to tighten enforcement language through developer agreements after concerns about shallow private wells, native seeding, erosion controls and chloride management were raised.
Dayton City Council on March 11 pulled the Riverwalk Fourth Edition environmental assessment worksheet (EAW) from consent for extended discussion about groundwater vulnerability, habitat measures and how to ensure developer commitments are enforced.
Council members and staff focused on technical details in the EAW that, several said, read as non‑binding guidance rather than firm requirements. City Engineer Jason Quisberg noted the EAW’s role is to identify potential impacts and to flag whether a more extensive environmental impact statement (EIS) is needed. He told the council the EAW is meant to “determine if an EIS is needed,” with the EIS requiring a larger, site‑specific investigation if triggered.
The council heard that many private wells in the project area are relatively shallow — around 79 to 80 feet — while the city’s primary supply wells are hundreds of feet deeper. A resident raised the concern that shallower wells are more susceptible to surface contamination than deeper aquifers. Councilmembers asked staff whether the EAW’s language and the developer’s planned measures would adequately protect private wells from road runoff, chloride and potential fuel contamination if a gas station were later proposed near the area. Quisberg said shallower wells are “more susceptible” but stopped short of concluding they were at immediate risk; he recommended ensuring impermeable layers and site‑specific protections are identified during plan review.
Separately, council members pressed for firmer commitments on landscaping and habitat protections that currently read in the EAW as “may include” rather than “will include.” Topics raised included mandatory use of native seed mixes, biodegradable erosion control materials, wildlife‑friendly curbing to allow small animal passage, and a chloride management plan for winter operations. A councilmember noted that the EAW document contains city responses to developer submittals, and asked how to make sure measures in the EAW become enforceable obligations. Staff replied that implementation tools include explicit conditions in the developer’s agreement and plan‑review checkpoints at final plat; staff said the developer’s agreement is executed at final plat and that items deemed important can be required there.
After discussion the council moved and seconded the item, then voted to approve the EAW item as presented; the motion passed 5–0.
Why this matters: The EAW will inform whether a more detailed environmental review is needed and sets expectations for protections around groundwater and habitat. Council members emphasized that wording in the document should not be left vague if the council expects enforceable measures.
