-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Direction confused ~on city_limit sign~ when area is glued to way with direction-node #5634
Comments
I think the best thing to do here is just unglue the road from the landuse |
In the spirit of documenting edge cases: This issues does happen as well, when using Example: https://www.openstreetmap.org/edit?note=3490280#map=20/52.48743/13.43160 This came up in a different context as well (https://www.openstreetmap.org/note/3490280). It looks like Garmin Navis do have similar rending effects as iD. The notes talk about a Garmin navi that showed 4 traffic lights instead of one. |
fyi: I just started a thread in the forum on this phenomenon. |
#9013 tracks another case of this issue involving stop signs and non-roadway lines. |
for certain vertex features, only look at matching parent ways when determining where to draw direction cones: * highway related points (e.g. highway=stop/yield/etc., traffic calming, cycleway=asl, traffic signs, barriers): only look at parent ways with highway=* * railway related points (e.g. railway=milestone): only look at parent ways with railway=* * waterway related points (e.g. waterway=milestone): only look at parent ways with waterway=* see also #5634
for certain vertex features, only look at matching parent ways when determining where to draw direction cones: * highway related points (e.g. highway=stop/yield/etc., traffic calming, cycleway=asl, traffic signs, barriers): only look at parent ways with highway=* * railway related points (e.g. railway=milestone): only look at parent ways with railway=* * waterway related points (e.g. waterway=milestone): only look at parent ways with waterway=* see also #5634
for certain vertex features, only look at matching parent ways when determining where to draw direction cones: * highway related points (e.g. highway=stop/yield/etc., traffic calming, cycleway=asl, traffic signs, barriers): only look at parent ways with highway=* * railway related points (e.g. railway=milestone): only look at parent ways with railway=* * waterway related points (e.g. waterway=milestone): only look at parent ways with waterway=* see also #5634
Case: There is a road which is glued to the area next to it.
This is here: https://www.openstreetmap.org/edit?way=198948464#map=20/50.81705/6.37598
The direction indicator seems to be confused by the glued area + road.
no direction:
traffic_sign:direction=backward
traffic_sign:direction=forward
traffic_sign:direction=both
Workaround:
The text was updated successfully, but these errors were encountered: