Cloud cover and your weekly lake pass: what actually gets missed

If you've ever pulled up a weekly satellite feed for your source lakes and found last Tuesday's pass is just a gray smear, you already know the answer to the question in the headline: it happens more than anyone running a monitoring program would like.
Optical satellites need a clear line of sight to the water. A pass over a lake region, especially anywhere with lake-effect weather, frontal systems, or summer convective buildup, has a real chance of landing on a day when the basin is socked in. Some weeks you get a clean look at every water body in the region. Other weeks half the lakes in your coverage area are hidden under cloud, and a few show up partially obscured, which is its own problem since a partial scene can make a clarity read look better or worse than it is depending on where the gap falls.
Why this matters more for source lakes than it sounds
A single missed pass on a reservoir you check once a quarter is a shrug. A missed pass on a source lake you're trying to track through bloom season is different. Chlorophyll-a and turbidity don't move in straight lines. They can shift fast around a storm event, a turnover, or the start of a bloom, and if your weekly cadence gap lands right there, you've lost the one data point that would have told you something was changing before it showed up at the intake.
The gap compounds too. A single cloudy week usually just pushes your trend line out by a week. Two cloudy weeks back to back and you're flying on a trend that's two to three weeks stale during exactly the stretch of the season when conditions move the most.
What wide-swath revisit actually buys you
This is where wide-swath revisit earns its keep over a narrow-swath, long-return-interval setup. A sensor with a wide swath comes back over your region on a weekly cadence, so a single clouded-out pass costs you one week, not a month. You lose that week's read, and the next scheduled pass is already queued up seven days later, already built into the schedule rather than buried somewhere in a multi-week orbital cycle.
It doesn't eliminate the problem. No optical platform sees through cloud. But a weekly cadence with wide-swath coverage across the whole region means a missed pass costs you one week of trend, not one missed pass turning into whatever gap happens to exist before the satellite swings back over your specific basin again. For a utility tracking a dozen or more source lakes at once, that difference between a one-week gap and a multi-week gap is the difference between catching an early bloom signal and catching it after it's already a problem at the raw water intake.
Working around the gap
A few things help when a pass does get clouded out:
- Treat a missed week as missing data, not a zero. A gap in the trend line is honest. A flat-lined or interpolated number isn't.
- Watch for partial scenes. A lake with cloud over half its surface can still give you a usable read on the visible portion, as long as you know which part of the water body it's covering.
- Keep the memo per water body even on a clouded week. A note that says "no usable scene this week" for a given lake is still useful information when you're reviewing the season later.
If you're weighing a wide-swath weekly service against a narrower-swath option with a longer return interval, the real comparison isn't resolution. It's how many weeks in a row you can go without a usable look at a given lake, and how many lakes in your region are covered by that one weekly pass instead of a handful you can reach by boat. Water Quality Retrieval is built around that weekly, region-wide pass, delivered as a numbered memo per water body so you can see exactly which lakes came through clean and which ones are waiting on next week's pass.
If a clouded-out week has ever cost you the read you actually needed, it's worth seeing what a weekly regional pass looks like for your source lakes.