You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: