Every license plate camera in Milton, Georgia, mapped

55 inside the city limits, 138 more just outside the line, exactly where people have pinned them. Readers have since found 2 more that nobody had pinned. They are on the map, marked as reported. A security researcher's snapshot of Flock's own device records lists 20 more that nobody had pinned. They are on the map too, marked. The city says it runs 36, keeps the data for a year, and is investigating two of its own searches as possible misuse. The gap between the counts is explained below the map.

  • Inside Milton (55)
  • Just outside the line (138)
  • Reported by a reader, confirmed (2)
  • In Flock’s own records, Dec. 2025 (20)
  • City limits

Not on this map: the city’s 3 mobile cameras and its 39 patrol cars, which move. The map does not record who owns a pin, so it cannot say whether all 33 of the city’s fixed cameras are among the 55 inside the line.

Added September 16, 2026: Lake Haven entrance, Freemanville Road at Hipworth Road; Bethany Bend at the side entrance to the CVS at Highway 9. Readers reported them and we confirmed each on Google Street View. Not pinned on OpenStreetMap yet, so not in the counts above. Know another? tips@readroundabout.com.

Added October 5, 2026: 20 plate readers that Flock’s own device records listed as in service on Dec. 14, 2025, in a snapshot published by security researcher Joshua Michael (Flock Surveillance Map). Half are at neighborhood entrances, and four are at schools. None is pinned on OpenStreetMap, so they are not in the counts above, and we have not yet confirmed each on the ground. The same records list the city’s three mobile cameras, which move, so they stay off the map. See one that’s gone, or one we still missed? tips@readroundabout.com.

Tap a dot for what was recorded about it. Points: OpenStreetMap contributors and DeFlock (ODbL). Boundary: City of Milton GIS. Base map: OpenStreetMap.

Fly over every camera A 50-second 3D drone tour of all 55, ringed in gold. Then you take the controls.

The numbers

as of September 12, 2026, sourced line by line

On the map
55 license plate cameras pinned inside Milton's city limits OpenStreetMap and DeFlock, Sept. 12
138 more pinned within about a mile and a quarter of the city line OpenStreetMap and DeFlock, Sept. 12
1 in 750 residents per pinned camera. At the city's own count, one for every 1,150; with the patrol cars, one for every 550 Census Bureau, July 2025 estimate, 41,266 residents
What the city runs
36 Flock cameras the city says it operates: 33 fixed, 3 mobile Milton Police, on the record, Sept. 11
39 marked patrol cars with license plate reading on board Milton Police, Sept. 11
15 private camera owners, neighborhoods and businesses, whose cameras Milton police can search Milton Police, Sept. 11
What happens to the data
2 matters under investigation as potential misuse, after the department reviewed its own officers' searches. Both remain open. Milton Police, on the record, Sept. 11
365 days the city keeps what its cameras record. It was 30. Georgia allows up to 30 months; Flock's new default is 7 days Milton Police, Sept. 11; O.C.G.A. 35-1-22; Flock, Aug. 13

Why 55 and 36 are both true

The 36 are the city’s. The 55 are everything a DeFlock contributor has spotted and pinned on OpenStreetMap inside the line, including cameras that neighborhoods, businesses and Fulton County Schools bought for themselves. The city says it can search 15 of those private feeds. A pole with two cameras can be pinned twice, and a camera can come down after it was pinned. Treat 55 as a floor with error bars. Of the 55, 54 are tagged Flock Safety.

What the city says

  • “Data collected by the City’s Flock cameras is currently searchable for 365 days. Milton previously used a 30-day retention period.”
  • “Not every search receives advance approval or individual supervisory review. All searches are logged.”
  • “Authorized law enforcement agencies outside Georgia can access Milton-collected data depending on the City’s sharing settings.”
  • “The Department reviewed search activity and identified two matters that warranted further investigation as potential misuse. Both matters remain under investigation.”
  • The cameras are not watched live, take still images rather than video, and are not used for moving violations.

Lt. Andrew Noblett, Milton Police Department, written answers to The Roundabout, September 11, 2026. Our reporting.

All 14 answers, printed as written

Lt. Andrew Noblett answered our written questions on the record on September 11 at 4:04 p.m. His answers are below, unedited. Our questions are shortened. Six follow-up questions went to the department on September 12; the answers go here when they come.

