On Fri, Oct 16, 2020 at 11:59 AM Roger Bivand <roger.biv...@nhh.no> wrote:
> Cases 794 and 936 are all-by-all intersections, and as noted in the latter > issue, the problems occurring differ by input order. > Well, that's disappointing that 794 and 936 still have failures. Especially because 794 was also reported as JTS 300: https://github.com/locationtech/jts/issues/300 and the test data there is incoporated in the robustness test suilte in both JTS [1] and GEOS [2] , where it passes using OverlayNG. Is there any way to get a dump of the actual input geometries to GEOS which are causing these errors? [1] https://github.com/locationtech/jts/blob/master/modules/tests/src/test/resources/testxml/robust/overlay/TestOverlay-jts-300.xml [2] https://git.osgeo.org/gitea/geos/geos/src/branch/master/tests/xmltester/tests/robust/overlay/TestOverlay-jts-300.xml
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
