-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Do not ask for path segregation in case either bicylce or foot is set to "no" #5213
Comments
I think this part of the query is wrong: Line 21 in b623dcc
In this case, we have a match of the combination highway = path and footway:surface Maybe |
Oh, that is definitely a bug. Thank you for the input, I will have a look at it now. |
It was added by @matkoniecz in #4642 , not sure why though. I don't really understand why the filter is there in the first place. Maybe he remembers? (In any case, @ironspock , the way is tagged a bit weird: As a |
Weird tagging is present there, I opened https://www.openstreetmap.org/note/3851707
to handle some not fully tagged ways, also I guess that case like reported here is blatantly invalid rather than missing tagging and could be skipped (though it would anyway cause confusion in surface overlay anyway...) And maybe surface overlay should not simply check |
I see, |
In plan on fixing it this way + open notes in places with such tagging. See http://overpass-turbo.eu/s/1zG7 and http://overpass-turbo.eu/s/1zG9 for suspicious data - I opened some notes already, may open more later. |
possible bug or enhancement on quest "How footway and bicycleway are segregated" (highway:path)
SC is asking for path segregation however the node already has a tag bicycle:no
(refer to https://www.openstreetmap.org/way/990523743)
I'm not sure whether it's happen often or maybe it's better to change the node from highway:path to highway:footway via JOSM/ID/etc.
Expected Behavior
Do not ask for segregation in those cases.
Versions affected
v53.3
The text was updated successfully, but these errors were encountered: