If we can reach consensus on the use of traffic_sign_code, it would not be hard to perform a mechanical edit to move them over (and populate the traffic_sign) with human readable values.
Such a script would not touch 'ambiguous' data, of course and leave that to humans. The tricky part is making a good proposal. Not overly hard for many of the traffic signs, Quite a challenge for all the sub signs in the various languages... Polyglot 2015-10-28 9:48 GMT+01:00 Martin Koppenhoefer <dieterdre...@gmail.com>: > > 2015-10-28 7:12 GMT+01:00 Mateusz Konieczny <matkoni...@gmail.com>: > >> Also, one may use for example traffic_sign_code to tag exact reference >> allowing for country specific data processing (for example >> [traffic_sign=oneway, traffic_sign_code=PL:D-3]). >> > > > one might use this tag traffic_sign_code=*, but it's not what people are > doing so far. There are just 2 instances of this key, but there are 343.000 > traffic_sign tags, most of them being "city_limit", 2nd place "maxspeed" > and most of the rest are country dependent codes: > http://taginfo.osm.org/keys/traffic_sign#values > > Cheers, > Martin > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
