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
When building multipolygons, Osmium detects intersections between way segments and doesn't build the multipolygons in these cases. This is because valid polygons aren't allowed to have intersections and having only valid polygons makes further processing much easier.
Ideally all those cases will be fixed in the OSM data and Osmium can report where those intersections are to help in fixing them. We want to manually look at those places and fix them, because most often the intersections are a sign of a bigger problem with the data.
But at least as an option it would be nice to be able to fix those polygons by introducing "pseudo nodes" at the places where the intersections are. This will at least make the polygons valid allowing further processing. Implementation should not be too difficult, but there are a lot of corner cases to be done correctly. A "proper" intersection in the form of an X is probably easy, but what about segments that are on the same line, etc.
The text was updated successfully, but these errors were encountered:
When building multipolygons, Osmium detects intersections between way segments and doesn't build the multipolygons in these cases. This is because valid polygons aren't allowed to have intersections and having only valid polygons makes further processing much easier.
Ideally all those cases will be fixed in the OSM data and Osmium can report where those intersections are to help in fixing them. We want to manually look at those places and fix them, because most often the intersections are a sign of a bigger problem with the data.
But at least as an option it would be nice to be able to fix those polygons by introducing "pseudo nodes" at the places where the intersections are. This will at least make the polygons valid allowing further processing. Implementation should not be too difficult, but there are a lot of corner cases to be done correctly. A "proper" intersection in the form of an X is probably easy, but what about segments that are on the same line, etc.
The text was updated successfully, but these errors were encountered: