Replies: 1 comment
-
This is similar to #205 - but it looks like a data issue in OSM, if you fix the height tag in OSM it should make it into the next daily build. That being said, I think it does make sense to put a check for unrealistic values on parsing the height tag. Either that or we can reject values that have commas in them, which will have false positives. Can someone survey what the tagging guidelines and existing data has about commas? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey all,
just noticed that height entries with commas in OSM like "89,10" are parsed as "8910" resulting in a 9km tall column if extrapolated:
It's about this gasometer in Rome: https://www.openstreetmap.org/way/26840361#map=17/41.869573/12.480705
The Burj Khalifa as tallest building in the world is below 1000m so it might generally make sense to add such a max value in the planetiler config. Also, how to make sure, these OSM values are parsed correctly? I assume that in this example "89.1m" were actually meant, so might sanitizing the height string by replacing comma with dot already do the job?
Style I'm using
Beta Was this translation helpful? Give feedback.
All reactions