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

Remaining impact of broken polygon geometries #37

Open
imagico opened this issue Sep 11, 2017 · 0 comments
Open

Remaining impact of broken polygon geometries #37

imagico opened this issue Sep 11, 2017 · 0 comments

Comments

@imagico
Copy link

imagico commented Sep 11, 2017

Although this project is no more active i wanted to share some observations here regarding the remaining impact of broken polygon geometries in the OSM database, in particular w.r.t. osm2pgsql-dev/osm2pgsql#684.

Looking at the data actually used for the landcover and water areas layers in OSM-carto there are now remaining about 3600 landcover features and about 400 water area features that are broken in a way that prevent libosmium from handling them (that is either intersections or open rings AFAIK). This sounds like very few (about 0.01 percent - this is however not comparable to the numbers in osm2pgsql-dev/osm2pgsql#684 (comment) since i count only features that are actually rendered based on the tags) but the visual impact is still significant (i would say probably about half to one third of what was before the cleanup effort).

The most frequent tags among the 3600 landcover features are:

    102 natural=scrub
    103 landuse=grass
    113 landuse=meadow
    261 amenity=parking
    286 leisure=park
    389 landuse=forest
    392 landuse=farmland
    404 landuse=residential
    733 natural=wood

This might be of interest for release and rollout of future osm2pgsql versions using libosmium and for those who routinely process polygon data with libosmium - cc @joto, @lonvia, @pnorman, @woodpeck.

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

1 participant