Where satellites are seeing cyanobacteria.
NASA and EPA read a pigment index over roughly 2,300 U.S. lakes large enough to resolve at 300 m. This map says where to look — it does not say whether a bloom is toxic, and it is not a substitute for your state’s advisory.
- Lakes elevated or high
- 1,164
- Could not be assessed
- 375
- Lakes screened
- 2,321
Composite window: 2026-08-30 to 2026-09-05
What a satellite can and cannot tell you about a bloom
This map is useful for one thing: narrowing where to look. Everything below is a limit of the instrument, not small print — and the limits are what make the map safe to use.
This map is a pre-screening indicator that says where to look. It is not a health assessment and it is not a substitute for your state’s cyanobacteria advisory — your state programme is the authority on whether a lake is safe to swim in, drink from, or fish.
A satellite reads only the surface — the top of the water column. Wind mixes a bloom down through the lake, so a bloom that is genuinely present can be missed entirely, and this map can read clear on a day a lake is not. That is the failure direction that matters: an absent reading is never evidence of clear water.
The index measures a pigment common to cyanobacteria. It cannot distinguish a toxic bloom from a harmless one, and it says nothing whatever about microcystin or any other toxin. Only sampling the water can answer that.
Readings below roughly 10,000 estimated cells/mL are beneath the sensor’s detection limit. That is “we could not see anything”, not “there is nothing there” — those lakes are not verified clear.
Cell densities are converted from a pigment index, not counted. The published conversion carries roughly 29% mean absolute percentage error, so treat every figure here as an estimate with real spread around it rather than a measurement.
Cyanobacteria are bacteria, not algae, despite “blue-green algae” being the common name. The distinction matters because the toxins that make a bloom dangerous are bacterial, and treatments and advisories written for algae do not necessarily apply.
The underlying product is published by NASA as preliminary and for evaluation purposes only. It has not been through the validation an operational product would carry.
The sensor resolves at 300 m, and a lake needs a few clear water pixels away from its own shoreline to be read at all — roughly 900 m across. Smaller lakes and most rivers are absent from this map entirely, which says nothing about their condition.
This map has not been validated against state advisory records. Published agreement figures for satellite cyanobacteria screening come from the research literature and describe other lakes in other seasons — not this map’s performance, which nobody has measured yet.
The impaired waters map shows what states have formally told EPA about their own waters under the Clean Water Act — a regulatory judgement, made over assessment cycles that run for years, and one of its listed causes is nutrient and algal growth. This map is a satellite reading of a single recent week. A lake can be listed as impaired for nutrients and read clear here, or read high here and never have been assessed at all. Neither one supersedes the other, and neither is an advisory.
About cyanobacteria blooms.
What a satellite reading does and does not tell you about a lake.
Is it safe to swim in a lake this map shows as clear?
This map cannot answer that, and it is the most important thing to understand about it. A satellite reads only the surface of the water; wind mixes a bloom down through a lake, so a bloom that is genuinely present can be missed entirely and the lake will read clear here. Readings below roughly 10,000 estimated cells/mL are beneath the sensor’s detection limit — that is “we could not see anything”, not “there is nothing there”. Your state’s cyanobacteria programme issues the advisories, samples the water, and is the authority on whether a lake is safe to use. This map is a pre-screening indicator that says where to look.
Are cyanobacteria the same as algae?
No, despite “blue-green algae” being the common name. Cyanobacteria are bacteria. The distinction matters because the toxins that make a bloom dangerous — microcystin among them — are produced by the bacteria, and guidance written about algae does not necessarily apply. Plenty of green water is harmless algae, and plenty of cyanobacteria blooms are themselves harmless. Colour is not a reliable guide either way.
Does a “high” reading mean the bloom is toxic?
No. The satellite measures a pigment that cyanobacteria contain, not a toxin. The index cannot distinguish a toxic bloom from a harmless one and says nothing whatever about microcystin concentration. A high reading means there is a lot of cyanobacteria at the surface — a good reason to check your state advisory and to stay out of visible scum, and not a determination that the water is poisonous. Only sampling the water answers the toxicity question.
Where do the cell counts come from, and how accurate are they?
They are estimates converted from a pigment index using a published relationship (Lunetta et al. 2015), not counted cells. That conversion carries roughly 29% mean absolute percentage error, so a figure of 100,000 cells/mL should be read as a number with real spread around it rather than as a measurement. The two density landmarks the bands use — about 20,000 and about 100,000 estimated cells/mL — are the values US state programmes most commonly cite, and they vary by state. Check your own state’s thresholds; those are the ones that apply where you are.
Why is my lake not on this map?
Most likely it is too small. The sensor resolves at 300 m, and a lake needs several clear water pixels away from its own shoreline to be read at all — roughly 900 m across. Around 2,300 U.S. lakes across 46 states meet that bar. Rivers, ponds and most reservoirs are absent entirely, and their absence says nothing whatever about their condition. A lake can also be present but unassessable in a given week, in which case it is drawn with the reason rather than left off.
What does “could not be assessed” mean?
That we have no reading, and the map says which of six things prevented one: ice or snow on the lake, cloud over it, the lake reading as mostly land in the satellite product because it is drawn down or dry, a lake too small to resolve, a lake outside the product’s footprint, or our own failure to retrieve the imagery. That last one is ours rather than weather, and it is labelled separately for exactly that reason. An unassessable lake is never evidence of a clear lake — those are different facts, and this map keeps them apart deliberately.
How current is this, and how often does it update?
The map renders NASA and EPA’s 7-day composite, which is published weekly and lags a few days behind the end of its own window. Our sampler runs daily so a late composite is picked up promptly, but the underlying observation does not move faster than the satellite product does. The window the map covers is shown on the page. NASA publishes the underlying product as preliminary and for evaluation purposes only.
How is this different from the impaired waters map?
The impaired waters map shows what states have formally told EPA about their own waters under the Clean Water Act — a regulatory judgement made over assessment cycles that run for years, and one of its listed causes is nutrient and algal growth. This map is a satellite reading of a single recent week. A lake can be listed as impaired for nutrients and read clear here, or read high here and never have been assessed at all. Neither supersedes the other, and neither is an advisory.
Has this map been checked against real advisories?
Not yet, and we say so rather than borrowing someone else’s numbers. Published agreement figures for satellite cyanobacteria screening come from the research literature and describe other lakes in other seasons — they are not this map’s measured performance. A one-season retrospective comparing what this map published against state advisory records is planned; until it runs, treat any agreement statistic you see quoted as being about the technique in general, not about this map.
Does Driftwise use cyanobacteria data in its monitoring platform?
Yes. Satellite cyanobacteria screening is one of more than a dozen federal inputs Driftwise watches on the waters a customer is responsible for, alongside USGS gauge readings, the National Water Model, drought classification, NOAA flood forecasts, wildfire proximity and EPA water quality designations. In the product a bloom reading is resolved to the specific access points and reaches a crew manages, so it becomes a factor in what a steward is told to do this week rather than a page somebody has to remember to check.
The other public maps.
Free, no-login maps built from the same federal data the Driftwise engines read.
Watershed Explorer
Click any point in the country and read what six federal datasets say about it — flow, drought, fire, flood forecast, satellite cyanobacteria screening and Clean Water Act impairment — each one labelled with what it is actually a fact about.
Wildfire & Smoke Map
Official NIFC fire perimeters and incident points under NOAA’s HRRR-Smoke near-surface forecast, filterable by size, state, and containment.
Streamflow Map
Every reporting USGS stream gauge in the country, coloured by how today’s flow ranks against that gauge’s own record for this calendar day.
U.S. Drought Map
The U.S. Drought Monitor — the country’s official weekly drought assessment — drawn across five severity categories from D0 to D4.
Flood Outlook Map
NOAA’s river forecast centres call the next few days at every forecast gauge in the country, on the National Weather Service’s own flood categories — action, minor, moderate and major.
Impaired Waters Map
Every subwatershed in the country against the states’ own Clean Water Act assessments — what is impaired, what is still on the 303(d) list, what is causing it, and how much of the country nobody has assessed at all.
Critical Habitat & Protected Waters Map
Every river and stream the federal government has designated as ESA critical habitat, the listed species each unit is designated for, and who manages the protected land around it.
One platform for three monitoring programs.
Run a mark-recapture program, coordinate a multi-partner invasive species response, or manage the waterway program for a state park or conservation nonprofit. Bring your own program to the demo and we'll run Driftwise on it, live.
Request a demoA free 30-minute working session with your data on screen.
Scope a pilot for your program.
Tell us about your program — a watershed, an infestation, a trail system. We'll walk through how a field record becomes the report your agency and funders sign off on.
A working call, not a pitch
We spend the time on your actual program — the data you have now and the report you owe.
Guided onboarding
We import your existing records and configure the setup alongside your team. Role-based in-product tours carry the rest of the crew after the call.
Start with one season
Run a single pilot first and expand when it earns the next watershed.
Send us your corridor, watershed, or program and we'll build the working demo around your records. We reply within one business day.
Click to reveal — we obscure the address to cut spam.