[Tagging] Traffic sign's relevant direction: direction=* vs. relation [Was: traffic_signals:direction=* vs. direction=*]
yopaseopor at gmail.com
Thu Mar 23 23:15:41 UTC 2017
On Thu, Mar 23, 2017 at 9:03 PM, Martin Koppenhoefer <dieterdreist at gmail.com
> sent from a phone
> > On 23 Mar 2017, at 17:23, Jean-Marc Liotier <jm at liotier.org> wrote:
> > - highway=stop+direction=forward node on the incoming way... Only
> > covers the simple case but covers it simply
I prefer the subkey :forward / :backward because then we save one pair of
key=value we can use to put the future unification of the meaning of
traffic signs groups.
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.
For consistence , whit two ways with the same directions, which problem do
you have if the splitted way marks the direction...to the same direction so
is coherent between nodes and the two ways?
> 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.
Using the :forward/backward scheme and with Kendzi3D I get the situation
very similar to reality as you can see in these pics,  and . I can
map any traffic sign you have in any traffic law which have a code. People
like Mapillary do some classification we can "copy" or use/propose similar
in a future unification of the keys with meaning for traffic signs , fa
away than only city limit,
Salut i senyals de trànsit (Health and traffic signs)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging