TomTom’s tekniska team har utfört en analys som identifierar och fixar inkonsekventa bro- och tunneltaggar. I ett försök att hjälpa samhället att lösa potentiella problem, lanserar vi en ny utmaning; Sweden - Fix inconsistent bridge and tunnel tagging.
Det finns information på GitHub-sidan och utmaningsbeskrivningen för att hjälpa dig att lösa uppgifterna, men tveka inte att kontakta mig om du har några frågor, kommentarer eller funderingar.
Ha det så bra och önskar er alla en trevlig redigering!
Salim
This will lead to more errors introduced. I’ve seen this changed many times. Often stating “fixing a problem” when the person has no clue if it is a bridge or a tunnel. A way crossing a stream is much better than someone creating a non existent tunnel (or bridge).
What is the actual problem being fixed? Where does it cause an issue?
I see I did write too much before reading what it actually was.
But I hope this challenge will not introduce as many false positives as some prevoius ones.
It looks like the challenge looks for layer +/- without bridge/tunnel and bridge/tunnel without layer=*
It’s ok as long as the user make the right choise but as Anders says, there is a rish people blindly slap on tags to get questpoints.
I’ve also seen places where people have crossed bridges with tunnels where there should only be a tunnel OR a bridge.
A while ago I did an overpass-search for waterways with layer tag and a way length > 100 m (or something like that), since waterways are usually not underground for so long distances.
But since it is almost impossible to see in aerial photos whether it is a tunnel, culvert or bridge where the waterway crosses a road, I only split the ways and gave it layer=-1 exactly where it crosses the road, not a longer distance.
Since it is almost impossible to see from aerial photos, I am a bit hesitant to the added value of this challange…
I think has flaws. I assume the query is layer=1 or layer=-1 without a bridge or tunnel.
