It’s a big feature deal but I tend towards wanting to stick to semver... not until we break backwards compatibility
On Wed, Nov 11, 2020 at 5:04 PM Daniel Baston <dbas...@gmail.com> wrote: > This strikes me as a big deal - any thoughts on calling the next release > GEOS 4? > > Dan > > On Tue, Nov 3, 2020 at 5:45 PM Paul Ramsey <pram...@cleverelephant.ca> > wrote: > >> The switch has been flipped. >> If you build GEOS without any options, you will get the OverlayNG engine >> backing the standard geometry functions. >> >> geom->union() >> geom->intersection() >> geom->symdifference() >> geom->difference() >> geom->unaryunion() >> >> The unit and XML tests that differed from the old engine have been >> updated to match the new NG outputs. That means if you use the >> --disable-overlayng option in autotools or the DISABLE_OVERLAYNG option in >> cmake, not all tests will pass anymore. NG is the new normal. >> >> P. >> >> On Fri, Oct 30, 2020 at 1:10 PM Regina Obe <l...@pcorp.us> wrote: >> >>> +1 for flipping the switch. >>> >>> >>> >>> I don’t know what “light your hair on fair” means J >>> >>> >>> >>> >>> >>> *From:* geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] *On >>> Behalf Of *Paul Ramsey >>> *Sent:* Friday, October 30, 2020 3:47 PM >>> *To:* GEOS Development List <geos-devel@lists.osgeo.org> >>> *Subject:* [geos-devel] OverlayNG as Default >>> >>> >>> >>> OK, it's been a while, and I'd like to flip over GEOS master to use >>> OverlayNG as the engine behind >>> >>> >>> >>> Geometry.intersection() >>> >>> Geometry.difference() >>> >>> Geometry.union() >>> >>> Geometry.symdifference() >>> >>> Geometry.unaryunion() >>> >>> >>> >>> That will entail changing the expected outputs for a few of the >>> regression tests, as detailed here. >>> >>> >>> >>> >>> https://docs.google.com/document/d/1TDm2aR4a7O41-soS-25Xog1EdQcjmvKCnKltxjbxOC0/edit#heading=h.ojs23hjdmk7a >>> >>> >>> >>> Once that is done, regressions in PostGIS and other downstream projects >>> can be #ifdef'ed around GEOS version. As seen in the document above, there >>> actually aren't than many cases that need special handling in PostGIS, and >>> hopefully not in other downstream projects. >>> >>> >>> >>> If you have any concerns, please light your hair on fair in the next >>> couple days. >>> >>> >>> >>> P. >>> _______________________________________________ >>> geos-devel mailing list >>> geos-devel@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/geos-devel >> >> _______________________________________________ >> geos-devel mailing list >> geos-devel@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/geos-devel > > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel