Puzzled by traffic sign mapping

[emvee]

@SK53

I would have expected it to provide a more human readable indication of the nature of the sign: precise for very common values (e.g., give_way, stop, city_limits, maxspeed, …) and more generic for signs with variable content (destination) or ones used less frequently (hazard, instructional …). It is this latter approach which is best documented on the wiki , but usage does not really reflect this (hazard: 2135, destination: 1507, stop: 31,907, but NL:G11: 57,080).

The Wiki, Traffic sign IDs is clear to me, it is after Human-readable values that might obscure it a bit.

I do not see a need for human-readable values, what is needed is that things are clear to the user and precise. This is how Josm looks for me:

Source: Josm with an image background from beeldmateriaal,nl

Notice that it is clear that the cycleway is a NL:G11 without seeing “traffic_sign=NL:G11” ever. Also adding new traffic signs can be done without knowing the code ever.

For the JOSM menu, see JOSM Presets voor NL, traffic signs for ways are available through Josm Map Paint Styles and I have also the Road Extended JOSM (default) style (forum post) active.

iD offers about 5 of the documented textual values and not the ones most widely used.

Fix the tools instead of adding an additional traffic_sign:ref that will for sure trigger problem like traffic_sign:ref and traffic_sign not being in line with each other.