Opened 12 years ago
Closed 10 months ago
#572 closed defect (fixed)
Contains issue for complex LineStrings [JTS fails too]
Reported by: | Mike Taves | Owned by: | mdavis |
---|---|---|---|
Priority: | major | Milestone: | Upstream |
Component: | Default | Version: | 3.3.4 |
Severity: | Unassigned | Keywords: | jtsfail |
Cc: |
Description
This issues was first identified by Julia via 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).
Change History (13)
comment:1 by , 12 years ago
Milestone: | 3.3.5 → 3.4.0 |
---|
comment:2 by , 11 years ago
Milestone: | 3.4.0 → 3.5.0 |
---|
comment:5 by , 7 years ago
Milestone: | 3.7.0 → 3.8.0 |
---|
comment:6 by , 6 years ago
See also https://github.com/locationtech/jts/issues/270.
This branch may have a fix: https://github.com/locationtech/jts/tree/bug-test-intersects
comment:7 by , 5 years ago
Upstream ticket is https://github.com/locationtech/jts/issues/396
Still no solution for this.
comment:8 by , 5 years ago
Milestone: | 3.8.0 → 3.9.0 |
---|
comment:9 by , 3 years ago
Milestone: | 3.9.0 → GEOS Fund Me |
---|
comment:10 by , 3 years ago
Milestone: | GEOS Fund Me → Upstream |
---|
comment:12 by , 10 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:13 by , 10 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Still an issue