I've figured out a fix for the performance reqression and it's now in GEOS master. My testing using the sample data provided above indicates it's at least 10x faster, so essentially eliminating the performance regression in this case (and it should provide that for most situations)
If anyone can test further to confirm it is indeed faster and most importantly correct that would be great. On Thu, Apr 11, 2019 at 1:03 PM Martin Davis <[email protected]> wrote: > Well, we have figured out what the problem is - it's a known regression in > the GEOS UnaryUnion code, reported in this ticket [1] > > Unfortunately there's no fix for this yet, but we'll try and escalate this. > > [1] https://trac.osgeo.org/geos/ticket/867 > > >
_______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users
