[RFC] Feature Proposal – More detailed tagging of traffic mirrors

I would keep to mention that it’s NOT intended to be mapped.

Please review my recent update of the proposal page.

Here’s a list of remaining issues:

  • “Other approaches”: Can we delete this? In my opinion, usage of the description tag will not scale well. It is better to use traffic_mirror=dead_angle or traffic_mirror=bidirectional. We could say that their usage is optional, if a relation (or two) provide the same information.
  • The tag mirror_curvature is in use for a low number of mirrors. Is this the most appropriate tag? Maybe it should be mirror:curvature? The simple tag curvature might be mistaken for information about curves of the street.
  • I’ve added placeholders for a confidence check and for migration from legacy tagging. If you have a good idea what to write there, please edit these sections and add appropriate text.

In fact,
highway=traffic_mirror
count=2
direction=272;182
could be simplified to:
highway=traffic_mirror
direction=272;182

count=2 makes sense only if you know you’ve 2 mirrors but not their directions.

Thanks, I’ll try to provide better info about tags that are redundant under specific conditions. This is not the only one.

The proposal currently lists the “in use” tag shape with the values circular and rectangular. It probably makes sense to take a better look at this. (99% of roughly 120 instances where the tag is used are located around Saarbrücken, Germany, and were probably all tagged by the same mapper.)

I searched the internet and it looks like many manufacturers (probably the majority) use the term “round” instead of “circular”. Should circular be changed to round?

Other mirror shapes that can occur might be “dome”, “half_dome”, “quarter_dome”. shape=half_dome might fully describe the shape of the mirror with very wide viewing angle that is shown in one example and would otherwise need a description.

1 Like