The August 19 traffic stop

  1. How was the 911 call classified, and what was the basis for the stop?

    Dispatch classified the call as a civil dispute on the roadway, a call type commonly described by the Department as a road-rage incident. The 911 call originated in Forsyth County and was transferred to Alpharetta 911 as the vehicles entered Milton. The caller reported that a vehicle had followed him for at least 15 minutes over multiple roads and turns and said he did not want to stop while the vehicle remained behind him. Officers did not know before making contact that the other driver was a journalist. An officer stopped the vehicle to investigate the caller’s report.

  2. Why did three units respond?

    This was a moving call involving two vehicles whose locations were changing. Officers approached from different directions so they could locate the vehicles and obtain separate accounts from both drivers. Additional officers eventually arrived. The initiating officer did not request emergency backup. The response reflected the call type, the changing locations and the need to speak with both drivers.

  3. The stop ran about 17 minutes. What was the basis for its length?

    The stop began at approximately 3:05 p.m. About five minutes later, the initiating officer contacted the officer who was speaking with the caller. At approximately eight minutes, she advised that she was obtaining the caller’s account and would then release the driver. She returned the driver’s license and ended the detention at approximately the 10-minute mark. As you’ll see in the recording, the remaining interaction was a voluntary conversation in which the driver continued to ask questions and engage. No citation was issued.

  4. Does the department have guidance for officers on encounters with the press?

    The Department has policy governing media relations and officers’ interactions with lawful newsgathering at incident scenes. This encounter arose from a call concerning the driver’s conduct, rather than from his presence as an observer covering an incident. Officers did not know before contact that he worked in the news media. A person’s occupation is immaterial to an officer’s investigation of an incident as described by the caller.

  5. Is there a policy for responding to calls from a vendor’s employees or contractors?

    No. No vendor-specific response policy or special protocol applied to this call. Officers assess calls based on the information reported, the call type, the location, available personnel and any public-safety considerations.

  6. The city has paid Flock Safety $341,235.62 since our records begin in October 2020. Does that relationship carry any obligation or expectation about responding to Flock personnel?

    No. The contractual relationship does not give Flock personnel priority, special standing or a different police response. The Department has no standing instruction to provide Flock employees or contractors special treatment.

  7. Did the department review the encounter?

    Yes. The Department reviewed the encounter. The review found that officers did not know before contact that the driver was a journalist; the response was based on the caller’s report; and the officer returned the driver’s license at approximately the 10-minute mark after obtaining the caller’s account. The remaining recorded interaction was voluntary. The officers were professional, and no citation was issued.

The camera program

  1. Are the department’s 2022 statements still accurate: still photographs, not video; not used for moving violations; not monitored around the clock?

    Yes. The cameras are not watched live around the clock, nor can they be. They capture still images and associated vehicle data rather than continuous video, and the Department does not use them to enforce moving violations.

  2. How many plate reader cameras does the city operate, and can police search cameras the city does not own?

    The City operates 36 Flock readers: 33 fixed units and three mobile units. Automated license plate reader capability is also available on 39 marked Police Department vehicles. Milton users may search data shared by participating law-enforcement agencies and by private camera owners who separately authorize access. The City currently has 15 data-sharing connections with private residential and commercial entities. That sharing is one-way-private owners do not gain access to City data.

  3. Who can run a search, and does a supervisor review it?

    Authorized users are Milton-certified officers and designated crime-intelligence personnel. Each authorized user has an individual account. Searches must serve a legitimate law-enforcement purpose and include the required case, CAD or purpose information. Not every search receives advance approval or individual supervisory review. All searches are logged. Flock’s audit-assistance tool flags specified searches for review, and a three-member Department audit team reviews those alerts.

  4. Does Milton take part in Flock’s national lookup network, and can agencies outside Georgia search Milton’s cameras?

    Yes. Milton participates in Flock’s data-sharing program, and authorized law enforcement agencies outside Georgia can access Milton-collected data depending on the City’s sharing settings and the requesting agency’s authorization.

  5. Has the department audited its own searches, and what did it find?

    Yes. The Department reviewed search activity and identified two matters that warranted further investigation as potential misuse. Both matters remain under investigation.

  6. What does the plate reader “hit validation” service in the city’s checkbook pay for?

    If this question refers to Goldshield, that service supported the City’s system by validating information against the GCIC/NCIC network. The City has discontinued that service.

  7. How long does the city keep plate data?

    Data collected by the City’s Flock cameras is currently searchable for 365 days. Milton previously used a 30-day retention period and extended it as part of a program upgrade to support investigations in which a lead may not emerge immediately. Milton does not host that data.

The camera policy, every version

