#256 closed enhancement (wontfix)
Support GeometryCollection as argument in Spatial Relationship functions
| Reported by: | andi | Owned by: | pramsey |
|---|---|---|---|
| Priority: | critical | Milestone: | PostGIS 1.4.1 |
| Component: | postgis | Version: | 1.4.X |
| Keywords: | GeometryCollection, Geometry, relationship, function | Cc: |
Description
Functions like ST_Intersects() still do not support the GeometryCollection type as argument. I have implemented a wrapper in plpgsql, which loops over collection geometries, but this inacceptably inperformant.
A native implementation makes sense because other multi geometries are supported, too.
The docs for 1.4 still warn not to use GeometryCollection as argument, so I think milestone 1.4.1 is correct.
Attachments (1)
Change History (4)
by , 15 years ago
| Attachment: | ST_Intersects_.sql added |
|---|
comment:1 by , 15 years ago
| Type: | defect → enhancement |
|---|
comment:2 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Because of the interaction between GEOS and PostGIS, this ends up being a lot more complex than one would like to solve at the PostGIS level. I am ticketing this in GEOS instead (http://trac.osgeo.org/geos/ticket/298) and hopefully it will be resolved there.
comment:3 by , 12 years ago
| Version: | 1.4 → 1.4.X |
|---|
Note:
See TracTickets
for help on using tickets.
Implementation of a wrapper for ST_Intersects() in plpgsql