Rivers, tap water, beaches, groundwater, and wastewater
Thailand water-quality intelligence only works when river, canal, tap, groundwater, beach, marine, wastewater, industrial, and standards layers stay separate. Use the Pollution Control Department for national surface-water quality, automatic stations, marine water quality, and wastewater context; Thaiwater for multi-agency near-live station observations; MWA and PWA for tap-water and raw-water monitoring; the Department of Groundwater Resources for wells and groundwater context; Bangkok open data for canal and Chao Phraya urban monitoring; DMCR, GISTDA, and Copernicus for coastal and ocean-condition context; DIW and PCD for industrial-effluent boundaries; MRC for Mekong and transboundary monitoring; and Department of Health plus FDA standards for potable and bottled-water thresholds.
Current trip check
The page below is still useful without JavaScript. When current checks are available, this panel points you to the Today, comparison, and route pages that matter before committing.
Showing static water planning links until the latest check is available.
Use this order when river stations, tap-water dashboards, coastal proxies, standards, and industrial monitoring all appear to be talking about the same place.
| Rank | Source layer |
|---|---|
| 1 | PCD, Thaiwater, MWA, PWA, DGR, and BMA for official Thai surface-water, tap-water, groundwater, and urban-water monitoring truth. |
| 2 | DMCR, GISTDA, Copernicus Marine, and other marine or satellite products for coastal-condition, bloom, sediment, and proxy context that supports but does not replace field sampling. |
| 3 | PCD wastewater and DIW monitoring surfaces for wastewater-treatment and industrial-effluent context, with explicit limits on public facility-level visibility. |
| 4 | MRC for transboundary Mekong and regional water-quality context when basin-scale metals, nutrients, or solids matter more than one local station. |
| 5 | Department of Health and FDA standards for interpreting potable-water and bottled-water limits without pretending standards pages are live monitoring feeds. |
These rules keep WQI, tap water, raw water, beaches, groundwater, wastewater, industrial effluent, and satellite proxies from collapsing into one misleading record.
| Rule | Meaning |
|---|---|
| 1 | WQI and MWQI are not the same thing as live water-safety today; they summarize field or sampling cycles and must be kept separate from automatic-station telemetry. |
| 2 | Tap water, raw-water intake, river water, canal water, groundwater, marine water, wastewater, and industrial effluent are different products with different standards and use cases. |
| 3 | Satellite chlorophyll, turbidity, or suspended-matter products are proxies, not microbiological swim-safety proof. |
| 4 | Groundwater-well records and historical lab results do not prove present untreated drinking suitability at the tap. |
| 5 | Industrial and wastewater monitoring systems exist, but public facility-level realtime access is usually partial or restricted. |
| 6 | The same station or waterbody can appear under different agency names, codes, languages, and coordinate precision. |
| 7 | Heavy-metal incidents are often event-driven and sampling-based, not stable realtime API fields. |
Each layer answers a different question. A river WQI trend is not a live safe-today feed, a raw-water salinity alert is not a finished tap-water failure, a marine satellite proxy is not a bacteria test, and a standards page is not an observation feed.
Thailand river intelligence needs national WQI, station telemetry, basin context, and sampling cadence kept separate so recent observations do not get confused with slower index scores.
WQI is not realtime Bangkok tap waterMWA, PWA, and standards pages answer different questions: what the finished tap water looks like, what the raw intake looks like, and what thresholds define potable-water compliance.
raw water is not finished tap water well lookupGroundwater pages should separate well identity, aquifer context, older lab results, and present drinking suitability so a historical well record does not overstate safety.
lab data is slower Bangkok canalsBangkok canal and Chao Phraya layers explain urban water stress, salinity intrusion, and WQI context, but they are not a simple beach-style safe-or-unsafe signal.
urban monitoring is mixed cadence beach cautionCoastal pages need field-sampled marine quality, local advisories, and satellite proxies kept separate so bloom or turbidity signals do not masquerade as a same-day bacteria answer.
satellite is not swim safety wastewater contextMunicipal wastewater, treatment capacity, public effluent-control guidance, and industrial monitoring systems belong together only if their public-access limits stay explicit.
facility-level visibility is restricted Mekong contextMekong monitoring and potable-water standards help explain heavy-metal incidents, regional water-risk interpretation, and what threshold a traveler or researcher should compare against.
incident sampling is event-drivenThese pages turn the source model into usable tap-water, river, canal, beach, marine, groundwater, wastewater, and Mekong guidance.
Bangkok tap-water pages should separate finished tap-water quality, raw-water salinity intrusion, potable-water standards, and the limits of public station coverage.
Bangkok tap water / salinity watch urban-water guideBangkok canal pages should use BMA and PCD context to show urban pollution, WQI, and Chao Phraya pressure without pretending canal data is a swim-safety feed.
Bangkok canals / urban context river guideChao Phraya pages need automatic stations, WQI, salinity intrusion, and Bangkok river context separated so trend scores and recent sensor values do not blur together.
river quality / salinity alerts beach-water guideBeach-water pages should combine marine/coastal sampling, local advisories, and satellite proxies while clearly warning that chlorophyll and turbidity are not the same thing as bacteria tests.
beach caution / swim planning destination water guidePhuket water pages should separate beach and marine quality, island raw-water pressure, wastewater context, and broad coastal proxies rather than implying one island-wide score.
island beaches / coastal caution destination water guideSamui pages need coastal proxies, beach caution, potable-water caveats, and island infrastructure limits kept visible rather than reduced to a generic beach-safe claim.
island beaches / resort planning destination water guideKrabi water pages should combine Andaman coastal sampling, turbidity and sediment proxies, and potable-water caveats without collapsing mainland and island conditions.
Andaman trips / coastal caution river guideChiang Mai river pages should lean on river WQI, Thaiwater observations, and standards rather than forcing northern river condition into a beach or tap-water template.
northern rivers / river context transboundary-water guideMekong pages should separate basin-scale monthly monitoring, incident-driven heavy-metal testing, and local Thai advisories so regional risk is not overstated or understated.
Mekong context / heavy-metal events groundwater guideGroundwater pages should separate well identity, slow-changing lab context, present treatment needs, and location confidence so a mapped well is not mistaken for safe potable water.
well lookup / groundwater contextUse the Pollution Control Department for national surface-water quality, automatic stations, marine water quality, and wastewater context; Thaiwater for multi-agency near-live station observations; MWA and PWA for tap-water and raw-water monitoring; the Department of Groundwater Resources for wells and groundwater context; Bangkok open data for canal and Chao Phraya urban monitoring; DMCR, GISTDA, and Copernicus for coastal and ocean-condition context; DIW and PCD for industrial-effluent boundaries; MRC for Mekong and transboundary monitoring; and Department of Health plus FDA standards for potable and bottled-water thresholds.