[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 pramsey):

 I'm not sure I understand why even things like invalid multipolygons
 cannot be amenable to predicate evaluation?

 A Intersects B... if any element A intersects any element of B, A
 intersects B
 A Contains B... if all elements of B are contained by at least one element
 of A, and are disjoint from all other elenents of A, then A contains B
 A Touches B... if all elements of A touch an element of B, and are
 disjoint from all other elements of B, then A touches B

 I mean, Relate() is not possible, but it feels like the boolean
 predicates, which are made up of some "obvious" interactions and other
 "ok, I can kind of believe that" intersection (do we really believe
 "crosses" is well defined between two polygons?) do have plausible rules
 that can be at least made up for GCs.

 Feel free to tear me apart on this.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4749#comment:4>
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.