The police department’s written rules for its license plate readers, as the city produced them on Oct. 21, 2026, in answer to our records request (PRR-533). Georgia law requires every agency that uses plate readers to keep such a policy, including how officers are trained: O.C.G.A. 35-1-22.

  • Oct. 15, 2026 Data kept up to 365 days. The only change from August.
  • Aug. 26, 2026 Adds monthly audits by a three-member team, automatic suspension for abnormal use and a flag on every emergency search. Data kept up to 30 days.
  • July 24, 2025 Data kept up to 30 days. A case number or other identifier on every search.
  • Nov. 30, 2022 Data kept up to 30 months.
  • March 21, 2019 Data kept 30 months.
  • General Order 3.3.30, Aug. 15, 2018 The original plate-reader order, first issued March 1, 2017. Data kept 30 months.

The rules vs. the record

What Georgia law, the Milton Police Department and Flock say the rules are for Milton’s Flock cameras, side by side with what the records show. Every cell links to its source.

  • 5 gaps
  • 2 with no records
  • 1 withheld

Last updated Oct. 22, 2026 · What changed

The rule coversGeorgia lawMilton police rulesFlock’s rules
How long your data is kept Meets Up to 30 months is allowed. Milton keeps data 365 days. O.C.G.A. 35-1-22(b) Gap The written policy said 30 days while the city kept data 365 days, for at least 10 months. The Oct. 15 rewrite made it 365. Policy, July 2025Policy, Oct. 15, 2026Our Oct. 15 story Gap Keeping data a year requires approval “from an elected official and/or a governing body.” The City Council never voted on it. Flock’s evidence policy, p. 6Our Oct. 17 story
Who can see your data Can’t tell Law enforcement agencies only. Milton’s list includes “Flock Safety - Machine Learning Test,” which its page doesn’t explain. O.C.G.A. 35-1-22(c)Milton’s Flock page Gap Its Flock page limits sharing to agencies in Georgia and federal partners that work there. Its own list of 391 includes Indiana HIDTA and “Puerto Rico live cameras.” Milton’s Flock pageDepartment’s answer, Sept. 18Our Oct. 15 story City’s call Flock says only the agency decides who sees its data. Milton’s 2022 contract also gives Flock a “perpetual” license to share it with police for investigations. Milton’s Flock pageContract, section 4.1
Immigration enforcement No rule None found Its Flock page bars it. No immigration agency is on its list, and no Milton search in the logs gives that reason. Milton’s Flock pageHow we counted City’s call Flock says it doesn’t work with ICE and leaves sharing to each agency. Flock on ICE
Traffic enforcement Meets State law allows searches to investigate traffic offenses. O.C.G.A. 35-1-22(a)(3) and (a)(4) Gap Its Flock page bars traffic enforcement, and the department told us it doesn’t use the cameras “to enforce moving violations.” Thirteen logged searches cite speeding, nine of them “speeders” on Oct. 6, 2025. The written policy does allow plate readers “to detect violations of law.” Milton’s Flock pageAnswers, Sept. 11Policy, July 2025How we counted Allowed Flock’s list of search reasons includes “Traffic Infraction.” Milton officers chose it 109 times from December 2025 to July 2026. How we counted
Searches only for police work Questioned The department found two possible misuse cases. No charges are known. Answers, Sept. 11O.C.G.A. 35-1-22(d) Questioned Its Flock page bars personal use and harassment. The same two cases. Milton’s Flock pageOur Oct. 15 story Questioned Milton’s contract allows use only to gather evidence for “a lawful criminal investigation.” Contract, section 2.4
What the cameras read Covered State law’s limits cover “any other data” the cameras capture, not just plates. O.C.G.A. 35-1-22(a)(2) Silent Every policy version describes reading plates only. Its Flock page says the system also identifies body type, color, roof racks, bumper stickers and damage. Every policy versionMilton’s Flock page No face ID Flock says its cameras don’t use facial recognition or identify people. Milton’s 2024 order lists “Vehicle Fingerprint” machine learning and a search for “suspect vehicles that frequently travel together,” which Milton officers have run at least 23 times. Milton’s Flock page2024 order, features pageHow we counted
How close a match counts No rule Silent Set at 75% for the state and 25% for the plate number, and any sworn officer or crime analyst can change it during a search. No policy version mentions it. Department’s answer, Sept. 25Every policy version Not published Flock hasn’t published its default. Its training material says the system is “set to a high confidence level,” and it says most reads score above 95%. Business Insider, March 9, 2026
A case number on every search No rule Gap Required since 2018. About 9 in 10 logged searches from 2023 to May 2026 had none. General Order, 2018Our Oct. 13 story Not yet Optional since July 2025. Flock says it will require case codes for all searches by the end of 2026. Flock, Aug. 13, 2026
Audits of officers’ searches No rule No records Monthly audits required since Aug. 26, and its federal data-sharing agreement requires audits too. The city says none exist outside Flock’s audit tool, and it withheld that tool’s history. Policy, Aug. 26, 2026The city’s answers In use The department says Flock’s audit tool flags searches for review. Flock says the tool will be required for every agency by the end of 2026. What the city saysFlock, Aug. 13, 2026
Officer training On paper The policy must cover training. Milton’s does. O.C.G.A. 35-1-22(e)Policy, Oct. 15, 2026 No records The city says it has no training records for the officers who hold Flock accounts. The city’s answers No rule
Monthly reports No rule Withheld Required since 2018. The city withheld them, citing the state law that shields plate data. General Order, 2018The city’s answers No rule

