[geos-devel] [GEOS] #725: GEOS allows relate ops on GeometryCollection, while JTS and PostGIS do not

[GEOS]

#725: GEOS allows relate ops on GeometryCollection, while JTS and PostGIS do not
------------------------+---------------------------
 Reporter:  mwtoews     |       Owner:  geos-devel@…
     Type:  task        |      Status:  new
 Priority:  minor       |   Milestone:  GEOS Future
Component:  Default     |     Version:  3.1.0
 Severity:  Unassigned  |  Resolution:
 Keywords:              |
------------------------+---------------------------

Comment (by sirsigurd):

 Replying to [comment:3 strk]:

 > I suggest to put the checks back in place.
 I don't think it's a good idea because of these reasons:

 1. it breaks backward compatibility
 1. the reason to have this restriction is that it's hard to implement
 operations efficiently for collections, not because these operations on
 collections are invalid
 1. it's seems that there is a simple fix (but probably inefficient) that I
 suggested in #752: if operation is performed on collection, then just use
 their `UnaryUnion`, because union doesn't return collections with
 overlapping components

--
Ticket URL: <https://trac.osgeo.org/geos/ticket/725#comment:6>
GEOS <http://trac.osgeo.org/geos>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).