geos/coverage/CoverageUnion in fact delegates to geos/operation/overlayng/CoverageUnion. It's there to provide an API which is the same as the other coverage operations.
overlayng/CoverageUnion seems to be quite a bit faster than geos/operation/union/CoverageUnion, by my testing. So it has my vote.(They are both exposed in geosop, so independent verification is welcome.) On Tue, Apr 18, 2023 at 3:56 PM Paul Ramsey <pram...@cleverelephant.ca> wrote: > We have quite a few of them? Which one should be keep and bind into CAPI? > > geos/operation/union/CoverageUnion.h > geos/operation/overlayng/CoverageUnion.h > geos/coverage/CoverageUnion.h > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel >
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
