Public disaster and road-access planning data for Thailand

Support public disaster coordination with flood evidence, Bangkok monitoring locations, reference boundaries and mapped road context.

How can agencies share a common public evidence picture during planning?

Combine source-labelled flood observations, reference administrative boundaries and mapped access context into a public planning brief. Police, military support teams and local authorities still confirm conditions and act through their official command procedures.

Review workflow

  1. Define the planning area and responsible administrative units using reference boundaries, retaining the agency's official jurisdiction records.
  2. Collect source-dependent flood observations and record freshness, missing coverage and the observation time for each item.
  3. Use Bangkok station metadata to identify monitoring locations and mapped roads to frame access questions; request readings and confirmations from the responsible authority.
  4. Share a dated brief showing verified agency reports separately from public observations and route unresolved access questions to local teams.

What to produce

A public coordination brief with source-labelled observations, administrative references and a list of access questions requiring official confirmation.

Available evidence and its limits
DatasetCoverage and cadenceSources and licencesLimitations
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

Floodboard
CC BY 4.0

Bangkok DDS legacy road-flood telemetry
BMA reuse permission (confirmed by the data owner to the operator on 2026-09-27)

Bangkok DDS KlongMap canal water levels
BMA reuse permission (confirmed by the data owner to the operator on 2026-09-27)

Experimental, source-dependent observations (reports, road state, rainfall, water level). Coverage and cadence vary by source; an empty viewport does not mean no flooding.
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
BMA reuse permission (confirmed by the data owner to the operator on 2026-09-27)

Bangkok DDS KlongMap canal water levels
BMA reuse permission (confirmed by the data owner to the operator on 2026-09-27)

Experimental catalog of monitoring-station locations and metadata (rainfall, flow, canal level, road flood). It does not contain current readings.
Administrative boundaries

Stable

Thailand

Versioned reference release

Historical or versioned data; no real-time freshness claim

Boundaries: RTSD / UN OCHA COD-AB
CC BY 3.0 IGO

Boundaries are the COD-AB reference set for Thailand. They are a cartographic aid, not a legal or cadastral boundary.
Thailand basemap

Stable

Thailand

Versioned releases; no fixed public cadence

Historical or versioned data; no real-time freshness claim

© OpenStreetMap contributors
ODbL 1.0

Natural Earth
Public domain

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

No classified, tactical, real-time force-location or authoritative operational-command data is provided. The catalog cannot certify road safety, evacuation routes or current water readings; official agency instructions take precedence.

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/water-stations?bbox=100.4%2C13.6%2C100.9%2C14.1&limit=100'

Water monitoring stations →

Foundation API documentation →

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 an agency pilot, define public jurisdiction records, the planning area and the official confirmation contact. Agree an update procedure, missing-source flags and approval responsibilities before operational use.

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.