OpenStreetMap — camera locations ↗
Primary coordinate layer. We use records tagged as speed cameras within the UK boundary. Source fields can be missing or stale. Data is available under the Open Database Licence (ODbL).
Provenance before claims
Data Sources & Methodology
Every layer answers a different question. Source, date, scope and limitation remain visible so a static estimate is not mistaken for a live reading.
Department for Transport — road traffic statistics ↗
Annual average daily flow (AADF) at count-point level. A camera is matched to the nearest appropriate point. Source years vary by point, with records through 2024 in this snapshot.
Department for Transport — STATS19 road safety open data ↗
Police-reported personal-injury collisions. The current map uses the final 2024 dataset and labels it by year; it is not live collision information.
How records are matched
Camera coordinates are normalised from a versioned OpenStreetMap-derived snapshot. AADF is taken from the nearest matched DfT count point and collision context uses a 500-metre radius. Geographic aggregates deduplicate collision identifiers before counting.
Coverage and page scope
The national map contains every record in the snapshot. A dedicated city, county or road page is published only when the area has at least three mapped records and enough distinct data to support the page.
What the map does not claim
The map does not call every point active, treat annual traffic as live congestion, infer missing speeds, claim a camera changed collision outcomes or publish mobile-camera schedules without a timestamped source.
Machine-readable provenance is available in source metadata, with reuse terms in the data licence notice.