Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Stormwater Map topic

No spam. Unsubscribe anytime.

West Whiteland task force weighs public stormwater map design, data limits

West Whiteland Township Stormwater Task Force · May 20, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

At its June 17 meeting, the West Whiteland Township Stormwater Task Force reviewed a first draft of a public Stormwater Flow Map, asked staff for clearer visuals and an accompanying 'how to' guide, and flagged limits on displaying critical infrastructure; staff will revise the map and present it again.

WEST WHITELAND, Pa. — The West Whiteland Township Stormwater Task Force reviewed the first public iteration of a Stormwater Flow Map at its June 17, 2026, meeting and asked staff to simplify the map visuals, add explanatory guidance, and tighten what data appear by default.

Wyatt Williams, the township sustainability coordinator, presented the map and explained its legend and multiple layers, including USA Flood Hazard Areas. Williams said the map is intended as a "visual education tool" to help residents understand where streams and floodplains lie in relation to their properties and that he would provide "an educational narrative" explaining how to use the layers and legend.

Task Force members said the current color scheme and many overlapping layers made the map look as though large areas were flooded. Libby Madarasz, the supervisor liaison, warned that an all-layer view "could make it harder for someone trying to sell their home," and suggested starting from a blank base that lets residents find their home and then add layers as needed. Jason Bailey, a Task Force member, urged starting with only floodplains visible and allowing users to enable flow layers incrementally to reduce visual 'noise.'

Technical recommendations included setting a higher minimum depth threshold so the map does not highlight zero-depth or negligible flows by default, refining how extreme high-end flows are displayed to avoid anomalies, and adding contour lines or digital elevation models (DEMs) so users can infer flow direction visually. Scott Jeffers, a Task Force member who joined the meeting late, said DEMs "make it obvious how water flows," and said he would provide links to Hydrologic Unit Code (HUC) and StreamStats geographic layers.

Township staff also discussed data-access and security limits. Williams said the township "cannot post information on the website regarding its critical infrastructure for security reasons," though Pam Gural-Bear, the township manager, noted staff will meet individually with residents who request more detailed information. Jason Bailey disagreed with the blanket restriction, and Williams said he could add an option for users to "request further details" so staff can handle sensitive requests case-by-case.

The Task Force asked staff to refine map resolution, consider labeling state versus township roads, include stormwater inlet and outlet locations only where appropriate, and produce a concise "How to use the web map" guide for publication alongside the map. Williams outlined those next steps and said he would update the map and narrative for review at the next Task Force meeting.

Procedural note: A motion was made and seconded to approve the May 20, 2026 meeting minutes; the minutes do not record the mover, seconder, or the outcome of the vote.

The meeting, which began at approximately 5:00 p.m., adjourned at approximately 5:45 p.m.