Current page call
Turn Mekong and transboundary water-quality monitoring into a clear page for heavy-metal, nutrient, and river-risk interpretation.
4 source layers
2026-05-09 updated
Scope matters
Water-quality intelligence
Mekong Water Quality.
Mekong pages should separate basin-scale monthly monitoring, incident-driven heavy-metal testing, and local Thai advisories so regional risk is not overstated or understated.
Before you book
Use the Water page with the current trip checks
This water page is not claiming a page-specific current score. Use it as the static guide, then check Today, route, and comparison pages before paying for anything hard to change.
Decision fields
A strong water page says what the source can prove, what it cannot prove, and which water type or standard is actually being discussed before someone trusts a tap, river, beach, or groundwater claim.
| Field | Answer |
|---|---|
| Page type | transboundary-water guide |
| Primary use | Turn Mekong and transboundary water-quality monitoring into a clear page for heavy-metal, nutrient, and river-risk interpretation. |
| Updated | 2026-05-09 |
| Core caveat | incident data is event-specific |
- Mekong context
- heavy-metal events
- transboundary risk
- incident data is event-specific
- regional reports are not local household water tests
- MRC Mekong water quality
- Pollution Control Department water quality
- Thaiwater WaterQuality API
- Department of Health drinking water standards
Canonical record checklist
Waterbody type, station ID, station coordinates, parameter values and units, observation time, WQI or MWQI scope where relevant, threshold source, water-use class, alert status, method, quality flag, source URL, confidence, and last verified date. Swim, tap, raw-water, wastewater, and groundwater interpretations should stay in separate fields.
Station
Threshold
Use