AivexaNewsSearch
AI news for builders and product teamsChecked every hour

How to find Flock cameras near you with MapQuest’s new ‘surveillance layer’

Collected Oct 19, 2026

MapQuest announced on Bluesky that it has added a surveillance layer to the map in its app, letting users see the locations of known outdoor license plate readers near them. The company framed the feature around growing concern over the spread of Flock license plate tracking cameras. MapQuest is the long-established navigation brand that many users remember from printing turn-by-turn directions decades ago, and it now offers turn-by-turn navigation in its app much like Google Maps and Apple Maps.

The layer draws from multiple vendors rather than a single manufacturer. According to MapQuest, it shows license plate readers from Flock Safety, Motorola Solutions, Genetec, Axis Communications, Axon, Leonardo, Neology, Rekor, PlateSmart, Ubicquia, Verkada and others. That breadth matters because Flock is only one supplier in a broader market for automated license plate recognition hardware; the layer is aimed at outdoor readers specifically, which is the category typically mounted on poles, signs and roadside infrastructure.

Turning the layer on is straightforward: users tap the layer icon on the main navigation screen and flip the toggle. Cameras then appear on the map as a small red eye, and a vision cone shows which direction each camera faces. There is no setting yet to route around license plate reading cameras automatically. Users can see where the cameras are and choose to avoid them manually. That is a meaningful limitation for anyone who wants hands-off avoidance, since it puts the work of interpreting sight lines and choosing alternate streets on the user.

MapQuest has not explained how it sourced the camera locations to ZDNET, which has asked. Several crowdsourced maps of license plate readers already exist online, including OpenStreetMap, and Flock has been actively fighting some of those efforts. The likely reading is that MapQuest's data is user-generated, though the locations shown appear reliable. From a product standpoint, crowdsourced surveillance data raises familiar questions about freshness and accuracy: a camera removed or relocated may linger on the map, and a newly installed one may not appear until someone reports it. The vision cone also implies metadata about orientation, which is the kind of detail crowdsourced contributors can supply but that is harder to keep current at scale.

MapQuest's layer differs in emphasis from what rival navigation apps show. Waze identifies what it calls police cameras, but that category lumps in speed cameras and general traffic and weather cameras, making it hard to distinguish surveillance equipment from road-monitoring hardware. Neither Google Maps nor Apple Maps offers information on Flock camera locations, according to the report. In practice, that leaves MapQuest with a distinct, if narrow, position: a mainstream navigation app that treats surveillance exposure as a map layer alongside roads and points of interest.

The report includes an anecdotal sense of scale. ZDNET's Artie Beaty writes that he had not been especially concerned about Flock cameras until he turned the layer on and saw more than 30 cameras across his medium-sized town of about 80,000 people. A reader can do the arithmetic themselves, but the headline figure in the coverage is that roughly 90,000 Flock cameras have gone up in the United States.

MapQuest itself has been enjoying something of a resurgence against a market dominated by Google Maps, Waze and Apple Maps. In August the company announced it would not change the name of Lake Ontario, which led to a surge of new users, and it announced Android Auto support shortly afterward. The surveillance layer fits that pattern of using small, distinctive features to differentiate rather than trying to outspend larger rivals on mapping data.

Why it matters: Developers and product teams building navigation, delivery-routing or privacy-oriented tools now have a mainstream precedent for treating camera locations as a queryable map layer, which suggests (as my own inference) demand for structured surveillance-location data and for routing options that can act on it. Privacy-conscious users gain a manual avoidance tool inside an app they may already have installed, while the absence of automatic rerouting leaves room for competitors to go further. The big open variable is data provenance and maintenance: crowdsourced camera maps live or die on refresh rates, and neither MapQuest's sourcing nor its update cadence is publicly confirmed.

Read at ZDNet · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

A name from the past is emerging again to help you stay out of sight of surveillance cameras.