Proposal:More detailed tagging of traffic mirrors
| More detailed tagging of traffic mirrors | |
|---|---|
| Proposal status: | Proposed (under way) |
| Proposed by: | Biff |
| Tagging: | traffic_mirror=*
|
| Applies to: | |
| Definition: | Tagging of specific kinds of traffic mirrors, tagging of traffic mirror as a secondary feature |
| Statistics: |
|
| Draft started: | 2026-10-02 |
| RFC start: | 2026-10-03 |
Proposal
This proposal specifies tagging of the specific kinds of traffic mirrors, such as dead-angle traffic mirrors. It also specifies how to avoid tagging traffic mirrors as a secondary feature, for example if the traffic mirror is mounted to a street lamp. Additionally, it aims to improve the specification of highway=traffic_mirror.
The proposal applies to nodes, just like the basic and existing tag highway=traffic_mirror.
Rationale
During the discussion of the proposal that resulted in an enhanced specification of Relation:traffic_mirror, several ideas were developed for improved tagging of the mirror node. These ideas were outside the scope of the discussion of the relation, and it was decided to create a separate proposal for improved tagging of the mirror node.
To keep things simple, the proposed name of the tag is based on the value of highway=traffic_mirror.
Placement of the node
Place a node in the middle of the frame of the mirror when mapping with high resolution. When mapping with less detail, it is also acceptable to place the mirror node at its supporting structure, but see #Mirror attached to supporting structure if a separate node is provided for the supporting structure.
Tagging
Tags
The node is tagged as follows:
| Key | Value | Presence | Comment |
|---|---|---|---|
highway |
traffic_mirror |
! Required | Of course, this remains the main tag for traffic mirrors. |
direction |
<number> or <abbreviation> | ‽ Important | Cardinal direction in which the traffic mirror faces.
The given <number> specifies the degrees from 0 to 359 in which the feature faces, where 0 is equal to northward, using clockwise rotation. The <abbreviation> is one of the 16 main or first or secondary intercardinal directions, specified as its abbreviation using up to three uppercase characters [NWSE], e.g. |
traffic_mirror |
yes |
✗ Avoid | This tag is in use for a low number of traffic mirrors that are a secondary feature. An example is a traffic mirror that is attached to a street lamp that is already mapped as highway=street_lamp.
It is recommended to avoid tagging of traffic mirrors as a secondary feature. Instead, the mirror should be mapped as a separate node, see example #Mirror attached to supporting structure below. Existing instances should be changed. |
no |
✗ Avoid | This value can be used to clearly tag that no traffic mirror exists at the node.
This tag is specified here for completeness. No scenario has been identified where this tag is useful. Don't tag arbitrary nodes with this value. | |
dead_angle |
? Optional | A dead-angle mirror is placed at a junction to allow the driver of a truck or bus to see bicycles and pedestrians that are located in front of or at the side of the vehicle.
In German-speaking countries, such dead-angle mirrors are frequently called "Trixi" mirrors, see https://trixi-spiegel.de/ . | |
bidirectional |
? Optional | Bidirectional mirror. Such mirrors are frequently used in a curve to allow vehicles to look around in the corner in both directions of traffic.
To provide even more detail, two relations of | |
| <other value> | ? Optional | Of course, additional entries for the table can be defined based on the discussion of this proposal. OSM allows mappers to invent additional tag values, but some guidance should be given for this.
If the existing tagging scheme is insufficient, you can invent any tags you like. Please provide a good changeset comment and document the new tag value on the discussion page. It can take significant time until a new tag value is properly interpreted by data consumers. Initially, they are likely to simply interpret it as | |
count |
<number> | ? Optional | This tag specifies the number of traffic mirrors in one place. The tag is only intended to be used if a node represents more than one traffic mirror.
This tag can be avoided by mapping each mirror as a separate node, see example #Mapping two mirrors as two nodes below. |
operator |
<name> | ? Optional | This tag specifies the name of the operator of a traffic mirror.
This tag can be helpful to identify mirrors that are privately owned and typically only suitable to help when leaving a driveway vs. normal traffic mirrors on public roads. |
support |
<value> | ? Optional | This tag describes what supports the traffic mirror. |
The following attribute tags are in use with traffic mirrors:
mapillary=*andpanoramax=*start_date=*andcheck_date=*mirror_curvature=flat/convexshape=circular/rectangularindoor=*andlevel=*- Use
description=*to provide specific human-readable information about traffic mirrors that is not covered by other tags.
Other approaches
- Dead-angle mirrors and bidirectional mirrors can be fully represented by relations of
type=traffic_mirror. Mappers that do not know how to use the relation can always leave adescription=*and some other more experienced mapper can later create missing relations. This would mean that specific values liketraffic_mirror=dead-angleortraffic_mirror=bidirectionalare not needed at all.
Confidence check for tagging
TBD
Migration from legacy tagging
TBD
Examples
Mirror attached to supporting structure
A traffic mirror can be supported by a structure that merits its own node, for example a power pole.
Example: https://www.openstreetmap.org/node/2414421575
It is recommended to place the mirror node at a sufficient distance from the node of the supporting structure so mappers can see that these are two separate nodes at maximum zoom level.
-
highway=traffic_sign+traffic_sign=RO:B01;D01;A46+ separate node tagged withhighway=traffic_mirror+support=pole
Dead-angle mirror
A dead-angle mirror is placed at a junction to allow the driver of a truck or bus to see bicycles and pedestrians that are located in front of or at the side of the vehicle, see https://www.openstreetmap.org/node/11669196639. This kind of traffic mirror can also be used at traffic lights with an advanced stop line (for bicycles), see https://www.openstreetmap.org/node/6231164809 . (These examples are similar but not identical with the picture.)
Bidirectional mirror in curve
For a tagging example, see https://www.openstreetmap.org/node/14190195484 (similar but not identical with pictures).
Two mirrors in one place
If two mirrors exist in one place, for example to provide a view to the left and to the right, they can either be mapped as a single node or as two individual nodes.
Mapping two mirrors as a single node
For a tagging example, see https://www.openstreetmap.org/node/12536423929
highway=traffic_mirror count=2 direction=272;182
To provide more detail, Relation:traffic_mirror can be used. In this case, two relations are needed and the traffic-mirror node is added as the member to each relation (which means that the node is a member of two relations).
mirror
Mapping two mirrors as two nodes
For a tagging example, see https://www.openstreetmap.org/node/5068365280 and https://www.openstreetmap.org/node/11153695711
Left node:
highway=traffic_mirror direction=168
Right node:
highway=traffic_mirror direction=52
To provide more detail, Relation:traffic_mirror can be used. In this case, two relations are needed - and each traffic-mirror node is added as the member to one relation (each node is the member of one relation).
mirror
Specific kinds of traffic mirrors
Please use description=* to provide human-readable information about very specific kinds of traffic mirrors that is not covered by defined tags.
-
highway=traffic_mirror+description=This traffic mirror has an extremely wide viewing angle.
Mirrors that are not covered by this proposal
Traffic mirror at a train or tram platform
This mirror allows the driver to see if passengers are still getting on and off the train or tram.
Rendering
As already specified for highway=traffic_mirror.
Features/Pages affected
traffic_mirror=*highway=traffic_mirror- add information and link totraffic_mirror=*- Relation:traffic_mirror - add information and link to
traffic_mirror=*
External discussions
The idea for this proposal came up in this discussion: https://community.openstreetmap.org/t/title-rfc-feature-proposal-traffic-mirror-relation-using-ways/146318
The RFC has been posted to https://community.openstreetmap.org/t/rfc-feature-proposal-more-detailed-tagging-of-traffic-mirrors/148344
Comments
Please comment on the discussion page.