Flood disruption evidence for Thailand logistics teams
Review warehouse and delivery access using source-dependent flood evidence, historical extents and Bangkok monitoring-station metadata.
Which warehouse access points need an operational check?
Keep a review queue of depot access points near reported flood evidence, with timestamps and source status. Confirm road passability with local operators before changing dispatch plans; a mapped report does not guarantee a road is closed or open.
Review workflow
- List depot gates and critical road segments with coordinates and the dispatch team's own identifiers.
- Retrieve flood evidence for a small viewport and inspect its timestamp, source and freshness status rather than treating every item as current.
- Use historical extents as contingency-planning context and station locations as references for follow-up; the station catalog has no current readings.
- Ask an operator to confirm access, record that confirmation separately and apply your own dispatch escalation procedure.
What to produce
A depot-access review queue separating public observations, historical context and operator-confirmed road conditions.
| Dataset | Coverage and cadence | Sources and licences | Limitations |
|---|---|---|---|
| Current flood evidence Experimental | Source-dependent observations in Thailand; BMA feeds cover Bangkok Source-dependent; checked about hourly Marked stale after 6 hours; unavailable after 7 days | Bangkok DDS legacy road-flood telemetry Bangkok DDS KlongMap canal water levels | Experimental, source-dependent observations (reports, road state, rainfall, water level). Coverage and cadence vary by source; an empty viewport does not mean no flooding. |
| Flood history Beta | Published UNOSAT observation extents in Thailand Fixed historical archive Historical or versioned data; no real-time freshness claim | UNOSAT / United Nations Satellite Centre (Thailand flood extents) | A fixed archive of historical satellite flood-extent observations (UNOSAT). It is not a real-time flood map, and absence of an extent is not evidence that an area stayed dry. |
| Water monitoring stations Experimental | Bangkok monitoring locations Station catalog checked about hourly Historical or versioned data; no real-time freshness claim | Bangkok DDS legacy road-flood telemetry Bangkok DDS KlongMap canal water levels | Experimental catalog of monitoring-station locations and metadata (rainfall, flow, canal level, road flood). It does not contain current readings. |
| Thailand basemap Stable | Thailand Versioned releases; no fixed public cadence Historical or versioned data; no real-time freshness claim | Basemap geometry, not analysis data. It is drawn from vector tiles and is not a completeness claim about any feature on the ground. |
Questions this data cannot answer
The Atlas is not a nationwide live road-closure service and does not automatically feed closures into routing. Coverage is source-dependent; an empty response is not an all-clear signal.
Try a bounded data request
Read-only, no key required, limited to 100 features in the stated viewport. An empty response can indicate missing coverage. Read the response timestamps, sources and status before use.
curl --fail-with-body 'https://api.mapscale.io/v1/public/atlas/layers/flood-evidence?bbox=100.4%2C13.6%2C100.9%2C14.1&limit=100'Relevant geographic context
Inspect source-backed public examples
Use these references to inspect source identity, timestamps and limits. They do not establish coverage for every location in your project.
Prepare a pilot with your team
For a depot pilot, choose gates and routes your team can verify locally. Agree freshness and escalation rules, and track how many public observations receive operator confirmation before considering dispatch integration.
Scope a data pilot with MapScale →
Workflow documentation by MapScale, using the linked dataset contracts for sources and limitations. Report source discrepancies through our contact channel. Your team remains responsible for domain review and approval.