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

Gratuitous crossing:markings=yes #10474

Open
hungerburg opened this issue Sep 22, 2024 · 4 comments
Open

Gratuitous crossing:markings=yes #10474

hungerburg opened this issue Sep 22, 2024 · 4 comments

Comments

@hungerburg
Copy link

URL

No response

How to reproduce the issue?

A local user whom I know is quite affine to click iD-editor validator suggestions without much looking at what the problem is recently "upgraded" dozens of bus_stops and crossings:

Everywhere there is a "marked" crossing, there now also is "crossing:markings=yes" specified. I did ask. They told me, this is not wrong, as it makes it even more clear, that there are markings there.

I read the documentation - https://wiki.openstreetmap.org/wiki/DE:Key:crossing:markings - there it says: yes means unknown type of markings - so yes is wrong, the type of markings might be unknown to the validator - but it can be seen on the aerial without much trouble.

Please reconsider: Any bot can make such edits. iD should use the human work-force more constructively. Mapper time may be free, but it can be used to perform actual improvements to the data instead of being wasted.

Screenshot(s) or anything else?

No response

Which deployed environments do you see the issue in?

No response

What version numbers does this issue effect?

2.30.2

Which browsers are you seeing this problem on?

No response

@rskedgell
Copy link

If a mapper can see what the markings are in the available imagery, they can and should tag a relevant, documented and useful value. If they can't see what the markings are, they should not be adding this tag at all.

@hungerburg
Copy link
Author

Meanwhile I used the tag as a kind of crossing:markings=fixme note and downloaded a hundred from overpass. Our aerials are more than good enough to spot what is there. All but two were zebra crossings, no wonder in Austria. Two were unmarked crossings but they had a wrong crossing_ref=zebra specified before the so-called fixme was added. Wonder if that triggers the validator?

@rskedgell
Copy link

If/when iD stops encouraging users to add crossing:markings=yes, it would be nice to have it added to QA tools like Osmose as a possible tagging error to check.

@osmuser63783
Copy link

I'm fairly sure this needs to be reported as an issue in https://github.com/openstreetmap/id-tagging-schema instead.

I'm not sure which part of which preset exactly suggests that highway=crossing crossing=marked is "incomplete" and highway=crossing crossing=marked crossing:markings=yes is "complete" but I think the answer will be somewhere in there, and related to the marked crossing preset: https://github.com/openstreetmap/id-tagging-schema/blob/a7037f96cd817dc46971ae8573f4a7d7e2cb1f18/data/presets/highway/crossing/_marked.json

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