[postgis-devel] ST_MakeValid() behaviour
raul at rmr.ninja
Sat Apr 17 13:12:02 PDT 2021
If it's better and faster I think it should replace the old function
completely. Also, keep in mind there is currently 2 ST_MakeValid (one
implementation in PostGIS and one in GEOS, although they should be
pretty much the same) and this makes it a 3rd, so I would start thinking
on dropping one (the PostGIS one IMO).
On 17/4/21 19:12, Paul Ramsey wrote:
> Coming soon to GEOS 3.10 is a new implementation of a "validity repairer", currently named GeometryFixer.
> Open question is whether to bind the GEOS default GEOSMakeValid() CAPI to it. It provides (we think, arguably) more "expected" outputs for various invalid cases, and is almost certainly faster than the existing implementation. On the other hand, it's *different*, so people would get different results from ST_MakeValid() depending on the GEOS version under their PostGIS.
> We could still leave the old algorithm *accessible*, via extra parameters and knobs and switches, as Dan notes in a comment on the PR. Question is, can we switch out the default behaviour, or are we going to end up with ST_MakeValid() and ST_GeometryFix() (or something).
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
More information about the postgis-devel