<div dir="ltr">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.<br><div><br></div><div>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.)<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 18, 2023 at 3:56 PM Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">We have quite a few of them? Which one should be keep and bind into CAPI?<br>
<br>
geos/operation/union/CoverageUnion.h<br>
geos/operation/overlayng/CoverageUnion.h<br>
geos/coverage/CoverageUnion.h<br>
_______________________________________________<br>
geos-devel mailing list<br>
<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br>
</blockquote></div>