What is a cloud-free pass in satellite flood mapping?
If you've ever sat in an EOC refreshing a tasking order status and wondering why the imagery still hasn't shown up, the answer is usually one word: clouds.
A cloud-free pass is the first orbit over your flooded area where the sky is clear enough for the sensor to see the ground. For optical, multispectral sensors, the kind most flood extent mapping relies on, cloud cover is opaque. The sensor can't see through it. If the storm that caused the flood is still parked over the area when the satellite passes, that pass is wasted for mapping purposes, no matter how good the sensor is.
This is why satellite revisit time after a flood and a cloud-free pass are not the same thing. Revisit time is how often a given satellite, or constellation, flies over your area, regardless of weather. A cloud-free pass is the first time after that revisit when the sky cooperates. During active weather, the gap between the two can run from a single orbit to several days.
Why revisit time alone doesn't tell you when you'll get a map
Say a sensor has a 3-day revisit time. The natural assumption is "we'll have a flood map in 3 days." That math only holds if pass number one is clear. During and right after a flood event, it usually isn't. The same low-pressure system that caused the flooding tends to sit over the basin for a day or two afterward, so the honest answer to "how long" is "whichever pass comes back clean," not "whichever pass comes next."
This is the main reason flood imagery runs later than people expect. Providers aren't slow to process the scene. There's simply nothing to process until the sky clears enough for an optical sensor to see standing water instead of cloud tops.
What shortens the wait
A few things narrow the gap between the flood and a usable scene:
- More satellites in the constellation. More passes per day means more chances to catch a break in the clouds, even when any single satellite's own revisit time is slow.
- Multiple sensors tasked in parallel. Running several providers at once instead of waiting on one raises the odds that at least one pass comes back clear.
- Someone checking which pass came back clean. A tasking schedule tells you when a satellite flew over. It doesn't tell you whether that particular scene is usable until a human or a process confirms it and pulls the flood extent out of it.
None of this makes clouds move faster. What it changes is how much manual checking and delineation falls on your team once a clear scene finally lands, and how fast that turns into something you can hand to response coordination.
That's the gap Rapid Flood Mapping is built to close: it watches for the first cloud-free pass over your affected area and turns it into a numbered situation brief as soon as that pass comes in, instead of a GIS analyst noticing the imagery arrived and starting to trace water by hand.
If you're the one who has to answer "where's the map" every time a flood spins up, it's worth having this queued up before the next event instead of during it.