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
- ·Outcome data is behind icddr,b ethical approvalCRITICALstudy level
- ·Both daily VIIRS ERDDAP endpoints are dead from this netw…CRITICALdataset AL08
- ·icddr,b environmental archive needs IRB approvalCRITICALdataset AL26
- ·Matlab village ID key is effectively emptyCRITICALsite level
- ·ACOLITE is roughly 1 GB per scene and weeks of processingHIGHdataset AL18
- ·Needs a Copernicus Marine account and a Python toolboxMEDIUMdataset AL02
- +SPATIAL6 limitations · 3 critical
- +TEMPORAL7 limitations · 2 critical
- +ALGORITHMIC3 limitations · 1 critical
- +COVERAGE6 limitations · 1 critical
- +ATMOSPHERIC1 limitations
- +SPECTRAL2 limitations
- +PAPERSthe evidence, DOI-linked
CRITICAL Matlab village ID key is effectively empty access blocks Matlab
The vid field is populated in 8 of 251 records, and 251 polygons carry only 245 distinct village names with six names used twice. Neither an ID join nor a name join to the HDSS outcome data is safe.
What to do: Request the village-ID lookup table from icddr,b. Until it arrives, model at BLOCK level - seven units - and extract at village level anyway so nothing has to be redone later.