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
- +ALGORITHMIC3 limitations · 1 critical
- −COVERAGE6 limitations · 1 critical
- ·Dhaka has almost no pre-2015 algae observationCRITICALsite level
- ·Copernicus LWQ300 lake mask may exclude all three sitesHIGHdataset AL09
- ·Landsat 7 SLC-off stripes after May 2003HIGHdataset AL05
- ·IRI is a strong climate archive but a thin ocean-colour o…HIGHdataset AL17
- ·Multiple testing across the lag gridMEDIUMstudy level
- ·Dhaka polygon is a GADM level-3 unit labelled TejgaonMEDIUMsite level
- +ATMOSPHERIC1 limitations
- +SPECTRAL2 limitations
- +PAPERSthe evidence, DOI-linked
MEDIUM Dhaka polygon is a GADM level-3 unit labelled Tejgaon coverage blocks Dhaka
Dhaka_City.shp has NAME_3 = 'Tejgaon' but an extent of 17.6 x 26.0 km, which is city-scale rather than thana-scale. It works fine as a city AOI, but the label is misleading.
What to do: Describe it in the manuscript as a Dhaka city bounding polygon with the extent stated - not as Tejgaon thana.