Skip to content
All engineering use cases

Groundwater data UK

Review monitored groundwater levels alongside borehole logs and soil moisture context. Compare listed sources, access requirements and evidence for groundwater data uk.

4 sources · For drainage engineers, ecologists, flood consultants, geotechnical engineers, GIS analysts, hydrologists. Enrichment describes potential applications; review source evidence and limitations.

Soil moisture is supporting context rather than a groundwater level; boreholes may lack monitoring records.

Discover sources with MCP

Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "ea-hydrology-api"
  }
}

Listed sources

data api
65/100Currency C

EA Hydrology API ↗

Hydrological station metadata and quality-labelled flow, level, groundwater and rainfall time series.

What's in it

Data offered docs-verified
river flow 15-min instantaneous (m3/s) · river flow daily mean/min/max (m3/s) · river level 15-min instantaneous (m) · river level daily min/max (m) · rainfall 15-min total (mm) · rainfall daily total (mm) · groundwater level dipped (mAOD) · groundwater level logged, sub-daily (mAOD) · water quality 15-min instantaneous: dissolved oxygen (% and mg/L), fDOM (RFU), blue-green algae (RFU), turbidity (NTU), chlorophyll (µg/L), conductivity (µS/cm), temperature (°C), ammonium (mg/L), nitrate (mg/L as N), pH
Coverage llm-inferred
England
Resolution docs-verified
typically 15 min (sub-daily) and daily
Formats docs-verified
JSON · CSV · GeoJSON · HTML · RDF/XML · Turtle
Access llm-inferred
No authentication (per catalogue); free; Open Government Licence 3.0

Useful for

Use cases llm-inferred
FRA baseline flows and levels from nearest gauge · Rainfall and river level context for flood event review · Groundwater level baseline for site investigation or geotechnical assessment · Water quality baseline (dissolved oxygen, turbidity, nitrate) for ecological or pollution assessment
Audience llm-inferred
flood consultants · hydrologists · drainage engineers · ecologists · geotechnical engineers · GIS analysts

Limitations

Constraints docs-verified
Hard limit of 2,000,000 rows per call that cannot be overridden; soft limit of 100,000 rows per call (overridable with _limit) · Hard limit is subject to review and may be reduced if the service is overloaded · Bulk downloads should use the batch API; otherwise keep to one non-batch request in flight at a time · Concurrency limits may be enforced per IP address, and excessive demand may lead to blocking · Logged groundwater sub-daily values may mix 15-min and hourly intervals · Station identifiers are not always unique; some stations need a composite key with a wiskiID · HTML views are intended for debugging and development, not for presentation to consumers
hydrology

Englandpage reachable

Frequently asked questions

Which listed sources support Groundwater data UK?

Start with EA Hydrology API, BGS OGC API Features, BGS Geoindex. Review monitored groundwater levels alongside borehole logs and soil moisture context.

What should I check before using these sources for groundwater data uk?

Soil moisture is supporting context rather than a groundwater level; boreholes may lack monitoring records.

How do I inspect EA Hydrology API through MCP?

Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug ea-hydrology-api. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.

Are these sources free and independently verified?

Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.