> On Jul 15, 2021, at 1:01 PM, Paul Ramsey <pram...@cleverelephant.ca> 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?
I would prefer noop'ing it and setting an error than removing entirely
> - flip it over to also use NG semantics?
This is what you actually want, right? I do.
> - don't touch that you fool, it's important to have it as it is!
Users can continue to run older versions of the code at their discretion.
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
