Opened 9 years ago
Closed 8 years ago
#3446 closed defect (wontfix)
[raster] Error with topology reported on clean geometries when using ST_Intersection
Reported by: | gdrolet | Owned by: | Bborie Park |
---|---|---|---|
Priority: | critical | Milestone: | PostGIS 2.2.3 |
Component: | raster | Version: | master |
Keywords: | raster ST_Intersectino | Cc: |
Description
I get the following error when using ST_Intersection (raster, geometry) in development version 2.3:
ERROR: GEOSIntersects: TopologyException: side location conflict at 1749960.0258611713 1220621.9908729347 CONTEXT: PL/pgSQL function _st_intersects(geometry,raster,integer) line 22 at RETURN PL/pgSQL function st_intersection(geometry,raster,integer) line 5 at assignment SQL function "st_intersection" statement 1
The call that generates this error is:
SELECT ST_Intersection(rt.rast, gt.geom) gv FROM raster_100x100_indb_single rt, polygons gt WHERE ST_Intersects(rt.rast, gt.geom) and gid = 7
Version with the error is:
postgis_full_version | POSTGIS="2.3.0dev r14604" GEOS="3.5.0-CAPI-1.9.0 r4090" PROJ="Rel. 4.9.1, 04 March 2015" GDAL="GDAL 2.0.1, released 2015/09/15" LIBXML="2.7.8" LIBJSON="0.12" RASTER
No error is thrown when using the exact same query on the exact same data with this version:
postgis_full_version | POSTGIS="2.1.8 r13780" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.11.1, released 2014/09/24" LIBXML="2.7. 8" LIBJSON="UNKNOWN" TOPOLOGY RASTER
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
gdrolet, Can you provide a sample raster that triggers the error?
I suspect there is nothing we can do about this as it's erroring out in GEOS, but just in case. I can also verify at least whether its fixed in the latest development GEOS versions.
comment:3 by , 9 years ago
Milestone: | PostGIS 2.2.2 → PostGIS 2.2.3 |
---|
comment:4 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I'm just going to dismiss this since I never got a response.
Note:
See TracTickets
for help on using tickets.
I also get the error using this version: