mortewle

Thanks for the answer! gdf2 is a single polygon because I tried to make this issue as specific as possible (this single polygon is the one that fails). This is...

I have tried to reproduce the error in geosop, with one geometry at a time, but it succedes. As does geopandas/shapely when done one geometry at a time. But that...

Thank you for looking into this! This indeed fixes the GEOSException, and, at first glance, seems to give the correct results when exploding geometrycollections and fixing the geometries. Your suggestion...

@dr-jts Are there any plans for a rework of the snapping algorithm in the near future? Or similar coverage cleaning functions.

Thanks for the answer @pramsey! Context: we are in the process of refactoring a statistics production previously done without trouble in ArcGIS, so these kinds of differences are interesting. I...

Not running PostGIS, but geopandas/shapely. The shapely overlay operations offer a grid_size parameter, which looks like what GEOSIntersectionPrec is doing. I have tried this previously, with no success (a lot...

Yes, this example works correctly with 1e-6 rounding for me as well, thanks! The rounding of the coordinates is not a big issue in this production, but it might be...

@dr-jts I would very much favor the expensive and robust area check you mention in https://github.com/locationtech/jts/issues/1000. These bugs seem to happen quite a lot in the land use dataset I...

@dr-jts Yes, the small holes returned from GEOSOP are legitimate, but not the larger ones returned from QGIS/shapely with different GEOS versions (so probably not relevant here). Removing slivers would...

The original data is of high quality, but we are combining a bunch of datasets, which results in a whole lot of edge cases. Lucky indeed! I cannot really use...