Skip to content
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

Show geometry for crossing quests #3599

Closed
Helium314 opened this issue Dec 18, 2021 · 2 comments
Closed

Show geometry for crossing quests #3599

Helium314 opened this issue Dec 18, 2021 · 2 comments
Assignees

Comments

@Helium314
Copy link
Collaborator

I noticed that sometimes people confuse crossings with other nearby crossings.
See https://www.openstreetmap.org/node/8615277295 and https://www.openstreetmap.org/node/6557473402 which both have an incorrect crossing:island=yes, likely because there actually is a island at a different nearby crossing.

Showing geometry should help people with identifying the correct crossing.

(I was originally going to suggest not asking for crossings that are not part of a road, but showing geometry should help as well, and in more cases)

@westnordost
Copy link
Member

Geometry of what?

@westnordost westnordost added the feedback required more info is needed, issue will be likely closed if it is not provided label Dec 18, 2021
@Helium314
Copy link
Collaborator Author

Right, that was quite ambiguous...
Showing nearby crossings was the idea. Probably nodes with highway=crossing (if not excluded by some other filter, like the exclusion of driveways). I thought about ways with footway/cycleway=crossing, but showing them might be bad because this is not tagged at many crossings.

@matkoniecz matkoniecz removed the feedback required more info is needed, issue will be likely closed if it is not provided label Dec 20, 2021
@westnordost westnordost self-assigned this Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants