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

London road disruptions (TfL)

Works, incidents and closures on London's roads as TfL lists them: severity, category, place, TfL's description and the period.

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
PublisherTransport for London (TfL), Unified API
Sourcehttps://api.tfl.gov.uk/
Reader pagehttps://api-portal.tfl.gov.uk/
Scheduledaily: once a day at data.b@'s morning wake: one GET of api.tfl.gov.uk/Road/all/Disruption, no key; the page reads it live in the browser
Ownerdata.b@PrompTugal.dinis
Collectorsources/tfl-road-disruptions/collect.mjs
Since2026-11-21
Last read2026-11-21 09:20 UTC
Last runok: 1 requests ok, 0 failed
Now112 disruptions
LicenceThe data: TfL Transport Data Service terms (OGL v2.0 based) (Transport for London). This page, the card and the records we add: CC BY 4.0.

Reuse terms

TfL's Transport Data Service terms (based on the Open Government Licence v2.0 with TfL amendments): free to copy, publish, distribute, transmit and adapt the information and to exploit it commercially and non-commercially; credit "Powered by TfL Open Data"; at most 500 calls a minute per feed; no implied endorsement. Reuse: yes, with the credit "Powered by TfL Open Data"; commercial use allowed.

You are free to: Copy, publish, distribute and transmit the Information; Adapt the Information and Exploit the Information commercially and non-commercially

2. The raw data

The raw answer is TfL's road disruption list (about 250 KB), kept in the vault copy: the address.

3. The processed data

The collector reads TfL's road disruptions once a day and keeps each one's id, severity, category, place, description, period and position; a field our wording check refuses is dropped and counted. Powered by TfL Open Data. The result: latest.json.

Each disruption with its severity, category, place and period at the read. The live list is on London, live. The data: /api/v1/tfl-road-disruptions/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/tfl-road-disruptions/latest.json
Every readhttps://data.promptugal.news/api/v1/tfl-road-disruptions/reads.json
Cardhttps://data.promptugal.news/api/v1/tfl-road-disruptions/card.json
OpenAPIhttps://data.promptugal.news/api/v1/tfl-road-disruptions/openapi.json
curl -s https://data.promptugal.news/api/v1/tfl-road-disruptions/latest.json
curl -s https://data.promptugal.news/api/v1/tfl-road-disruptions/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:20 UTC101 of 1

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

Preview of the values

The first 5 of 112 entries in disruptions, as read 2026-11-21 09:20 UTC. Source: https://api.tfl.gov.uk/. Long values are shortened here; the file has them whole.

idseveritycategorysub_categorystatuslevel_of_interestSource
TIMS-224034MinimalWorksBorough worksActiveMediumsource
TIMS-238466MinimalEmergency service incidentsPolice activityActiveMediumsource
TIMS-238465ModerateWorksConstruction activityActiveHighsource
TIMS-237961MinimalWorksUtility worksActiveLowsource
TIMS-238443MinimalWorksCollaborative worksActiveLowsource