How to read it. “Gap” means the records show practice and the rule differ. “No records” means the city says none exist. “Withheld” means the city has the records and won’t release them. “Questioned” means the department itself flagged possible misuse. “Can’t tell” means the records don’t settle it. “Milton police rules” are the department’s written policy, the page it posted on Flock’s site in October and what it has told us. We don’t call any of this a violation; that is for prosecutors, courts and the city. Share the Oct. 21 graphic.

How we counted

Search counts come from Flock audit logs that other police agencies released under their own records laws. Each log shows the Milton searches that reached that agency’s cameras, so one search can appear in several logs; we counted each once, by its time. The logs run from 2022 to July 2026. They are a floor, not a total: a search that stayed on Milton’s own cameras never reaches them. Since Dec. 18, 2025, Flock has logged a category of offense rather than a typed reason; “Traffic Infraction” is one of those categories. No Milton search reason in the logs mentions immigration, ICE, customs, Border Patrol or Homeland Security.

The sharing list, the prohibited uses and the description of what the cameras identify are from the department’s Flock transparency page, read Oct. 21, 2026. Flock can change that page without notice.

What the department and the city told us, in their words

Lt. Andrew Noblett, written answer, Sept. 18, 2026, on sharing:

The City has recently changed its sharing configuration. Milton’s Flock data is now limited to law enforcement agencies within the State of Georgia. This represents approximately 800 law enforcement agencies within Georgia.

Lt. Noblett, written answer, Sept. 25, 2026, on the match-confidence setting:

The Department’s current default search match-confidence settings are 75% for the issuing state and 25% for the license plate number. All sworn police officers and crime intelligence analysts are authorized to adjust these settings when conducting a search. Search results are investigative leads and are not treated as conclusive identifications. Department personnel must independently verify the information returned by the system before taking any further law-enforcement action.

Lt. Noblett, written answer, Sept. 25, 2026, on the federal data-sharing agreement:

The Police Department has entered into a Memorandum of Understanding with the HIDTA License Plate Reader Integration Project. The agreement establishes a framework for sharing selected license plate reader data with our federal and state partners for legitimate law enforcement purposes.

The city’s answers to our records requests, Oct. 21, 2026:

  • Monthly plate-reader reports: withheld under O.C.G.A. 35-1-22(f), the law that shields captured plate data.
  • The audit team’s members, start date and review log: they “do not exist.”
  • The review history in Flock’s audit tool: withheld under the same law.
  • Training records for the officers who hold Flock accounts: they “do not exist.”
  • Audits required by the federal data-sharing agreement: they “do not exist.”
  • The list of agencies Milton’s older plate-reader system shared with: withheld under the same law.

We asked for administrative records, not plate data.

What changed
  • Oct. 22, 2026. Published, adapted from our Oct. 21 Facebook graphic, with a row on how close a plate match must be and a source for every cell. The graphic was corrected the night it ran: it had said Flock has required case numbers since August 2026, and that Flock has no rule on police-only use.

Our coverage

Elsewhere

Why we published the locations

These cameras face public roads and photograph the public, and their positions were already public on OpenStreetMap and DeFlock. A resident asked Council on September 9 how many there are and where. The city gave the count. This is the where. Wrong dot, or one we missed? tips@readroundabout.com, and we will fix it and say so.

Questions people ask

How many Flock cameras are in Milton, Georgia?

The city says it operates 36 Flock cameras, 33 fixed and 3 mobile, plus license plate reading on 39 patrol cars (Milton Police, September 11, 2026). Separately, 55 license plate cameras are pinned inside the city limits on the DeFlock map. The difference is cameras owned by neighborhoods, businesses and Fulton County Schools, and some double counting.

