Flood extent maps vs hydraulic models: what a duty officer actually needs
Three hours into a flood event, someone in the EOC asks for "the model output" and someone else asks for "the extent map," and half the room treats those as interchangeable. They're not. They answer different questions, they come from different places, and mixing them up at the wrong moment can send a crew to the wrong street.
A hydraulic model and a satellite-derived extent map can both show you water on a basemap. That's where the similarity ends.
What each one is telling you
A hydraulic or hydrodynamic model is a simulation. Someone built it ahead of time from a digital elevation model, channel geometry, and assumptions about how water moves across that terrain. Feed it rainfall totals, upstream gauge readings, or a breach scenario, and it computes where water should end up and how deep. It's forward-looking by design. That's its whole value: it can tell you what the next six hours look like before they happen, which is exactly what you need for evacuation timing and resource pre-positioning.
A flood extent map from satellite imagery is an observation, not a simulation. It's a record of standing water detected from an actual pass over the affected area, at the moment the sensor flew over and cloud cover allowed a clean look. It doesn't forecast anything. It tells you what was wet at that specific time, full stop.
One is a prediction running on inputs. The other is a photograph of the ground, more or less, processed into a polygon.
Where the model runs into trouble mid-event
Models are built on assumptions, and live events are where assumptions get tested. A gauge network can go offline right when you need it most. A levee can breach somewhere the model never flagged as a weak point. Urban drainage can back up in ways the terrain model doesn't capture because storm sewers aren't in the elevation data. Flash flooding in particular moves faster than most calibrated models were built to track in real time.
None of this makes the model useless. It means the output is only as good as its inputs, and during a fast-moving event those inputs degrade fastest. A model run six hours ago on pre-event rainfall forecasts can be meaningfully wrong by the time water arrives somewhere. Treating that output as ground truth for a tasking decision is how crews end up staged in the wrong sector.
Where satellite extent falls short too
It's fair to be honest about the other side of this. An extent map is bounded by whatever pass was available and whatever the weather let the sensor see. Medium-resolution imagery in the 3 to 10 m range won't resolve a flooded alley or a single blocked culvert. It tells you nothing about what happens next. If the sky stayed socked in for two days after the event, you're working from an older look than you'd like.
So neither one, on its own, gives a duty officer the full picture. The model tells you what to expect. The extent map tells you what's there.
Using both without the mix-up
In practice, the model earns its keep before and during the early hours: pre-positioning crews, deciding which zones to warn first, setting expectations for depth and timing. Once a cloud-free pass is available, an extent map grounds those expectations in what's underwater right now, and that's the thing worth handing straight to response coordination as a numbered situation brief rather than a modeled guess. Rapid Flood Mapping is built for that second half of the job: turning the first usable satellite pass after an event into that brief, fast.
If your next situation report needs an extent map that reflects what the imagery is showing right now, not what a model expected, that's the gap this is built to close.