Water and hydrology

DIW water pollution monitoring.

Factory monitoring layer for parameters such as BOD, COD, flow, and related compliance signals in industrial contexts. Treat it as regulated operational infrastructure, not open national water-quality data.

Restricted Online pollution monitoring system surface for industrial air and water pollution monitoring System exists publicly on the web, but practical facility-level access is role-gated and not a public bulk feed Operational / near real time where authorized Open source
Runtime role

Catalog only

Access class

Restricted

Access type

Online pollution monitoring system surface for industrial air and water pollution monitoring

Free status

System exists publicly on the web, but practical facility-level access is role-gated and not a public bulk feed

Cadence

Operational / near real time where authorized

Last verified

2026-05-11

Access class note

Exists and matters, but direct operational access is limited to authorized users or agencies.

Used in layers

page reference only

Useful fields

waterbody, station, timestamp, parameter code, value, unit, method, quality flag, WQI/MWQI, salinity, pH, turbidity, DO, BOD, conductivity, residual chlorine, bacteria, heavy metals, source threshold

Reliability rating

Medium-high for discovery and context; operational reliability depends on endpoint stability.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

How this helps travel recommendations

Turns water data into source-backed decisions about river condition, Bangkok tap-water confidence, raw-water salinity intrusion, beach caution, groundwater caveats, wastewater context, and whether a warning is really about tap, river, marine, or industrial water.

Endpoint and API notes

Factory monitoring layer for parameters such as BOD, COD, flow, and related compliance signals in industrial contexts. Treat it as regulated operational infrastructure, not open national water-quality data.

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

Developer reference

Best endpoint

Use PCD and Thaiwater for river and station observations, MWA/PWA for tap or raw-water dashboards, DGR for wells, PCD/DMCR for marine and coastal sampling, and standards pages separately for interpretation rather than observation.

Recommended refresh

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

Travel scoring role

Turns water data into source-backed decisions about river condition, Bangkok tap-water confidence, raw-water salinity intrusion, beach caution, groundwater caveats, wastewater context, and whether a warning is really about tap, river, marine, or industrial water.

Comparable / backup source

PCD, Thaiwater, MWA, PWA, DGR, BMA, DMCR, GISTDA, Copernicus Marine, MRC, DIW, Department of Health, and FDA.

Example request

# Verify the documented water endpoint before production use.
curl -L "https://poms.diw.go.th/" -H "Accept: application/json"

Failure modes

  • There is no single all-water-quality Thailand API.
  • WQI and MWQI are not realtime safe-today feeds.
  • Tap water, raw water, groundwater, river water, marine water, wastewater, and industrial effluent use different thresholds and cadences.
  • Satellite proxies such as chlorophyll or turbidity do not prove microbiological swim safety.
  • Public industrial-effluent visibility is limited and often role-gated.
  • The same station can appear under different agency names, IDs, and coordinate precision.

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.