Hi Latvia community!
I bet some of you remember me from State of the Map Baltics last week, where I had a talk about TomTom’s cooperation with and contribution to OpenStreetMap.
As said during the presentation (which I think will be available shortly as a recording for those who could not attend) I want to share a couple of MapRoulette challenges that can help fix map issues in your country.
You’re welcome to try these out, and we appreciate any feedback you may have.
Challenge urls:
Fix inconsistent Bridge and Tunnel tagging: https://maproulette.org/browse/challenges/39498
You can find more information about each challenge in the description in MapRoulette.
Our editing team may also work on these challenges in a couple of week.
If you have another topic you’d like to discuss, or other map issues you’d like us to look into, feel free to send me a personal message or contact osm@tomtom.com.
Thank you!
Regards,
Tomasz
Hi, thank you for the interest in OSM data quality.
There seems to be very little information on what is actually checked - even the Maproulette task itself has just this:
Expectation
Identify and fix cases where the bridge or tunnel has an incorrect tag.
Origin of Leads
Based on OSM Wiki guidelines, we developed an FME workbench which detected inconsistently tagged bridges and tunnels.
Where could we find all the rules/cases that are included here?
Hi Rihards,
each task is attributed with detailed information in properties, where issue is described; we were reviewing the data based on bridge or tunnel tag and related components, like is layer correctly added to an element, if attributes are not contradicted, etc. Of course, if you want I can provide more detailed information per each 'issue type'.
Do you expect explicit layer=0
on tunnel
that is at ground level?
Description of layer=* says:
0 should not be used explicitly.
and
Features at layer 0 should not normally have a layer tag.
Hi i-ky,
We do not want to solve an error only to have that fixed. There are of course general capturing rules and exceptions out of that. If the tunnel is at the ground level, we are not pushing to solve this situation - we understand that it is not to be solved. For an exceptions, please, add a status 'Not an issue'. We are analyzing this kind of tasks after the challenge is done to see, what possible implementation can be done in our process, so there are less cases like that in our challenges.
It seems to me that it would be very helpful to have a description about what a challenge includes - "these are the things included here, and these are the exact conditions for each of them".
It manages the contributor expectations, and it could allow detecting any potentially controversial, risky or incorrect suggestions before some eager mapper creates a lot of changesets that need to be reverted :)
Last updated: Dec 22 2024 at 03:46 UTC