Flock Cameras Map: 28 Maps of License Plate Readers and CCTV
Flock and other license plate readers across the US, state by state and city by city, plus Japan's N-System, UK ANPR, German scanners and CCTV.
Updated
Plate readers are mapped by the people who drive past them. The largest map here holds
74,777 cameras sorted by maker; most others cover one city or county, built from
public-records spreadsheets or from walks with a phone, often noting which way each
camera faces. Start with the national maps, then look for your state or city further
down; at the end come Japan, Britain, Germany and Brazil.
The biggest plate-reader map in the index sorts its 74,777 points into three layers,
one per maker: Flock, Motorola and Avigilon. The cameras often stand in clusters of
three or four at one intersection, one per lane or direction. Around Olathe in Johnson
County, Kansas, the Motorola units carry notes as exact as “Angled to capture Middle
and Outer WB lanes” and “Captures all NB Outer lane traffic”. Made in uMap by
McKenzieF, it covers the whole country and a few points abroad.
5,878 plate readers, all added in a single week, 6 to 13 August 2026, from Louisiana to
Puerto Rico. lonestead’s notes read like a file on each camera: in Lewisboro, New York,
“No record of Town Approval”, a state grant, “report of 2 year Data Retention”; at
Detroit Metro Airport, readers on the “Ramp to international arrivals level from
south”; a second reader “at main entrance of Lowes Cookeville TN”.
Objects
5,8785,878 points
Countries
United StatesPuerto RicoVirgin Islands, U.S.and 1 more
A crowd-sourced Flock map with layers for Georgia, Ohio, Texas, Wisconsin and Lake
County, Florida, and an invitation to send in locations and photos. The Georgia
entries around Warner Robins say where each camera looks: “Facing South East after
the Toyota Dealer entrance”, one “Attached to Speed Camera Pole. Tracking West
Bound.”, one “on Moveable LED Sign”, and one with “flock painted on sidewalk in front
of camera”.
EastValleyUnite mapped 1,890 reported surveillance cameras across the Phoenix metro,
“Flock camera, facing South on the west side of Ironwood” among them, and laid
city outlines over them with the state of each contract. Chandler: “Flock contract
cancelled.” Tempe: contract “expires in September 2027; will not be renewed.” Surprise:
“Officer misused ALPR data”, cameras suspended, contract terminated. Each city links
the news story of August 2026.
Along the US–Mexico border, plate readers come in disguise. The “Covert ALPR” layer
holds 95 units numbered COVERT001 onward, most of them inside construction barrels,
others in sand-filled crash barrels and trailers, starting east of Calexico with the
direction of traffic each one reads. Around them: 124 readers at checkpoints and ports
of entry, 45 face-recognition crossings sourced to CBP, 598 surveillance towers and the
radar balloons at Yuma, Fort Huachuca, Deming and Marfa.
A “living inventory” of Seattle’s cameras, each kind in its own layer: red-light
cameras by approach (“EB NE 45th St and Roosevelt Way NE”), SDOT’s “Block the Box” and
transit-lane plate readers downtown, SDOT and WSDOT traffic cameras, and police CCTV
marked “precise locations need verification”. Polygons add what the cameras serve: the
SODA and SOAP zones of 2025 and “Dragnet Zones” from Aurora (85th to 145th) to
Chinatown-International District.
Japan’s police plate readers, the N-System, mapped terminal by terminal: those wired
to the National Police Agency, four regional layers of the simplified units and the
road ministry’s AVI travel-time readers, updated in October 2026. Each entry
gives prefecture, road, direction, model and lanes read, and what the unit is mounted
on, often “parasitic” on a traffic sign, signal or detector pole. Moved units keep
their old spot: “before relocation 35.40948,139.62557” on the Tokyo Bay road in Yokohama.
DeFlockSF splits San Francisco’s Flock cameras into those of the police and those
bought privately, with the police readers outnumbering the private ones. A
third layer holds something few maps have: two “SFPD Flock Drone Pad” sites, one near
Potrero Hill and one near Glen Park, where the police launch drones.
lonestead asks a pointed question of the plate-reader data: which readers stand next
to gun stores, shooting ranges and smoke shops? Two layers answer, 208 points at smoke
shops and 71 at gun stores. The notes name the hardware, from a
“Verkada Bullet Series” in Tucson to a “Hardwired Flock PTZ 360” in Fort Smith and one
“Attached to Shell station sign”.
759 readers across Connecticut, each titled with its bare coordinates and noted with
its owner and mount: “Putnam PD”, “Stonington PD Pole Mount”, “Norwich PD Street Lamp
Mount”, “West Hartford PD Traffic Signal Mount”, and a “Lowe’s Pole Mount”. Extra
layers place the state’s court houses, hospitals, immigration attorneys and
reproductive health clinics, so you can see which cameras stand near them.
The Kansas City metro by county, from Johnson (140 cameras) and Jackson (100) to Cass
(2), with the vendor of nearly every site. Genetec readers line 75th Street,
“All directions” at many crossings, Vigilant Systems watches “119th & I-35”, and at Scheels the
note reads “5 FLOCK systems in total, all facing in towards the parking lot”.
Britain’s fixed number-plate cameras, made as part of a campaign against mass
surveillance. The list begins in Northern Ireland, with gantries on the M1 at
Dungannon (“Set of 6 cameras both East and Westbound”) and Sprucefield, then works
through Belfast street by street: Grosvenor Road, Divis Street, Queens Bridge, Belfast
City Airport, and Belvoir Road, where the camera is “Almost hidden in the trees”.
Every title starts with a code for the traffic it reads: (E), (W), (N), (S), or (GI)
for cars going in. At University Park Mall in Mishawaka four “(GI)” readers watch the
entrances; on IN 23 one reader catches “cars going north into Michigan”; one is marked
“(MISSING)”. Layers run from Northwest Indiana and Indianapolis to the toll road, with
Raven gunshot detectors and a layer of unverified spots.
kfinity mapped Richmond, Virginia, in three layers: plate readers, some with a link to
the Leonardo ELSAG Street Sentry, “Ravens”, Flock’s gunshot detectors, and “Possible
Locations”. That last layer keeps the uncertain ones honest, “Harwood St #2?” and
“Missing 1 somewhere along North Ave”.
Journalism students at the University of Nevada, Reno, catalogued what campus police
use, for a report with the EFF: plate readers, body cameras, drones, face recognition.
The plate-reader entries come with numbers. In 2018 the University of Maryland police
scanned 8,765,641 plates and Towson University 3,676,764, from six fixed sites with ten
cameras; Florida State’s readers turn up in the vendor’s own promotional material.
Southeastern Wisconsin’s Flock cameras as the cities listed them in answer to
open-records requests, one layer per spreadsheet: Waukesha and Kenosha, West Allis and
Beaver Dam, Milwaukee, Pleasant Prairie, Greenfield, Germantown and more. Each camera
keeps its number and the city’s own “Intersection or address”, such as “SE Appleton
Ave and County Line Road”.
135 readers in the Sierra foothills, from Rocklin and Roseville up to Grass Valley,
Auburn, Yuba County and Truckee, each with the way it faces. The maker goes back to
check: in Grass Valley one reader on East Empire is “Gone as of 1/17/23. Probably
moved to Empire x Whiting St”, where a camera now “Faces east toward Empire Mine”;
another on East Main is “Missing, probably moved to Manor Dr”.
Five public lists in one map: Oakland’s and the CHP’s Flock cameras along I-880,
Berkeley’s readers numbered with the direction each one reads (camera 01, “EB” on
Ashby Ave at Seventh St), El Cerrito’s city list, the Port of Richmond, and Richmond’s
Flock Falcons, a layer marked “WIP there are many, many more”.
Germany’s automatic plate scanners on the autobahn, worked out site by site: 14
verified, seven from published sources, six suspected positions, one former site and
eleven checked routes. The notes describe how they are hidden, “Unter
Brückenvorsprung versteckt” on the A6 at Waidhaus, and reason like detectives: the A13
site at Großräschen “fits no previous pattern”, since it would need two extra scan units.
Sources run from netzpolitik.org’s 2013 list for Brandenburg to Patrick Breyer’s photos.
Little Rock in three layers: 115 plate readers, many marked “Flock License Plate
Reader”, 57 police surveillance cameras and 31 ShotSpotter gunshot sensors, the
sensors clustered in the blocks around Fair Park Boulevard and South Fillmore Street.
One police camera “is placed on the Marriott Hotel”.
The same direction codes as the Indiana map, applied to Chicagoland’s suburbs, where
many readers watch shopping centres: “(GI)” and “(GO)” pairs read cars going in and out
of North Riverside Park Mall, and another catches “all east bound traffic into Orland
Square Dr, Mall”. Two smaller layers hold red-light cameras and a Raven gunshot
detector.
Where the plate-reader documents came from. Each point is a request filed by Dave
Maass through MuckRock and marked “Completed”, most of them titled “2018 Vigilant Data
Sharing Information”: which agencies a police department shares its plate-reader data
with, from Bakersfield and the Austin Regional Intelligence Center to Ball Ground,
Georgia, and Beachwood, Ohio.
Dallas police cameras numbered one by one and described by the corner they hang on: “360
degree police cam on signal pole on SE corner”. The maker watched them change: Cam 2
“gone as of 3/25/15. Camera back as of 10/25/15.” The plate-reader layer notes each
scanner is “tied to 1 year of storage”; others cover private readers and Fort Worth.
Curitiba’s city cameras sorted by what they can do, each type with its code: MDAR
high-resolution, MDRF facial recognition, MDRPV plate recognition, MDP panoramic and
three MDT thermal cameras, “Monitoramento Digital Térmico”. Further layers hold the
older SIMM traffic and security CCTV and the cameras at the city’s tube stations,
terminals and Praça Rui Barbosa.
The doorbell side of the camera network: 358 US cities and counties whose police
joined Amazon Ring’s Neighbors program, each with its source, a police news page, a
local report or a tweet, from Addison, Illinois, to Anne Arundel County. Some entries
keep Ring’s own verification line: “Text ‘alexandriava’ to 555888 to verify”.
Which agency uses what, in Alameda, Contra Costa, San Francisco, Sonoma and Solano
counties: body cameras, plate readers, camera networks, camera registries, drones and
gunshot detection, each entry with vendor, summary and a source. Much of it was found
in plain sight: Cloverdale, Concord and Danville police are identified by the Axon Body
2 cameras officers wear on their Facebook pages.
A small-city map keyed to one numbering: “Flock #1 - Velp Av. and Military Av.”, #9 and
#10 at East Mason and Bellevue, #12 and #13 on Lombardi Avenue by the stadium. The
maker warns the list may be incomplete.
A campus where cameras come with coverage: 118 “Camera Ranges” polygons drawn around
78 dome cameras, 44 blue-light cameras and 14 fixed CCTV units at
the University of Maryland. They are named by building, from the Chemistry Dome Camera
to “The Diner Dome Cam 2” and the Center for Young Children.