It's a different topic: speed, height... Mainly apply to a way whereas stops mainly (always ?) apply to a node.
Speeds can still be tagged on the way and the sign put appart from the road, mainly for rendering purpose because the way it applies to is already tagged with the consequence (the speed). In this thread I already proposed the same mechanism for stops, i.e. a node for the sign at it's exact location (for renderers) + a node on the way at the location where the car has to stop/halt/slow down (for routing engine). This way we can address both needs (routing engine are not the only data consumer ;) ). What do you think? LeTopographeFou Message original De: dieterdre...@gmail.com Envoyé: 23 mars 2017 9:05 PM À: j...@liotier.org Répondre à: tagging@openstreetmap.org Cc: tagging@openstreetmap.org Objet: Re: [Tagging] Traffic sign's relevant direction: direction=* vs. relation [Was: traffic_signals:direction=* vs. direction=*] sent from a phone > On 23 Mar 2017, at 17:23, Jean-Marc Liotier <j...@liotier.org> wrote: > > - highway=stop+direction=forward node on the incoming way... Only > covers the simple case but covers it simply while this might work often with stop signs it'll hardly work with maxspeed signs, because the changing maxspeed requires to split the highway, so that there would be 2 highways ending in the same node and forward would not be clear of which way. When I map traffic signs it's mostly city limit, maxspeed/maxweight/maxheight and I do it generally for fellow mappers (including myself) because the effect of the sign I will map on the highway (typically linear, not just a point). Mapping on the side of the road has worked out perfectly for this scope. 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
