-
Notifications
You must be signed in to change notification settings - Fork 9
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
consider banning whosonfirst.mapzen.com labels #14
Labels
Comments
Yes, that's a good idea |
It seems that filtering should be readded in https://github.com/ENT8R/streetcomplete-mapstyle/blob/master/layers/labels.yaml#L20 |
ENT8R
pushed a commit
that referenced
this issue
Aug 21, 2019
low quality nonOSM source - duplicate, malformed, invalid labels unfixable in OSM would be confusing for OSM editors see tilezen/vector-datasource#1410 whosonfirst-data/whosonfirst-data#1008 whosonfirst-data/whosonfirst-data#1022 tilezen/vector-datasource#1418 fixes #14 (again), repeats #26 and fixes streetcomplete/StreetComplete#1527
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mapzen data includes nonOSM data.
I am unsure whatever I am unlucky or overall data quality is low but whosonfirst.mapzen.com dataset at least in my region is full of malformed, duplicated and invalid labels (reported as tilezen/vector-datasource#1410 whosonfirst-data/whosonfirst-data#1008 whosonfirst-data/whosonfirst-data#1022 tilezen/vector-datasource#1418 ).
In addition this project seems to be quite slow to update, even with provided PRs - see https://github.com/whosonfirst-data/whosonfirst-data/pulls?page=2&q=is%3Apr+is%3Aopen
Malformed labels from external source are likely to be confusing for OSM editors - so maybe it would be a good idea to exclude them?
The text was updated successfully, but these errors were encountered: