Public Safety
IoT Networks Could Improve Washington Flood Monitoring
Published by IOT Washington Research & Editorial Team

Washington's flood risk comes in several forms. Atmospheric rivers can send heavy rain onto mountain snow and swell rivers in the western part of the state. Rapid snowmelt can raise water in the east. Burned hillsides shed water quickly. The state has seen serious floods in recent years, including damaging events in the Nooksack basin in 2021 and major river flooding in western Washington in late 2025. Each one prompted calls for better local warning.
The state already has a solid river monitoring network. This article looks at how low-cost IoT sensors could fill in the gaps, and what would be needed to make that useful.
What Exists Today
Federal and state agencies run river gauges, rain gauges, weather stations and snowpack sensors, and forecasters use them to issue flood watches and warnings. These sites are accurate and well maintained, but there are only so many of them. A town on a small tributary may sit miles from the nearest gauge, and a flash flood can develop faster than a forecast can account for.
Where Gaps Remain
| Gap | Why it matters | IoT approach |
|---|---|---|
| Small streams and culverts | Fast response and local flooding | Low-cost level sensors at key crossings |
| Roads and underpasses | Drivers need real-time warning | Water depth sensors with signs or alerts |
| Urban drainage | Storm drains overwhelm quickly | Level sensors in pipes and basins |
| Burned watersheds | Debris flows after fires | Rain gauges and slope sensors |
| Farm fields and ditches | Saturation and runoff | Soil moisture and ditch level sensors |
| Dike and levee systems | Seepage and overtopping | Water level and pressure sensors |
How Low-Cost Sensors Work
A typical flood sensor measures water level using ultrasonic or radar technology mounted over a stream or in a culvert. It may include a rain gauge and a small solar panel. Data is sent by cellular or low-power radio every few minutes, and more often when levels rise. Dashboards plot readings and send alerts when thresholds are passed. Such devices cost far less than a full gauging station, which makes dense networks practical.
Who Could Use the Data
- Emergency managers. Decide on closures and evacuations with local detail.
- Road departments. Close or sign flooded roads and prioritize repairs.
- Farmers. Protect livestock, equipment and crops, and plan field access. See how farmers use sensors for water and weather risk.
- Utilities. Protect substations, pump stations and treatment plants.
- Residents. Receive local alerts and understand conditions.
- Forecasters. Use extra observations to check and improve models.
City and Utility Use Cases
Cities can monitor storm drains and detention basins and combine the data with rainfall to anticipate trouble spots. Water and sewer utilities use level sensors to manage overflows. Examples of related urban monitoring appear in Kirkland public services technology and real-time leak detection in Issaquah. Smart city planning is also covered in Spokane's roadmap for the next five years.
Ports, Roads and Freight
Floods disrupt freight, closing highways and rail lines. Sensors at key crossings help logistics managers re-route trucks. Ports also watch water levels and storm surge. Our article on smart port technology in Tacoma touches on how data supports operations.
Challenges to Solve
Sensors in streams face debris, ice and sediment, so mounting and maintenance matter. Power and connectivity can fail in storms exactly when data is needed, so batteries, solar and backup links are important. Data must be accurate, with calibration and quality checks, since false alarms reduce trust. Someone must own and pay for upkeep, which can be hard for small communities. And data needs a clear way to reach forecasters and the public without confusion about which source is official.
A Practical Pilot
A county or city can start with a handful of sensors on streams and roads known to flood. Choose sites with a history of problems, partner with the nearest forecast office, and set alert levels with emergency staff. Share readings publicly where possible and review each event to adjust. Funding sources may include state and federal hazard mitigation programs, as discussed in federal infrastructure funding for Washington IoT rollouts.
A Practical Example: A Small Town on a River
Picture a small town where a creek runs through a culvert under the main road. During heavy rain, the culvert clogs with debris and water spills onto the road and into nearby homes. A level sensor upstream and another at the culvert inlet report to the town's public works team. When water rises quickly, the team receives a text, sends a crew to clear debris, and puts barriers on the road. Residents on the street receive an alert. The same data later helps the town decide whether to replace the culvert with a larger one.
Evidence like this also supports funding requests. A record of how often and how fast the creek rises is more persuasive than anecdotes when applying for hazard mitigation grants.
Looking Ahead
Expect more partnerships between agencies, universities and local governments, wider use of open data standards, and tighter links between sensor readings and flood models. Over time, the combination of established gauges and low-cost local sensors could give communities more lead time. It will not prevent floods, but better information can limit harm and speed recovery. See the public safety category and the Everett public safety page for related coverage.
