Satellite imagery vs. grab sampling for reservoir bloom monitoring

If you run the sampling program for a source reservoir, you already know the drill. A field tech drives out, drops a bucket off the dock or the boat, fills a jar, labels it, and drives it back to a lab. Depending on your contract lab and your method (microscopy count, ELISA, or LC-MS/MS for toxins), you might have a result in a day. You might wait a week. Either way, the bloom has kept doing whatever it was doing the whole time you waited.
Satellite monitoring works differently. A sensor passes overhead once a day during bloom season and reads the color of the water surface across the whole reservoir, not just the spot where your boat happened to be. The two methods aren't competing for the same job, and understanding where each one is strong is most of what you need to build a monitoring program that doesn't leave you reacting to a bloom that's already at the intake.
What grab sampling tells you that nothing else does
Grab sampling is the only method that gives you a legally defensible toxin concentration. If you're reporting to your state primacy agency or deciding whether to issue a do-not-drink notice, you need a number from an accredited lab, not a spectral estimate. Microscopy also tells you which genus you're dealing with, which matters because Microcystis, Dolichospermum, and Planktothrix don't behave the same way or produce the same toxins.
The tradeoff is coverage and timing. Most utilities sample a handful of fixed stations, often weekly or biweekly outside of an active bloom event, because a tech and a boat cost money and a lab run costs more. A reservoir can look clean at your sampling point on Tuesday and have a surface scum forming over the old river channel by Thursday, two miles from where anyone looked. Point sampling is precise about the one point it measures and blind everywhere else.
Where satellite imagery fills the gap
Satellite imagery reads the spectral signature that chlorophyll-a and phycocyanin pigments leave on the water surface, rather than a toxin concentration in a sample bottle. That signature shows up as a bloom patch forming, holding steady, or spreading. Because the pass covers the entire reservoir surface instead of a handful of stations, it catches formation in parts of the reservoir your sampling schedule never visits, including the upper arms and coves where wind and nutrient loading tend to start trouble first.
For a source water protection program, the payoff is lead time. Seeing a bloom patch forming near a tributary inlet three or four days before it drifts toward your intake lets you schedule a confirmatory grab sample right there, instead of waiting for your next routine rotation to happen to catch it, and it gives you a head start on the intake-timing and public-notice conversations. That's the use case Algal Bloom Warning is built around: a daily-in-season read of your reservoir that flags where bloom extent is forming, with a short trend note so you can see whether it's growing, holding, or breaking up.
Putting the two together
Neither method on its own gives a complete picture. A reasonable way to think about it: satellite imagery tells you where and when to point your grab sampling, and grab sampling tells you what's actually in the water once you're there. Utilities that rely on sampling alone tend to find out about a bloom when operators start fielding taste-and-odor calls or when a routine sample comes back hot, often after the bloom has already moved. Utilities that rely on imagery alone have no toxin number to act on and no regulatory standing to issue a notice.
If your current program is grab sampling on a fixed schedule with no eyes on the rest of the reservoir, imagery is the piece that tells you when to break from that schedule, go look, and send a sample to the lab once you're there.
Watching your reservoir's bloom history build day by day, rather than sample by sample, is a different way to plan the season, and worth a look before your next bloom season starts.