Opened 12 years ago
Closed 6 years ago
#2055 closed defect (fixed)
Intersection with a result from Intersection fails
Reported by: | bscholten | Owned by: | pramsey |
---|---|---|---|
Priority: | high | Milestone: | PostGIS GEOS |
Component: | postgis | Version: | 1.5.X |
Keywords: | Intersection | Cc: |
Description
Basic problem:
Following query gives an error:
SELECT ST_Intersection(ST_Intersection(first_column, second_column), third_column) FROM test_bug_situation
The error returned is:
NOTICE: TopologyException: no outgoing dirEdge found at 184311.56259997687 319320.99999998196
ERROR: GEOS Intersection() threw an error!
Fout
ERROR: GEOS Intersection() threw an error! SQL status:XX000
ST_IsValid and ST_IsSimple both return true for all columns and ST_Intersection(first_column, second_column).
Switching the columns doesn't throw an error: ST_Intersection(ST_Intersection(first_column, third_column), second_column) or ST_Intersection(ST_Intersection(third_column, second_column), first_column)
Extra information:
Postgres version: "PostgreSQL 8.4.12, compiled by Visual C++ build 1400, 32-bit" Postgis full version: "POSTGIS="1.5.5" GEOS="3.3.5-CAPI-1.7.5" PROJ="Rel. 4.6.1, 21 August 2008" LIBXML="2.7.8" USE_STATS" Tested on windows platform.
See accompanying bug_report_XYZ_column_base64 for each geometry encoded in base64 Encoded WKB.
Same test with POSTGIS 1.4.2 on both Windows and Linux has same results.
Attachments (3)
Change History (13)
by , 12 years ago
Attachment: | intersection_bug_report.zip added |
---|
comment:1 by , 12 years ago
Milestone: | PostGIS 1.5.6 → PostGIS 1.5.7 |
---|
comment:2 by , 12 years ago
Milestone: | PostGIS 1.5.7 → PostGIS 1.5.8 |
---|
comment:3 by , 12 years ago
Milestone: | PostGIS 1.5.8 → PostGIS GEOS |
---|
follow-up: 6 comment:4 by , 12 years ago
Priority: | medium → high |
---|
Hi bscholten could you be so kind and upload the geometries as WKB strings..I amexperiencing problems with the base64 format here..thanks a lot!
comment:5 by , 12 years ago
to be more specific: the 3rd column doesn't get imported,ERROR: invalid end sequence
by , 12 years ago
Attachment: | intersection_bug_report_WKB.zip added |
---|
files containing WKB geometries
follow-up: 7 comment:6 by , 12 years ago
Replying to rajanski:
Hi bscholten could you be so kind and upload the geometries as WKB strings..I amexperiencing problems with the base64 format here..thanks a lot!
Uploaded geometries with WKB strings now, let me know if this works or if I should export them some other way.
comment:7 by , 12 years ago
Hi,still doesnt work..could you upload a plain sql dump of the whole table?
Replying to bscholten:
Replying to rajanski:
Hi bscholten could you be so kind and upload the geometries as WKB strings..I amexperiencing problems with the base64 format here..thanks a lot!
Uploaded geometries with WKB strings now, let me know if this works or if I should export them some other way.
comment:9 by , 6 years ago
Works in PostGIS 2.5.2:
SELECT
ST_Intersection(ST_Intersection(habitat_geometry, hexagon_geometry), variant_geometry)
FROM test_bug_situation;
01030000204071000001000000040000005ACC192B5C7F0641115BD5F5407D1341C66D3480BC7F064100000000647D13411601A9C8947F0641115BD5F5407D13415ACC192B5C7F0641115BD5F5407D1341
comment:10 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Zip file containing geometries causing the problem