+1 for flipping to OverylayNG On Thu, Jul 15, 2021 at 11:01 AM Paul Ramsey <[email protected]> wrote:
> Just stumbled over this old stub, > > https://github.com/libgeos/geos/blob/main/capi/geos_ts_c.cpp#L1425 > > In addition to GEOSUnaryUnion, which calls a cascaded union as required, > we have this explicit hook into cascaded polygon union in the C API. It > seems a little duplicative, which is not a high crime, but it also has a > hidden feature: unlike UnaryUnion which calls the new NG routines in "safe > sequence" (try full precision, fall back to gentle snapping, fall back to > snap rounding), this CAPI GEOSUnionCascaded call uses the > ClassicUnionStrategy, which is to say the *old* overlay functions and the > HeuristicOverlay fallbacks (various forms of bit stripping and precision > reduction). > > Question: > - just remove this API end point entirely? > - flip it over to also use NG semantics? > - don't touch that you fool, it's important to have it as it is! > > thanks, > P > _______________________________________________ > geos-devel mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/geos-devel >
_______________________________________________ geos-devel mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/geos-devel
