Water-quality intelligence

Groundwater in Thailand.

Groundwater 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.

Current page call

Explain how DGR well data and groundwater-quality context should be interpreted for drinking, drought, and rural-water pages.

3 source layers 2026-05-09 updated Scope matters

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.

TodayCurrent destination calls and weak signals. CompareSide-by-side destination evidence. Route checkTransfer risk, weak legs, and pivots. Source notesOpen the receipts when you want to inspect them.

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	groundwater guide
Primary use	Explain how DGR well data and groundwater-quality context should be interpreted for drinking, drought, and rural-water pages.
Updated	2026-05-09
Core caveat	wells are not automatic drinking approval

Best for

well lookup
groundwater context
rural water planning

Watch

wells are not automatic drinking approval
groundwater quality data is slower

Useful sources

Department of Groundwater Resources wells
Department of Health drinking water standards
Thaiwater WaterQuality API

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