Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1055 closed defect (fixed)

GEOSInterpolate() segfaults on empty geometry collections

Reported by: caspervdw Owned by: strk
Priority: minor Milestone: 3.8.2
Component: C API Version: 3.8.0
Severity: Unassigned Keywords:
Cc:

Description

Hi GEOS developers,

I am working on PyGEOS, a fast python wrapper for GEOS. While testing the GEOSInterpolate() we encountered segfaults on particular empty geometries. The full list is below.

In ​https://trac.osgeo.org/geos/ticket/926 this was already fixed for the empty linestring and linearring, but the issue persists for empty collections and on collections with the first geometry being empty, for example:

  • MULTIPOINT EMPTY
  • MULTILINESTRING EMPTY
  • MULTILINESTRING Z (EMPTY, (0 0 0, 1 1 0))
  • MULTIPOLYGON EMPTY
  • GEOMETRYCOLLECTION EMPTY
  • GEOMETRYCOLLECTION Z (LINESTRING EMPTY, POINT (1 1))

See related PyGEOS issue ​https://github.com/pygeos/pygeos/pull/208

Change History (5)

comment:1 by strk, 4 years ago

Status: new → assigned

Thanks for the report, I'm on it

comment:2 by Sandro Santilli <strk@…>, 4 years ago

In 27516e0/git:

Surivive empty collection from GEOSInterpolate

References #1055 in master branch (3.9.0dev)

comment:3 by Sandro Santilli <strk@…>, 4 years ago

Resolution: → fixed
Status: assigned → closed

In bc5429f/git:

Surivive empty collection from GEOSInterpolate

Fixes #1055 in 3.8 branch (3.8.2dev)

comment:4 by strk, 4 years ago

Milestone: → 3.8.2

comment:5 by caspervdw, 4 years ago

That was fast. Thanks a lot!

Note: See TracTickets for help on using tickets.