Network panel
Algae Dataset
Every data hub, dataset, sensor, variable, paper and limitation in one tree — and for each: where it comes from, how far back it goes, how often it captures, why it belongs in a cholera study, and why it does not work everywhere.
Highlight site
All three
Chakaria HDSS
Matlab HDSS
Dhaka City
Choosing a site greys out everything that does not apply there.
- +DATA HUBSwhere the data physically comes from
- +DATASET TYPESgrouped by what kind of water they see
- +SITE-WISEwhat actually applies at each site
- +DURATION & CAPTURE CADENCEdaily · weekly · 10-day · 16-day · monthly
- +VARIABLESwhat is computed from the bands
- −LIMITATIONSwhy not — typed and severity-ranked
- +VALIDATION2 limitations · 1 critical
- +ACCESS6 limitations · 4 critical
- +SPATIAL6 limitations · 3 critical
- −TEMPORAL7 limitations · 2 critical
- ·Record starts mid-2015 - two-thirds of the study window i…CRITICALdataset AL03
- ·OCTS and CZCS predate the study periodCRITICALdataset AL21
- ·The 2015 sensor discontinuityHIGHstudy level
- ·16-day revisit misses short blooms entirelyHIGHdataset AL05
- ·Mission ended December 2010HIGHdataset AL07
- ·Monthly cadence cannot resolve a two-week bloomMEDIUMdataset AL01
- ·PACE launched 2024 - a very short recordMEDIUMdataset AL15
- +ALGORITHMIC3 limitations · 1 critical
- +COVERAGE6 limitations · 1 critical
- +ATMOSPHERIC1 limitations
- +SPECTRAL2 limitations
- +PAPERSthe evidence, DOI-linked
HIGH 16-day revisit misses short blooms entirely temporal
One Landsat satellite passes every 16 days. A bloom that initiates, peaks and collapses inside two weeks can fall entirely between two passes and leave no trace in the record.
What to do: Two satellites in orbit halve the effective interval to about 8 days. Combine L7+L5 for 2000-2012 and L8+L9 for 2021 onward. Report bloom FREQUENCY with an explicit detection-probability caveat.