Even with --enable-overlayng, the ring orders are different from those
generated by OverlayNG in late October. At that stage we could
differentiate by typical ring order patterns, now something else has
changed and we cannot see whether OverlayNG is operative or not. Lots of
tests in R packages built against GEOS have relied on operations returning
ring-order identical polygons (or coord-order identical line segments)
compared with stored expected values.
Please clarify urgently: OverlayNG is not mentioned in NEWS, nor does it
appear as the last line in ./configure output; all I can see is
--disable-overlayng as a configure option. How can we test for the
presence of OverlayNG in the runtime? Recall that any user compiling from
source or any packager may use the configure argument.
Please do not simply rely on the version number, it is sufficiently
robust.
Roger
On Thu, 10 Dec 2020, Roger Bivand wrote:
Hi,
Please confirm that the 3.9.0 release will as advertised enable OverlayNG by
default. As lately as beta2 configure still seemed to need
--enable-overlayng. Ad-hoc tests from late October to detect ring order fail
without --enable-overlayng. I repeat that it is necessary to provide a clear
way to interrogate the runtime to find out whether it supports OverlayNG.
Next question - why no RC, is it fair to just go from beta to release?
Best wishes,
Roger
--
Roger Bivand
Department of Economics, Norwegian School of Economics,
Helleveien 30, N-5045 Bergen, Norway.
voice: +47 55 95 93 55; e-mail: roger.biv...@nhh.no
https://orcid.org/0000-0003-2392-6140
https://scholar.google.no/citations?user=AWeghB0AAAAJ&hl=en
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
