|Devices that measure and document traffic violations and their coverage zone|
|* - device|
This relation documents different kinds of devices that measure and document traffic violations, such as:
- speed traps
- red light cameras
- distance between vehicles measuring
- weight check (heavy goods vehicles)
- ordinary traffic checks (papers, use of alcohol, etc.)
These devices belong to the same class of objects and shall therefore use the same tagging schema with different values. Sometimes a combination of values is required if the device serves more than one function (e.g., both a speed trap and red light camera in one device).
Where to map?
Everywhere, except in countries that forbid mapping traffic enforcement installations. If rendering or displaying in a routing software or alerting in a routing software is forbidden anywhere, you can add the information to the map - renderer and routing software will make sure to follow the law. Therefore, routing software shall offer traffic enforcement features as plug-ins, so the user can choose if he wants to install the feature.
Traffic enforcement devices are not a place you'd want to go and are therefore not an amenity.
Create a single relation for each traffic enforcement device, if there are several, as each can measure different things to vehicles from different directions.
|type||enforcement||enforcement||The type of relation.|
|enforcement||maxheight / maxweight / maxspeed / mindistance / traffic_signals / check / access||maxheight||The type of enforcement.|
|maxheight||number; specify unit if not in metres||4||The maximum height (only specify if enforcement=maxheight)|
|maxweight||number; specify unit if not in tonnes||16||The maximum weight (optional, only specify if enforcement=maxweight)|
|maxspeed||number; specify unit if not in km/h||60||The maximum speed (only specify if enforcement=maxspeed)|
The "mindistance" enforcement is for following distance. The "check" enforcement is for a checkpoint.
See the original proposal