Cities and civic

Bangkok Flood Monitoring System.

Bangkok drainage and flood-monitoring surface with current flood-event, rainfall, canal-water, threshold, and forecast API routes exposed by the public app bundle. Useful for Bangkok-only route and city-friction context, not as a nationwide flood service.

Public Official public dashboard plus public API endpoints exposed by the city flood web app Free public Operational / event-driven Open source
Runtime role

Decision driving

Access class

Public

Access type

Official public dashboard plus public API endpoints exposed by the city flood web app

Free status

Free public

Cadence

Operational / event-driven

Last verified

2026-05-11

Access class note

Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.

Used in layers

source health, observation ingest, signal compute, decision compute

Useful fields

hazard type, severity/status, affected area, geometry/layer, timestamp, warning text, sensor/source, update time

Reliability rating

High for official context; validate endpoint availability before automation.

Runtime truth

Runtime role

Decision driving

Production ready

Yes

Entity scope

destination, district, street, transport_zone, hotel_area, attraction, route

Observation scope

bangkok_flood_current_event_count, bangkok_flood_max_level_cm

Decision scope

where_to_go_today, where_to_stay, route_check

Runtime note

Feeds active observations and signals that currently influence traveler-facing decisions.

How this helps travel recommendations

Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.

Endpoint and API notes

Bangkok drainage and flood-monitoring surface with current flood-event, rainfall, canal-water, threshold, and forecast API routes exposed by the public app bundle. Useful for Bangkok-only route and city-friction context, not as a nationwide flood service.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use official disaster feeds, hazard APIs, WMS/WFS layers, or event feeds; keep geometry and severity separate from the text summary.

Recommended refresh

Refresh every 15-60 minutes, with caching and backoff when the upstream fails.

Travel scoring role

Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.

Comparable / backup source

GISTDA, DDPM, GDACS, NASA FIRMS, USGS, TMD earthquake feeds, Thaiwater, and local authority announcements.

Example request

# Source landing or publication page; inspect linked documents or resources before automation.
curl -L "https://flood.bangkok.go.th/"

Failure modes

  • Hazard layers can be geospatial, tiled, or projection-specific.
  • Event feeds may lag official local announcements.
  • Dashboard-only layers may change markup or token behavior.
  • Dashboard markup or public-page layout can change without notice.

Last checked and source confidence

Last checked: 2026-05-11.

Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.