[geos-devel] [GEOS] #572: Contains issue for complex LineStrings [JTS fails too]

[GEOS]

#572: Contains issue for complex LineStrings [JTS fails too]
------------------------+---------------------------------------------------
 Reporter:  mwtoews     |       Owner:  geos-devel@…              
     Type:  defect      |      Status:  new                       
 Priority:  major       |   Milestone:  3.3.5                     
Component:  Default     |     Version:  3.3.4                     
 Severity:  Unassigned  |    Keywords:  jtsfail                   
------------------------+---------------------------------------------------
 This issues was first identified by Julia via
 [https://github.com/Toblerity/Shapely/issues/17 Shapely #17].

 With non-simple A and simple B:
 {{{
 A: LINESTRING (1 0, 0 2, 0 0, 2 2)
 B: LINESTRING (0 0, 2 2)
 }}}

 Compare DE-9IM results. First with Shapely (1.2.14, with GEOS C API 1.7.1;
 also verified with PostGIS 2.0 with 3.3.3-CAPI-1.7.4):
 {{{
 A.relate(B) : 101F001F2
 B.relate(A) : 1F100F102
 }}}

 JTS (1.12.0):
 {{{
 AB : 001F001F2
 BA : 0F100F102
 }}}

 The expected intersection matrix should be (based on {{{LINESTRING (2 0, 0
 2, 0 0, 2 2)}}}):
 {{{
 AB : 101F00FF2
 BA : 1FF00F102
 }}}

 Related issues are apparent with "Contains" ({{{T*****FF*}}}), which
 return False for AB and BA combinations for both JTS and GEOS. This result
 is consistent with the DE-9IM relate patterns. The expected result for AB
 is True (and False for BA).

-- 
Ticket URL: <http://trac.osgeo.org/geos/ticket/572>
GEOS <http://geos.refractions.net/>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).