What about a type=traffic_sign relation? Where traffic_sign could be stop, give_way, parking.
We can put a traffic_sign tag on nodes, where they get the country_code:specific_national_code like BE:C1. Several traffic signs can have an effect on several ways and nodes of the road network, so we could group them in such relations. In case of a stop sign, we could include the sign on a node, role 'sign'. The node of the intersection, maybe role 'to'. The way the vehicle is approaching from, maybe role 'from'. In case of parking it would make very clear on which ways there is parking and we would have central place to keep track of the conditions like "opening_hours" and tariffs, or specific requirements like permits. Polyglot 2017-05-07 8:57 GMT+02:00 Paul Johnson <ba...@ursamundi.org>: > I think it's time that we seriously reconsider how stop signs, yield signs > and traffic calming devices are handled in all but the most simple (all > approaches to the affected node apply) cases. This largely after having a > protracted discussion with one person about nodes lacking direction and > this being a big factor in turn restrictions and enforcement being handled > by relations already (and really, the entire reason relations were > introduced in the first place). > > I'm thinking it's time to start mapping this similar to how we handle > enforcement and turn restrictions, ie, with relations, for all but the > simplest of cases, especially since the whole forward/backward direction=* > thing is nonapplicable to nodes by design. > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
