-
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
Highway crosses building validation feedback #5891
Comments
For reference, I added a similar request to KeepRight at keepright/keepright#93 Apparently there are cases where |
@bhousel raised a similar sentiment and I agree we could do better with highway/building crossings. The connection fix is somewhat useful when you want to add an entrance node or split the way and tag the part under the building as covered, but it doesn't do all the rest of that right now. Another option is for a fix that just tags the whole road as In any case, you're probably right that there should only be one issue here and not one per crossing. |
A real time saver where to have a one click action "Split this road and make the part that goes through the building a building_passage". Another solution might be #5900 to at least provide a place where people can read up on the different cases that one has to think about in such a situation. |
re: |
As I understand it the main differences between Automatically splitting and tagging the way gets complicated if the way crosses the building more than twice or goes through many adjoined buildings. |
So I removed the connection fix from building-highway crossings and made it so only one issue is created per building-feature pair instead of one per crossing. I think this is sufficient for now. The automatic splitting and covering idea seems pretty complicated so I'm not going to worry about it for this issue. |
Location:
&map=19.20/57.11650/-2.08751
Is this a valid quick fix? I think it would make more sense to recommend
covered
ortunnel=building_passage
.It's also a little confusing that the issue appears twice for the same entity (because it crosses twice).
The text was updated successfully, but these errors were encountered: