How it works

1. Camera data

We take a snapshot (Geofabrik US extract, October 16, 2026) of every OpenStreetMap node tagged surveillance:type=ALPR inside the 50 states + DC (144,253 nodes; this matches Geofabrik taginfo's US count minus a few hundred in territories/offshore). Much of this was mapped by volunteers using DeFlock. We don't add, verify or physically confirm any camera.

2. Your route

Place names are geocoded with Photon (OSM data), and driving routes come from the FOSSGIS OSRM server at routing.openstreetmap.de. If routing fails, we fall back to a straight line and say so. Your query goes from your browser straight to those services. We don't proxy, log or store it.

3. The estimate

We count mapped ALPRs within about 75 m (≈250 ft) of the route line. Where a camera has a mapped facing direction, we also estimate how many point toward oncoming traffic in your direction of travel (within ±60°). The 0–100 exposure index is 100 × (1 − e^(−readers per 10 mi ÷ 2)), an illustrative number and not a measurement.

Other layers

In the exposure index, ALPRs count fully, enforcement cameras ×0.5, traffic cameras ×0.3 and CCTV ×0.2. These weights are editorial choices, not measurements.

Not included (and why)

Limitations

Attribution & licenses

Camera and map data © OpenStreetMap contributors, licensed under the Open Database License (ODbL) 1.0. The derived camera file at /data/alpr.json is also offered under the ODbL. Basemap by OpenFreeMap / OpenMapTiles. Thanks to the DeFlock community. Further context: EFF Atlas of Surveillance.

See a missing camera? Add it to OpenStreetMap via DeFlock.

Estimate only. Based on publicly available, crowdsourced data (© OpenStreetMap contributors / DeFlock), which is incomplete and may be wrong. Many cameras, including mobile and commercial plate readers, are not mapped. This cannot tell whether you or your vehicle is being tracked. Not legal advice. Not for evading law enforcement or breaking any law. Provided as-is, with no warranty and no liability. Full disclaimer.