Agreed about the need to handle each dimension of the input separately. Polygonal elements need to be reduced in a topologically correct way using OverlayNG PrecisionReducer, and other dimensions can just be reduced in pointwise fashion.
I intended this logic to go into GeometryPrecisionReducer, rather than OverlayNG PrecisionReducer, since that preserves the existing API. I see now that the logic there is not complete - it handles Polygonal geometries, but not collections containing Polygonal geometry. I'll ticket that for fixing in JTS. On Sun, Nov 29, 2020 at 9:38 AM Paul Ramsey <[email protected]> wrote: > Looking at PrecisionReducer::reducePrecision, it seems like it should > perhaps have a little extra logic so that each dimension of the input are > handled separately. Underlying the op is just > > OverlayNG ov(geom, nullptr, gf.get(), OverlayNG::UNION); > > >
_______________________________________________ geos-devel mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/geos-devel