Where are the license plate cameras in Milton?

On the map above, exactly where DeFlock contributors pinned them on OpenStreetMap as of September 12, 2026: 55 inside the city limits and 138 just outside. The city's 3 mobile cameras and 39 patrol cars move and are not on it.

How long does Milton keep license plate camera data?

365 days, up from 30, according to Milton Police on September 11, 2026. Georgia law allows up to 30 months. Flock's default for new customers is seven days.

Who can search Milton's license plate data?

Milton officers and designated crime-intelligence staff, each with an individual account; agencies outside Georgia, depending on the city's sharing settings. Not every search gets advance approval. All searches are logged, and a review of them found two matters now under investigation as potential misuse.

Table view: all 195 points
#Inside MiltonTagged makerZoneMounted onFacingPinnedSource
1 yes Flock Safety traffic camera pole 60° 2024-12-17 OSM node
2 yes Flock Safety traffic camera pole 200° 2025-02-17 OSM node
3 yes Flock Safety traffic camera not tagged 38° 2026-07-12 OSM node
4 yes Flock Safety not tagged not tagged 44° 2025-11-21 OSM node
5 yes Flock Safety traffic camera pole 310° 2024-12-31 OSM node
6 yes Flock Safety traffic camera pole 350° 2024-12-17 OSM node
7 yes Flock Safety traffic camera pole 30° 2025-02-13 OSM node
8 yes Flock Safety not tagged not tagged 4° 2025-11-21 OSM node
9 yes Flock Safety traffic camera light pole 135° 2024-12-17 OSM node
10 yes Flock Safety traffic camera not tagged 211° 2026-06-24 OSM node
11 yes Flock Safety traffic camera pole 350° 2025-01-07 OSM node
12 yes Flock Safety traffic camera pole 160° 2025-01-07 OSM node
13 yes Flock Safety traffic camera not tagged 41° 2026-04-02 OSM node
14 yes Flock Safety traffic camera not tagged 82° 2025-12-02 OSM node
15 yes Flock Safety traffic camera pole 240° 2025-02-13 OSM node
16 yes Flock Safety traffic camera moveable mount/speed limit sign 27° 2026-06-11 OSM node
17 yes Flock Safety traffic camera not tagged 53° 2025-12-02 OSM node
18 yes Flock Safety traffic camera pole 340° 2025-02-17 OSM node
19 yes Flock Safety traffic camera not tagged 57° 2026-05-20 OSM node
20 yes Flock Safety traffic camera not tagged 64° 2026-07-26 OSM node
21 yes Flock Safety traffic camera not tagged 266° 2026-07-26 OSM node
22 yes Flock Safety not tagged not tagged 350° 2025-11-21 OSM node
23 yes Flock Safety (operator: Fulton County Schools) not tagged pole not tagged 2025-05-26 OSM node
24 yes Flock Safety traffic camera not tagged 266° 2026-06-16 OSM node
25 yes Flock Safety traffic camera not tagged 315° 2026-05-13 OSM node
26 yes Flock Safety traffic camera not tagged 0° 2026-05-13 OSM node
27 yes Flock Safety traffic camera pole 90° 2024-12-17 OSM node
28 yes Flock Safety traffic camera not tagged 277° 2026-08-07 OSM node
29 yes Flock Safety traffic camera not tagged 66° 2026-04-19 OSM node
30 yes Flock Safety traffic camera not tagged 239° 2026-06-11 OSM node
31 yes Flock Safety traffic camera not tagged 47° 2026-03-16 OSM node
32 yes Flock Safety traffic camera pole 120° 2024-12-31 OSM node
33 yes Flock Safety traffic camera pole 189° 2026-09-04 OSM node
34 yes Flock Safety traffic camera not tagged 324° 2026-05-20 OSM node
35 yes Flock Safety traffic camera not tagged 281° 2025-12-01 OSM node
36 yes Flock Safety traffic camera pole 140° 2024-12-17 OSM node
37 yes Flock Safety traffic camera pole 250° 2024-12-17 OSM node
38 yes not tagged (operator: Flock Safety) public area pole 228° 2024-12-12 OSM node
39 yes Flock Safety traffic camera not tagged 98° 2025-12-01 OSM node
40 yes Flock Safety traffic camera pole 250° 2025-02-26 OSM node
41 yes Flock Safety traffic camera not tagged 45° 2026-06-07 OSM node
42 yes Flock Safety traffic camera not tagged 45° 2026-06-07 OSM node
43 yes Flock Safety traffic camera not tagged 76° 2026-06-07 OSM node
44 yes Flock Safety traffic camera not tagged 166° 2026-07-24 OSM node
45 yes Flock Safety traffic camera pole 280° 2025-02-14 OSM node
46 yes Flock Safety traffic camera not tagged 75° 2025-11-19 OSM node
47 yes Flock Safety traffic camera pole 90° 2025-02-14 OSM node
48 yes Flock Safety traffic camera not tagged 318° 2026-05-16 OSM node
49 yes Flock Safety traffic camera not tagged 76° 2025-11-19 OSM node
50 yes Flock Safety traffic camera not tagged 84-129° 2025-12-07 OSM node
51 yes Flock Safety traffic camera not tagged 84-129° 2025-12-07 OSM node
52 yes Flock Safety traffic camera not tagged 84-129° 2025-12-07 OSM node
53 yes Flock Safety traffic camera not tagged 198-243° 2025-12-07 OSM node
54 yes Flock Safety traffic camera not tagged 173° 2026-06-07 OSM node
55 yes Flock Safety traffic camera not tagged 173° 2026-06-07 OSM node
56 no Flock Safety traffic camera not tagged 70° 2026-04-14 OSM node
57 no not tagged (operator: Flock Safety) traffic camera not tagged 260° 2024-12-13 OSM node
58 no Flock Safety traffic camera not tagged 172° 2025-11-20 OSM node
59 no Flock Safety traffic camera not tagged 172° 2025-11-20 OSM node
60 no Flock Safety not tagged not tagged 90° 2025-09-19 OSM node
61 no Flock Safety traffic camera not tagged 261° 2026-06-09 OSM node
62 no Flock Safety traffic camera pole 155° 2024-12-17 OSM node
63 no Flock Safety not tagged not tagged 120° 2025-10-09 OSM node
64 no not tagged (operator: Flock Safety) traffic camera not tagged 90° 2024-12-17 OSM node
65 no Flock Safety traffic camera pole 220° 2024-12-17 OSM node
66 no not tagged (operator: Flock Safety) traffic camera not tagged 90° 2024-12-13 OSM node
67 no not tagged (operator: Flock Safety) traffic camera not tagged 245° 2024-12-17 OSM node
68 no Flock Safety (operator: The Home Depot) traffic camera not tagged 181° 2025-11-20 OSM node
69 no Flock Safety traffic camera pole 340° 2024-12-30 OSM node
70 no Flock Safety not tagged not tagged 230° 2025-10-09 OSM node
71 no not tagged (operator: Flock Safety) traffic camera not tagged 270° 2024-12-13 OSM node
72 no Flock Safety traffic camera pole 320° 2024-12-30 OSM node
73 no Flock Safety (operator: Flock Safety) traffic camera pole 260° 2024-12-17 OSM node
74 no Flock Safety traffic camera not tagged 206° 2025-12-31 OSM node
75 no Flock Safety traffic camera pole 70° 2025-01-02 OSM node
76 no Flock Safety traffic camera not tagged 343° 2025-12-31 OSM node
77 no Flock Safety traffic camera not tagged 191° 2026-01-03 OSM node
78 no Flock Safety traffic camera pole 220° 2025-01-02 OSM node
79 no Flock Safety traffic camera not tagged 282° 2026-06-22 OSM node
80 no not tagged (operator: Flock Safety) traffic camera not tagged 25° 2024-12-13 OSM node
81 no not tagged (operator: Flock Safety) traffic camera not tagged 25° 2024-12-13 OSM node
82 no Flock Safety traffic camera pole 43° 2026-04-30 OSM node
83 no not tagged (operator: Flock Safety) traffic camera not tagged 0° 2024-12-13 OSM node
84 no Flock Safety traffic camera not tagged 9° 2026-01-03 OSM node
85 no Flock Safety traffic camera pole 161° 2026-04-30 OSM node
86 no Flock Safety traffic camera not tagged 341° 2025-12-31 OSM node
87 no Flock Safety traffic camera pole 86° 2026-07-27 OSM node
88 no Flock Safety traffic camera pole 267° 2026-07-27 OSM node
89 no Flock Safety traffic camera not tagged 359° 2025-11-24 OSM node
90 no not tagged traffic camera not tagged 190° 2026-04-10 OSM node
91 no not tagged (operator: Flock Safety) traffic camera not tagged 165° 2024-12-13 OSM node
92 no Flock Safety traffic camera not tagged 147° 2025-11-19 OSM node
93 no Flock Safety traffic camera post 219° 2026-07-25 OSM node
94 no Flock Safety traffic camera not tagged 334° 2025-11-19 OSM node
95 no Flock Safety traffic camera pole 50° 2025-02-14 OSM node
96 no Flock Safety traffic camera not tagged 95° 2026-09-01 OSM node
97 no Flock Safety traffic camera not tagged 270° 2026-08-29 OSM node
98 no not tagged traffic camera not tagged 60° 2026-04-10 OSM node
99 no Flock Safety traffic camera not tagged 235-280° 2025-12-03 OSM node
100 no Flock Safety traffic camera pole 190° 2025-01-07 OSM node
101 no Flock Safety (operator: Alpharetta Police) traffic camera pole 70° 2025-01-03 OSM node
102 no Flock Safety traffic camera pole 270° 2025-02-13 OSM node
103 no Flock Safety traffic camera pole 345° 2026-04-26 OSM node
104 no Flock Safety traffic camera pole 165° 2026-04-26 OSM node
105 no Flock Safety traffic camera not tagged 218° 2025-12-31 OSM node
106 no Flock Safety traffic camera pole 70° 2025-02-17 OSM node
107 no Flock Safety traffic camera pole 260° 2025-02-13 OSM node
108 no Flock Safety traffic camera not tagged 199° 2025-12-31 OSM node
109 no not tagged (operator: Flock Safety) traffic camera not tagged 0° 2024-12-13 OSM node
110 no Flock Safety traffic camera not tagged 0° 2025-12-10 OSM node
111 no Flock Safety traffic camera pole 10° 2025-02-14 OSM node
112 no Flock Safety traffic camera not tagged 83° 2026-06-20 OSM node
113 no Flock Safety traffic camera not tagged 50° 2025-09-05 OSM node
114 no Flock Safety not tagged not tagged 290° 2025-09-05 OSM node
115 no Flock Safety not tagged not tagged 180° 2025-09-23 OSM node
116 no Flock Safety traffic camera not tagged 250° 2026-07-28 OSM node
117 no Flock Safety traffic camera not tagged 0° 2026-04-03 OSM node
118 no Flock Safety not tagged not tagged 330° 2025-11-13 OSM node
119 no Flock Safety traffic camera not tagged 345° 2026-08-31 OSM node
120 no Flock Safety traffic camera not tagged 38° 2026-06-20 OSM node
121 no not tagged (operator: Flock Safety) traffic camera not tagged 90° 2024-12-13 OSM node
122 no Flock Safety traffic camera not tagged 0° 2026-08-31 OSM node
123 no Flock Safety not tagged not tagged 45° 2025-11-06 OSM node
124 no Flock Safety traffic camera not tagged 106° 2026-01-02 OSM node
125 no Flock Safety traffic camera pole 300° 2025-01-02 OSM node
126 no Flock Safety not tagged not tagged 240° 2025-11-06 OSM node
127 no Flock Safety traffic camera not tagged 200° 2025-09-05 OSM node
128 no not tagged (operator: Flock Safety) traffic camera not tagged 140° 2024-12-13 OSM node
129 no not tagged (operator: Flock Safety) traffic camera not tagged 260° 2024-12-13 OSM node
130 no not tagged (operator: Flock Safety) traffic camera not tagged 270° 2024-12-13 OSM node
131 no Flock Safety not tagged not tagged 310° 2025-11-13 OSM node
132 no Flock Safety traffic camera not tagged 14° 2026-06-16 OSM node
133 no Flock Safety traffic camera not tagged 340° 2026-07-22 OSM node
134 no Flock Safety traffic camera not tagged 297° 2026-08-08 OSM node
135 no Flock Safety traffic camera not tagged 140° 2026-08-19 OSM node
136 no Flock Safety traffic camera pole 180° 2025-02-14 OSM node
137 no Flock Safety traffic camera not tagged 150° 2026-05-15 OSM node
138 no Flock Safety traffic camera not tagged 233-278° 2025-12-03 OSM node
139 no Flock Safety traffic camera not tagged 192° 2026-05-15 OSM node
140 no Flock Safety not tagged not tagged 180° 2025-09-29 OSM node
141 no Flock Safety traffic camera pole 60° 2025-01-07 OSM node
142 no Flock Safety traffic camera not tagged 262° 2026-07-12 OSM node
143 no Flock Safety traffic camera pole 100° 2024-12-30 OSM node
144 no Flock Safety traffic camera pole 140° 2025-02-14 OSM node
145 no Flock Safety traffic camera not tagged 26° 2026-07-12 OSM node
146 no not tagged (operator: Flock Safety) traffic camera not tagged 250° 2025-02-01 OSM node
147 no Flock Safety traffic camera not tagged 228° 2026-05-13 OSM node
148 no Flock Safety traffic camera not tagged 228° 2026-05-13 OSM node
149 no Flock Safety traffic camera not tagged 228° 2026-05-13 OSM node
150 no Flock Safety traffic camera not tagged 228° 2026-05-13 OSM node
151 no Flock Safety not tagged not tagged 290° 2025-11-22 OSM node
152 no Flock Safety traffic camera not tagged 128° 2026-07-31 OSM node
153 no Flock Safety not tagged not tagged 200° 2025-11-21 OSM node
154 no Flock Safety traffic camera pole 125° 2024-12-30 OSM node
155 no Flock Safety not tagged not tagged 65° 2025-09-23 OSM node
156 no Flock Safety traffic camera pole 70° 2025-02-17 OSM node
157 no Flock Safety not tagged not tagged 180° 2025-09-23 OSM node
158 no Flock Safety traffic camera not tagged 228° 2026-08-07 OSM node
159 no Flock Safety traffic camera pole 174° 2026-05-13 OSM node
160 no Flock Safety traffic camera not tagged 93° 2026-01-21 OSM node
161 no Flock Safety traffic camera pole 206° 2026-07-27 OSM node
162 no Flock Safety traffic camera not tagged 140° 2026-07-27 OSM node
163 no not tagged (operator: Flock Safety) traffic camera pole 130° 2024-11-16 OSM node
164 no not tagged (operator: Flock Safety) traffic camera pole 45° 2024-11-16 OSM node
165 no not tagged (operator: Flock Safety) traffic camera pole 235° 2024-11-16 OSM node
166 no not tagged (operator: Flock Safety) traffic camera pole 315° 2024-11-16 OSM node
167 no Flock Safety traffic camera pole 340° 2024-12-17 OSM node
168 no Flock Safety traffic camera not tagged 190° 2026-01-21 OSM node
169 no Flock Safety traffic camera pole 20° 2026-06-27 OSM node
170 no Flock Safety traffic camera pole 270° 2024-12-31 OSM node
171 no Flock Safety traffic camera pole 120° 2024-12-31 OSM node
172 no Flock Safety traffic camera not tagged 269° 2026-07-28 OSM node
173 no Flock Safety traffic camera not tagged 34° 2026-06-11 OSM node
174 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
175 no Axis Communications traffic camera Moveable sign 33° 2026-06-11 OSM node
176 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
177 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
178 no Flock Safety traffic camera not tagged 308° 2025-12-01 OSM node
179 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
180 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
181 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
182 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
183 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
184 no not tagged traffic camera not tagged not tagged 2026-08-05 OSM node
185 no Flock Safety traffic camera not tagged 306° 2026-08-19 OSM node
186 no Flock Safety traffic camera pole 54° 2026-03-29 OSM node
187 no Flock Safety traffic camera pole 290° 2025-02-01 OSM node
188 no Flock Safety traffic camera pole 130° 2025-02-01 OSM node
189 no Flock Safety traffic camera pole 130° 2025-02-14 OSM node
190 no Flock Safety traffic camera not tagged 150° 2026-07-01 OSM node
191 no Axon Enterprise traffic camera pole 196° 2026-06-16 OSM node
192 no Flock Safety traffic camera not tagged 83° 2026-08-13 OSM node
193 no Flock Safety traffic camera pole 329° 2026-06-13 OSM node
R1 yes not recorded not recorded pole not recorded reported 2026-09-13 Reader report, confirmed on Street View
R2 yes not recorded not recorded pole not recorded reported 2026-09-16 Reader report, confirmed on Street View

Take the data: the snapshot as JSON and the query that produced it.

Map of Milton, Georgia showing 55 license plate cameras pinned inside the city limits as gold dots and 138 just outside the line as hollow dots, with the city boundary drawn
The same data as a still image. Download.

Method and sources

OpenStreetMap nodes tagged man_made=surveillance and surveillance:type=ALPR in a box about 2 kilometers beyond Milton’s city limits, pulled from the Overpass API on September 12, 2026 (OSM data timestamp 2026-09-12T00:45:51Z; newest contributor edit 2026-09-04, oldest 2024-11-16). Inside and outside were decided against the City of Milton’s GIS boundary, shown simplified. The snapshot as JSON and the query. City numbers: Milton Police Department, written answers, September 11, 2026. Population: U.S. Census Bureau, Vintage 2025 estimate. Nothing on this page is sponsored.

Supported by our founding partners

At Home Property Group Meet our partners →