[postgis-tickets] [PostGIS] #5580: When encounting an empty geometry, potential bug in the ST_3DIntersects function

[PostGIS]

#5580: When encounting an empty geometry, potential bug in the ST_3DIntersects
function
---------------------+---------------------------
 Reporter:  Wenjing  |      Owner:  pramsey
     Type:  defect   |     Status:  new
 Priority:  medium   |  Milestone:  PostGIS 3.4.1
Component:  postgis  |    Version:  3.4.x
 Keywords:           |
---------------------+---------------------------
 Consider this query:

 {{{
 SELECT
 ST_3DIntersects(a1, a2)
 FROM ST_GeomFromText('GEOMETRYCOLLECTION Z (POINT Z EMPTY, POINT Z (0 0
 0))') As a1
 , ST_GeomFromText('POINT Z (0 0 0)') As a2;
 --excepted{t}; actual{f}
 }}}
 POINT Z (0 0 0) is the two geometries' intersection. So the excepted
 result of 3DIntersects is true.

 But the 3DIntersects function doesn't consider they intersect only when
 inserting an empty geometry before this point.

 Moreover, using the 2D Intersects function in this situation, we can get
 the expected result that they intersect.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5580>
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.