Downloads
Download the place and state tables
The figures on the place and state pages are here as files, so you can sort them, chart them or put them on a map of your own. They are free to use as long as you credit the sources.
Data built on , updated weekly.
The files
locateflock-places.csv
One row for each place where 10 or more license plate cameras are mapped: how many there are, how close they are to the rest of the place, and how they are spaced.
CSV, 2,395 rows, 220 KB
Download locateflock-places.csvlocateflock-states.csv
One row for each state with a mapped camera, plus the District of Columbia and Puerto Rico: the totals for the whole of it, inside a place or not.
Its rows add up to 143,491, not 143,570: 79 mapped cameras sit just past a coast or a border as the simplified state outlines draw it, or in a territory without a row of its own, so only the national total includes them.
CSV, 52 rows, 3 KB
Download locateflock-states.csvlocateflock-places.geojson
The places table again, as one point per place for a map or a GIS program. Each point sits inside the place's boundary and carries the same columns.
GeoJSON, 2,395 features, 917 KB
Download locateflock-places.geojson
Each CSV opens with one line of licence notice, and the column names are on the second line. In a spreadsheet the notice is row 1. In code, skip that line: skiprows=1 in pandas, skip = 1 in R’s read_csv. Every field is quoted, lines end in CRLF and the text is UTF-8. An empty field means the value is not known.
Rows are in the order of their identifiers, so two downloads taken on different dates can be compared line by line.
Columns in the places files
The CSV and the GeoJSON carry the same 14 columns under the same names. In the GeoJSON they are the properties of each point, and a value that is not known is null.
| Column | What it holds |
|---|---|
| geoid | The Census Bureau's identifier for the place: two digits for the state, then five for the place. Read it as text, because it can start with a zero. |
| place | The name of the place as the Census Bureau writes it. |
| state | Two-letter postal code of the state the place is in. |
| cameras | License plate cameras mapped inside the place's boundary. A floor: a camera nobody has mapped is not counted. |
| flock_ | How many of those cameras have Flock Safety recorded as their maker. |
| typical_ | Median straight-line distance, in metres, from a point inside the boundary to the nearest mapped camera. That camera can be of any maker and can stand just outside the boundary. |
| p90_ | The 90th percentile of the same measurements, in metres: nine tenths of the place is closer to a mapped camera than this. |
| pct_ | Percent of the area inside the boundary that lies within 400 metres (about a quarter of a mile) of a mapped camera. |
| pct_ | Percent of the area inside the boundary that lies within 800 metres (about half a mile) of a mapped camera. |
| median_ | Median distance, in metres, from a camera in the place to the nearest other camera in it. |
| cameras_ | Cameras with another mapped camera within 60 metres, which usually means one pole or one intersection. |
| population_ | Residents counted in the 2020 Census. Empty where there is no count for the place. |
| cameras_ | Mapped cameras for every 10,000 residents counted in 2020. Empty where there is no population count. |
| has_ | true if Locate Flock has a page for the place, false if it does not. |
Columns in the states file
| Column | What it holds |
|---|---|
| code | Two-letter postal code. |
| state | The name of the state, district or territory. |
| cameras | License plate cameras mapped anywhere in the state, inside a place or not. A floor, like every count here. |
| places_ | Census places in this state that have at least one mapped camera. |
| pct_ | Percent of the state's mapped cameras that stand inside an incorporated city, town or village. |
| median_ | Median distance, in metres, from a camera in the state to the nearest other camera in it. |
| population_ | Residents counted in the 2020 Census. |
| cameras_ | Mapped cameras for every 10,000 residents counted in 2020. |
Licence and credit
Camera locations are © OpenStreetMap contributors and come under the Open Database License (ODbL) 1.0. These tables are worked out from that data, so the same licence applies to them. Each file says so in its first line.
In practice that asks two things of you. Credit OpenStreetMap contributors wherever you publish something made from the files, and say that the data is under the ODbL. And if you publish a database built from them, release it under the ODbL too. That is a summary in plain words, not legal advice: the licence itself is what counts.
Place boundaries and the 2020 population counts come from the U.S. Census Bureau. A credit to Locate Flock is welcome and not required.
How to cite
The numbers move as volunteers add and correct pins, so give the data date with anything you quote. This line has it:
Locate Flock, “Mapped license plate cameras by US place and state: distance, proximity and spacing,” https://locateflock.com/downloads. Data dated October 2, 2026. Source data © OpenStreetMap contributors, under the Open Database License.
Before you use the numbers
- Mapped is not verified. Every camera behind these tables is a point that a volunteer added to OpenStreetMap. Nobody at Locate Flock has been to see it, and a pin can be misplaced, out of date or the wrong kind of camera.
- Counts are floors. A camera that nobody has mapped is in no file, so the real number in a place is the mapped number or more. Do not read a low count as proof of few cameras: it may only mean few mappers.
- Distance is all that is measured. The distance and area columns say how near a mapped camera is. They say nothing about which way it points, what it records or whether it is working.
- Lines are straight and rounded. Distances are straight-line metres rounded to the nearest 10, measured from a grid of points inside each boundary. Shares of area are whole percentages.
- Population is from 2020. Cameras per 10,000 residents sets today’s map against the residents counted in the 2020 Census.
The method page explains how each figure is measured, step by step.
Looking for individual cameras?
These files hold one line per place or state, not one per camera. To see single cameras, open the map or search near an address.
If you need every point as data, take it from the source. In OpenStreetMap each camera is a node carrying the tag surveillance:type=ALPR, and the Overpass API will return them for any area you ask about.