Best use for travel intelligence
For travel decisions, groundwater pages should say where the well is, what the historical lab context suggests, and why that still may not equal untreated drinking safety today.
Data cluster
Groundwater-well identity, slow-changing lab context, and suitability caveats for wells, aquifers, and drought-prone areas.
For travel decisions, groundwater pages should say where the well is, what the historical lab context suggests, and why that still may not equal untreated drinking safety today.
1 of 1 sources look official or agency-backed.
1 sources expose API, feed, CKAN/DataStore, JSON, XML, or similar machine-readable access.
0 sources have live, hourly, event-driven, warning, or frequent update language.
Store well identity, coordinates, use class, and slow-changing lab context separately, and avoid presenting historical groundwater samples as live potability proof.
Last checked: 2026-05-11.
Source confidence: This cluster is strongest when several sources describe the same traveler problem from different angles: official context, machine-readable feeds, and slower fallback documentation.