#782 closed defect (fixed)
Collection with Empty components crashes overlay
Reported by: | pramsey | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 3.7.0 |
Component: | Default | Version: | main |
Severity: | Unassigned | Keywords: | |
Cc: |
Description
This example from PostGIS crashes within GEOS:
select st_intersects( 'LINESTRING(10 0, 0 0, 0 10)'::geometry, 'MULTILINESTRING((10 -1,-1 10),EMPTY)'::geometry )
Attachments (1)
Change History (7)
comment:1 by , 8 years ago
Milestone: | 3.5.1 → 3.5.2 |
---|
comment:2 by , 6 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I tried this on
POSTGIS="2.4.4 r16526" PGSQL="100" GEOS="3.6.2-CAPI-1.10.2 4d2925d" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 2.2.4, released 2018/03/19" LIBXML="2.7.8" LIBJSON="0.12" LIBPROTOBUF="1.2.1" RASTER PostgreSQL 10.3, compiled by Visual C++ build 1800, 64-bit
and returns true.
I'm dismissing this as a works for me.
comment:3 by , 6 years ago
Priority: | blocker → major |
---|---|
Resolution: | worksforme |
Status: | closed → reopened |
Definitely still an issue. I think PostGIS may remove the empty components before passing the geometry over to GEOS.
comment:4 by , 6 years ago
Milestone: | 3.5.2 → 3.8.0 |
---|
comment:6 by , 6 years ago
Milestone: | 3.8.0 → 3.7.0 |
---|
Note:
See TracTickets
for help on using tickets.
Ticket retargeted after milestone closed