Atlanta's camera map and its police audit measure different things.

1,318 records within the stated circle—not 1,318 APD devices

The snapshot was retrieved at 13:54 UTC on October 3, using a reference center of 33.7490, −84.3880 and a 10-mile (16.1-km) radius. It includes 1,201 Flock-attributed records and 117 other or unattributed ALPR records. The data supplies headings for 1,309 records and last-verification dates for none.

This circle extends beyond the center of Atlanta and does not follow the municipal boundary. The database can contain public and private deployments. A source manufacturer label does not identify the owner, the agency with access or the agencies that have searched the system.

Near the reference point, one entry at 33.7489252, −84.3892124 is labeled Genetec. Another at 33.7485133, −84.3866268 is labeled Flock Safety. Keeping those labels separate is a practical check against turning every plate reader into a Flock count. No field observation was performed for this report.

Atlanta coverage page and selected records · Inspect the Genetec-labeled record · Inspect the Flock-labeled record

What APD said on September 14

On September 14, 2026, Atlanta Police published a statement about its review of license-plate-recognition policies and system use. APD said it had revised its policy, established monthly auditing, provided refresher training and strengthened access controls. The department also said some inquiry patterns required further investigation. Those are the department's published statements, not findings independently verified by FlockDetour.

An audit of searches answers who used a system and whether that use followed policy. A map inventory answers where someone documented hardware. One cannot validate the other. This report does not attach APD's audit conclusions to all 1,318 records or assume that APD operates them.

Useful follow-up evidence would include the current policy, subsequent audit reports, documentation of the review's outcome and a dated agency-owned equipment inventory. The September statement alone does not establish whether a later investigation is complete. Check the linked primary source for updates before repeating its status.

APD's September 14 review statement and attachment · Questions to ask about ALPR audit logs

How we counted—and what the date means

FlockDetour retrieved public camera records on October 3, 2026, selected the ALPR camera class, excluded records marked removed, and measured a 10-mile (16.1-km) circle from the stated reference point. Overlapping query results were deduplicated by record ID. Larger query boxes were split when the server result limit was reached; these three reported city snapshots had no unresolved result cap.

A record ID identifies a database entry, not necessarily a distinct pole or physical device. Nearby entries can describe different viewing directions, separate devices or duplicates. Flock attribution follows the source vendor label; other and unidentified vendors stay separate. The results do not establish who owns each device, whether it is operating or whether a particular vehicle would be captured.

The retrieval date is when we read the database. It is not an installation date, a field visit or a last-seen date. None of the records in these three snapshots supplied a last-verification date. Source corrections and removals can change a later count without a new installation or physical removal occurring that day.

Camera sources and attribution · Why camera-map counts disagree

Three checks before repeating an Atlanta camera total

First, identify the area: this 10-mile circle, Atlanta city limits and metro Atlanta are different boundaries. Second, identify the unit: source records, physical devices, network access and searches are different measurements. Third, identify the date and whose evidence supports it. A recently fetched old record has not become a newly verified camera.

For route planning, inspect the mapped records along the actual path. Road directions, incomplete mapping and changed installations constrain every estimate. FlockDetour publishes this report as the app maker and does not claim independent product validation or a camera-free route.

Compare camera-map tools and their scope

Related guides

Why do Flock camera maps show different counts? · DeFlock, FlockHopper and FlockDetour compared · How to request your city's Flock audit logs · All guides · Live camera map · Get the app