Water Rush

What Water Rush Actually Is

Water Rush is a flood simulation and risk-mapping tool used primarily by civil engineers, urban planners, and emergency management teams to model how water moves across terrain during heavy rainfall or infrastructure failure events. It's not a single monolithic product — the name gets thrown around for a few different software packages and frameworks that all do similar things, so you need to verify exactly which one a vendor or collaborator is referring to before you commit. The most common use case I run into is when a municipality needs to model stormwater overflow in a watershed area that has mixed zoning — residential, commercial, and some agricultural patches. Water Rush takes a DEM (digital elevation model) as its base input, runs a kinematic wave or full Saint-Venant equation solver depending on your settings, and outputs a raster map showing flood depth and velocity across the grid. Here is what the basic workflow looks like in practice:

You start by importing your terrain data. A LiDAR-derived DEM at 1-meter resolution works well for urban areas. Coarser data, like 30-meter SRTM, will smooth out important features like culverts, drainage ditches, and road embankments. The output is going to be garbage if the input terrain doesn't resolve the micro-topography that actually directs runoff. Next you define your precipitation input. This can be a hyetograph for a specific storm event — say a 10-year, 24-hour storm for your region — or a time-series from a rainfall gauge. Water Rush also supports synthetic storm generation if you have USGS or NOAA return-period data for your watershed. I usually grab the data from NOAA Atlas 14 for US locations since it is publicly available and reasonably current. Then you set the land cover parameters. Soil type, curve numbers, Manning's roughness coefficients — these control how much water infiltrates versus runs off. This is where most people screw up. I had a project once where the consultant used a default Manning's value of 0.03 for an entire suburban area, but the neighborhood had a mix of asphalt, concrete driveways, and grassy yards. The flood model underestimated peak discharge by about 40 percent because the roughness was too uniform. I went through and mapped three separate zones with their own coefficients — 0.013 for asphalt, 0.015 for concrete, 0.04 for turf — and the revised output was noticeably different.

After that you run the simulation. The solver step size matters more than most users realize. If you are running a large watershed at a coarse temporal resolution, you will miss the timing of peak flows. I typically use a step size of 10 to 30 seconds for urban catchments and let it run. It is not fast — a medium-sized basin at 1-meter resolution can take anywhere from 20 minutes to several hours depending on your CPU and how many sub-elements you have in the mesh. Once the model finishes, you export the results. Water Rush gives you depth rasters, velocity vectors, and a timeline of how the flood front advances. You can visualize this in QGIS or ArcGIS, or use the built-in viewer if your license includes it.

Where It Falls Apart

Water Rush has some real limitations that nobody really advertises. The biggest one is that it assumes your terrain data is accurate and up to date. If your DEM is from five years ago and there has been new construction, grading, or road work in the meantime, your model will be wrong. Not slightly wrong — structurally wrong in places where the flow paths have actually changed. I learned this the hard way on a project in Ohio where a new subdivision had been built between survey updates. The model routed floodwater along an old drainage path that no longer existed, and the real water went somewhere entirely different during an actual storm event. Another issue is the treatment of engineered infrastructure. Water Rush can model culverts and pipes if you set them up explicitly, but the default behavior treats the terrain as a continuous surface. If your area has a complex storm drain network, you need to either import the pipe network data or accept that the model will approximate those pathways through modified terrain geometry. Neither option is trivial. There is also a licensing cost to consider. The full professional version runs a few thousand dollars annually per seat. There is a free tier with limited functionality, but it restricts the resolution and size of your model. If you are doing this for a small consulting firm or a grad student project, the free version might be enough for learning the interface, but you will hit walls quickly.

A Note on Alternatives

If Water Rush doesn't fit your needs, SWMM and HEC-RAS are the other two options that come up constantly in this space. HEC-RAS is government software, free, and extremely well documented, but it has a steeper learning curve and its 2D capabilities are less polished. SWMM is better for urban storm drain modeling specifically. Water Rush sits somewhere in between — easier to pick up than HEC-RAS, more flexible than SWMM for overland flow scenarios. I usually recommend trying the free trial first. Download it, throw a small test watershed at it, and see if the workflow matches how your team actually operates. If you spend more than a week fighting the interface without making progress, it is probably not the right fit and you should move on to something else.