#1092: Fixed-precision overlay methods fail if inputs are mixed dimensions
--------------------------+---------------------------
Reporter: Brendan Ward | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.9.1
Component: Default | Version: master
Severity: Unassigned | Resolution:
Keywords: |
--------------------------+---------------------------
Comment (by Brendan Ward):
Perhaps there is additional validation in the fixed-precision methods?
GEOSIntersection returns the input geometry when that is intersected with
itself, without raising an error.
I see that the OverlayNG methods specifically check for this case:
https://github.com/libgeos/geos/blob/3.9/src/operation/overlayng/EdgeNodingBuilder.cpp#L194-L196
I wasn't able to easily find the counterpart for geometry collections in
the original overlay implementation.
Not arguing that this should work for mixed dimensions, only that the
behavior is different between the fixed and original operations, in case
it identifies a potential bug. In this case, it seems like OverlayNG is a
bit more strict, which is probably a good thing.
--
Ticket URL: <https://trac.osgeo.org/geos/ticket/1092#comment:2>
GEOS <http://trac.osgeo.org/geos>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite
(JTS).
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
