Opened 14 years ago

Closed 13 years ago

#700 closed defect (fixed)

ST_Boundary collection of empties crashes

Reported by: robe Owned by: pramsey
Priority: medium Milestone: PostGIS 2.0.0
Component: postgis Version: master
Keywords: Cc:


Is it too early to be complaining about more of these: you seem to be able to handle the single cases okay now but not the nested case.


Change History (2)

comment:1 by pramsey, 14 years ago

Yes, probably too early. Maybe you can come to the sprint and we can talk it out? The issue then becomes the definition of "empty". Right now lwgeom_is_empty() has a particular definition (has zero sub-elements) which is useful on some cases (if you want to extract the n-the element of a collection of empty things you still can) but not in others (like this ticket). Perhaps I just need two definitions ("has zero subelements" and "has no spatial definition") to apply in different cases. But it's an annoying conundrum, and a bit of a waste of time until we get the core functionality in place again on new foundations.

comment:2 by robe, 13 years ago

Resolution: fixed
Status: newclosed

With latest trunk this seems to be non-issue

Now gives acceptable error and no longer crashes

ERROR:  GEOSBoundary: IllegalArgumentException: Operation not supported by GeometryCollection
Note: See TracTickets for help on using tickets.