Introduction
Public transparency regarding municipal surveillance technology relies heavily on accurate documentation and accessible public records. A recent discovery in Denver highlighted a gap between public reporting and physical deployment when a Denver resident says city map didn’t properly show locations of Axon license plate readers. The discrepancy brought to light administrative oversights within the Denver Police Department’s geographic tracking and deployment paperwork, prompting swift updates to municipal public resources.
What Changed
City leaders in Denver updated the city’s official map tracking automated license plate reader (ALPR) locations following a citizen’s detailed inquiry. Initially, the Denver Police Department (DPD) identified 14 intersections for ALPR deployment based on violent crime, hit-and-run and injury crash statistics, and auto theft data. Each of these 14 selected locations received four ALPR units to ensure comprehensive coverage across every direction of travel.
However, physical deployments diverged from the original GIS filings. According to reporting from Denver7 and journalist Micah Smith, officers overseeing the installation of the equipment filed original paperwork with the city’s GIS team showing an intended installation at Sheridan and Dartmouth. Due to permitting constraints and geographic layout limitations, four of the original 14 intersections were deemed unviable, requiring DPD to shift to four alternate intersections.
Consequently, physical hardware appeared at intersections not listed on the public map, such as Evans Avenue and Federal Blvd., while other initially scheduled intersections remained empty.
Context and Discovery
The issue came to light through the investigative efforts of local resident William Beckett. Explaining his methodology to Denver7, Beckett stated: “When we switched and signed a contract with Axon, I saw that there were several intersections listed where the cameras were going to be going up, and so around the time they were supposed to be going up, I just traveled around to those intersections, and just — I wanted to see what they looked like. At some of the intersections that I went to, I noticed that there were no cameras.”
Upon inspecting the intersection of Evans Ave. and Federal Blvd., Beckett made a contrasting discovery. “I saw four Axon cameras and their solar panels up, one on each traffic light, and I was just baffled that they had gone up somewhere where DPD and the city had said that they were not supposed to be,” Beckett noted.
Acting quickly, Beckett documented the hardware and notified city officials. “Minutes later, I emailed City Councilor Kevin Flynn,” he recalled.
Business and Municipal Implications
City Councilor Kevin Flynn initially assumed Beckett might be mistaken, relying on prior assurances from the police department regarding deployment tracking. However, after receiving photographic evidence from Beckett, Flynn coordinated directly with law enforcement.
In response to the query, Flynn stated: “I emailed your photos to DPD and officers confirmed those are Axon ALPRs. The online map is being updated to reflect this. The confusion arose because the officers who oversaw installation of the cameras filed the original paperwork with the city’s GIS team, which showed those cameras were intended to be installed at Sheridan and Dartmouth.”
To prevent similar administrative gaps during the Axon ALPR pilot program, DPD instituted a new policy requiring a twice-annual audit of the ALPR map to ensure long-term accuracy.
Risks, Limitations, and Accountability
While the map has been updated, community members have raised concerns regarding operational oversight. William Beckett asserted that there was no public announcement regarding the location shifts, pointing out what he feels is a lack of accountability in the process. Additionally, Beckett claimed that there are no official city policies prohibiting surveillance cameras from being moved once deployed, though this specific policy detail remains an unverified claim without independent confirmation in the record.
From a technical access perspective, the operational scope remains relatively contained. The research notes that fewer than a dozen DPD personnel currently have access to ALPR alerts or possess the authorization to run investigative queries during this phase of the Axon pilot program.
What to Watch Next
As the pilot program continues, public scrutiny over automated policing technologies remains high. Observers and local residents will likely monitor whether DPD’s newly instituted twice-annual audits successfully keep digital public maps aligned with physical infrastructure changes. Future reporting will determine if transparency protocols evolve to include mandatory public notifications whenever deployment sites undergo last-minute geographic adjustments.