[geos-devel] PR for new GeometryFixer API

[Paul Ramsey]

I've changed the CAPI, this kind of follows Dan's suggestion for an optional signature that can encompass all the behaviours, while leaving the no-parameters default in place. 

https://github.com/libgeos/geos/pull/433/files#diff-cbedc388a4d6d798494e26f51269040e8131b7c3e610b4fb4a792aee4b27e83eR1247-R1289

I still think the default should probably be changed to the new algorithm, but by merging this and then exposing similar switches in PostGIS we can easily try out both and people can see the benefits / drawbacks of the new approach. Since we're still developing, we can also take in feedback ot make the new approach even better.

P

> On Apr 16, 2021, at 1:08 PM, Martin Davis <mtnclimb at gmail.com> wrote:
> 
> JTS recently had a class called GeometryFixer added.  The class provides functionality to accept any invalid geometry and convert it to a valid one.  This plugs a noticeable gap in the JTS API!
> 
> Paul R has ported this to GEOS:  https://github.com/libgeos/geos/pull/433
> 
> It performs a similar function to the existing GEOS MakeValid (which was a port of the PostGIS ST_MakeValid).  But it has some differences in semantics which are simpler and (hopefully) a useful alternative.
> 
> See the PR for links to documentation of the functionality of GeometryFixer (and there will be more docs and images coming soon).
> 
> Feedback is welcome, as always.
>  
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel