Tag:surveillance:type=ALPR

From OpenStreetMap Wiki
Jump to navigation Jump to search
surveillance:type = ALPR
Description
A camera designed to record license plate identifiers of passing vehicular traffic. Show/edit corresponding data item.
Group: man made
Used on these elements
may be used on nodesshould not be used on waysshould not be used on areasshould not be used on relations (except multipolygon relations)
Requires
Implies
Useful combination
See also

surveillance:type=gunshot_detector

Status: de facto

A surveillance camera known to be part of an automatic license plate recognition (ALPR) system (also known as automatic number-plate recognition (ANPR), among other names). ALPR utilizes computer vision technology to scan images of vehicular traffic for license plates (and potentially other identifying characteristics of each vehicle, such as color, make, model, etc.). This information is typically stored in databases and used for law enforcement scenarios, such as vehicle theft. While in principle ALPR can use images from any camera, some camera models are sold for the specific purpose of capturing vehicle license plates, often including features that improve license plate capture such as infrared imaging capabilities for operation in low light conditions or at night. Some common manufacturers of ALPR cameras include Flock Safety, Motorola Solutions, and Leonardo.

How to map

Place a node node at the location of the camera.

Main tag combinations

These combinations serve as the baseline for describing the ALPR.

Key Value Description
man_made=* surveillance ALPRs are always associated with man_made=surveillance.
surveillance=* public Typically for ALPRs located on streets that are watching general traffic.
outdoor Typically for ALPRs that are watching more specific areas, such as parking lots or entrances to places such as apartment complexes.
surveillance:zone=* traffic ALPRs watching street traffic that has no specific destination in mind.
parking ALPRs watching parking destinations.
entrance ALPRs watching entrances to destinations (besides parking), principally to apartment complexes.
camera:type=* fixed ALPRs are traditionally fixed cameras, as they are always targeting specific areas of traffic to read license plates. In principle, ALPR software can transform Pan/Tilt/Zoom (PTZ) cameras (OSM values panning or dome) into ALPRs; however, in this deployment, the typical behaviour is still fixed (and the ability to recognize when such a camera is deployed in such a configuration is limited).
camera:mount=* pole The vast majority of ALPRs are mounted on poles of one sort or another. Whether or not the poles should be mapped separately is undecided as of now (2025-06-29). In general, one can assume one of two scenarios:
  • An ALPR node with no separate pole nodes (e.g., man_made=utility_pole, highway=street_lamp, power=pole) "nearby" (one meter? ten meters?) implies that camera:mount=pole on the ALPR is the "authoritative pole." Typically, this would imply that the pole is used exclusively by the ALPR.
  • An ALPR node with separate pole nodes (see examples in previous bullet point) nearby implies that camera:mount=pole on the ALPR is referential to this separate pole.
  • However... many deployments do have an exclusive pole for the ALPR planted nearby to a separate pole. A practical solution to this problem could be to introduce a relation that binds together poles (or masts, or towers, or other similar structures) with the varying pieces of equipment that are mounted onto them. As of 2025-06-29, no such relation has been defined/explored yet. Another potential option is some sort of indicator tag, but... one problem at a time.
direction=* Usually a positive integer, but see Key:direction The direction that the camera is pointed toward; usually expressed as a number representing degrees clockwise from north, but see the key page for more details on acceptable values. But what about camera:direction=*? Seeing as this particular Key is only in "in use" status, as compared to direction=* which has "approved" status (and far greater usage), a preference for direction=* is given.
electricity=* solar For use when the ALPR is powered by a battery that is, in turn, charged by a small solar panel. Most Flock Safety devices fall under this category.
grid For use when the ALPR is powered by a grid connection of some kind. Axis Communications ALPRs are of this type.

Additional tag combinations

Often times, the ALPR is visually distinctive enough to identify its specific manufacturer. As well, when ALPRs are identified in response to public records requests, the operator of the particular camera is often revealed (typically, a police department or a Home Owners Association/HOA).

Key Value Wikidata Value Description
manufacturer=* Flock Safety manufacturer:wikidata=* [W]Q108485435 The largest vendor of ALPR devices in the United States.
manufacturer=* Axis Communications manufacturer:wikidata=* [W]Q2347731 Another vendor of ALPRs (and other security devices), typically for high traffic flow scenarios.
operator=* e.g., Ventana Homeowner's Association operator:wikidata=* [W]Q125921230 A Home Owner's Association (HOA) in far west Fort Worth, Texas.

Example deployment mappings

Below are some example areas where ALPRs (and other surveillance devices like surveillance:type=gunshot_detector ) have been mapped out by surveyors.

Las Vegas Trail Improvement Area in Fort Worth, Texas

This area has a higher crime rate than surrounding areas. As such, it was targeted for deployment of ALPRs and gunshot detectors provided by Flock Safety in a contract between Flock Safety and the city of Fort Worth.

A map of the Las Vegas Trail area of west Fort Worth, Texas. It shows Flock Safety Automated License Plate Readers (ALPRs) as red dots (technically, some Axis Communications ALPRs are also included), Flock Safety gunshot detection devices as blue dots, and combination devices as purple dots. A few other security cameras are also documented as yellow dots with blue outlines.
try it yourself in overpass-turbo
try it yourself in overpass-turbo
// @name surveillance-tarrant-county

[out:json][timeout:25];
  area[admin_level=6]["name"="Tarrant County"]->.tarrant; 
out body;

(
  node
  ["man_made"="surveillance"]["surveillance:type"="ALPR"]
  (area.tarrant);
  node
  ["man_made"="surveillance"]["surveillance:type"="gunshot_detector"]
  (area.tarrant);
  node
  ["man_made"="surveillance"]["surveillance:type"="camera"]
  (area.tarrant);
);
out body qt meta;

{{style:
  node[surveillance:type=gunshot_detector] { fill-color: blue; color: blue, fill-opacity 1;}
  node[surveillance:type=ALPR] { fill-color: red; fill-opacity 1; color: red, fill-opacity 1; }
}}

Another example

(This is where you come in, by the way.)

See also

Possible tagging mistakes

Possible synonyms of this tag

If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!

Manufacturer as brand or operator

If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!

Other common mistakes

If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!