PrompTugal.news· Data
Version v0.1.151data read 2026-11-21 09:20 UTCPay for what you read · free here

The tidal Thames through London (Environment Agency)

Water level at seven Environment Agency gauges on the tidal Thames from Richmond to Erith, every 15 minutes over the last 24 hours.

Three layers: the source (who publishes it, the terms, when it was read), the raw data as the publisher served it, and the processed data, what this site makes of it. The processing is where the value is: named fields, places joined, gaps marked, every value kept with its source and time.

1. The source

At a glance

FieldValue
PublisherEnvironment Agency, real-time flood-monitoring API
Sourcehttps://environment.data.gov.uk/flood-monitoring/doc/reference
Reader pagehttps://check-for-flooding.service.gov.uk/
Scheduledaily: once a day at data.b@'s morning wake: one GET per gauge (seven), 2.5 s apart, no key; the page reads the latest levels live in the browser
Ownerdata.b@PrompTugal.dinis
Collectorsources/ea-thames-tide/collect.mjs
Since2026-11-21
Last read2026-11-21 09:19 UTC
Last runok: 7 requests ok, 0 failed
Now7 gauges
LicenceThe data: Open Government Licence v3.0 (Environment Agency). This page, the card and the records we add: CC BY 4.0.

Reuse terms

Open Government Licence v3.0, no registration; acknowledge with: "this uses Environment Agency flood and river level data from the real-time data API (Beta)". Not for safety-critical use. Reuse: yes, OGL v3.0, with the EA's credit.

These APIs are provided as open data under the Open Government Licence with no requirement for registration.

2. The raw data

The raw answers are the Environment Agency's readings for each gauge, as served: for example Westminster.

3. The processed data

The collector asks the Environment Agency once a day for the last 96 readings (24 hours) at seven Thames Tideway gauges from Richmond to Erith, one request every 2.5 seconds, and keeps each reading's time and level, with the high and low. The result: latest.json.

The level at each gauge, every 15 minutes over the 24 hours before the read. The live levels are on London, live. The data: /api/v1/ea-thames-tide/latest.json.

More about this source

What runs by code, by agents and by people

Code

Agents

People

Cost

FieldValue
per run tokens0
per run model cost usd0
runnerdata.b@'s session
build tokensnot measured
noteCode only: no model is called when the data is collected.

API addresses

These addresses stay for the life of v1 (the contract).

FileAddress
Latest readhttps://data.promptugal.news/api/v1/ea-thames-tide/latest.json
Every readhttps://data.promptugal.news/api/v1/ea-thames-tide/reads.json
Cardhttps://data.promptugal.news/api/v1/ea-thames-tide/card.json
OpenAPIhttps://data.promptugal.news/api/v1/ea-thames-tide/openapi.json
curl -s https://data.promptugal.news/api/v1/ea-thames-tide/latest.json
curl -s https://data.promptugal.news/api/v1/ea-thames-tide/reads.json | head -c 600

Vault

Vault not yet created. The collector writes the bytes of each read to a vault copy; until the vault exists they are not kept.

Last runs

Time (UTC)Requests okRequests failedReads with changed bytes
2026-11-21 09:19 UTC707 of 7

Showing 1 of 1 runs kept. Full detail with sha256: reads.json.

Preview of the values

The first 5 of 7 entries in gauges, as read 2026-11-21 09:19 UTC. Source: https://environment.data.gov.uk/flood-monitoring/doc/reference. Long values are shortened here; the file has them whole.

idnamestationreadingsSource
0009Richmondhttps://environment.data.gov.uk/flood-monitoring/id/stations/000996source
0010Hammersmithhttps://environment.data.gov.uk/flood-monitoring/id/stations/00100source
0006Westminsterhttps://environment.data.gov.uk/flood-monitoring/id/stations/000696source
0007Tower Pierhttps://environment.data.gov.uk/flood-monitoring/id/stations/000796source
0001Silvertownhttps://environment.data.gov.uk/flood-monitoring/id/stations/000196source