[RFC] traffic signs national id and human readable values (traffic_sign=* and traffic_sign:id=*)

[Mateusz_Konieczny]

@yopaseopor

So…should I have to swear by the God I believe that I will not change any traffic sign mapped before?

This would not help - others would definitely do it anyway.

To avoid stealthy deprecation proposal would need to admit that it is deprecating things or it needs to approve multiple tagging schemes at once. And yes: both will not be liked by some other mappers.

Or proposal needs to limit itself to areas where no competing established tagging exists.

@yopaseopor

Also, traffic_sign=restriction makes no sense. That is a class of traffic signs, not a specific traffic sign. Maybe splitting proposal into parts is feasible? > This proposal is NOT about categories, you can read it in the proposal. This was already splitted out of the proposal.

If traffic_sign=restriction is not a part of a proposal then why it is on the proposal page on page listing what will be approved?

https://wiki.openstreetmap.org/wiki/Proposal:Extended_traffic_signs_tagging

@yopaseopor

but…how can you make a relation between traffic sign and the point where acts it?

by placing node at position of traffic sign, next to road it acts on? In rare cases where match to road is not obvious description can be added

@yopaseopor

Why in other items like enforcement do we need a relation?

No idea, not checked. Maybe these are intended to be machine-readable? You can link their documentation if you want fuller answer.

@yopaseopor

And how to map without a compass?

???

By using other orientation methods like already mapped objects or aerial imagery?

@yopaseopor

I’m not a big expert about that but I don’t understand why a traffic sign does not affect “itself” the object. Also I don’t know what software can do that and when, because some approved tags are not considered by main software. Is it a official parameter for “not to map” some kind of objects?

I do not understand this part.