[postgis-tickets] [PostGIS] #4749: Improve behaviour of spatial predicates with GeometryCollection inputs

[PostGIS]

#4749: Improve behaviour of spatial predicates with GeometryCollection inputs
--------------------------+---------------------------
  Reporter:  mdavis       |      Owner:  pramsey
      Type:  enhancement  |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 3.1.0
 Component:  postgis      |    Version:  2.5.x
Resolution:               |   Keywords:
--------------------------+---------------------------

Comment (by Algunenano):

 > The following cases cannot be handled easily. They should report a
 appropriate, informative error:

 The main issue I see with this is that chaining calls might bug out for no
 good reason as current geos predicates return GeometryCollections (I know
 you tried to change it, but in the end it's still there). For example,
 with this change `ST_Intersects(ST_Intersection(A, B), C)` will fail if
 the result of `ST_Intersection(A, B)` returns a GC of a polygon and a
 line.

 I'm not saying the old behaviour was correct (since it's obvious it was
 failing per your examples), but we should have a good base so we stop
 getting those random `TopologyException` that everybody dislikes.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4749#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.