[postgis-tickets] [PostGIS] #5557: Potential bug in the ST_3DIntersects function.

[PostGIS]

#5557: Potential bug in the ST_3DIntersects function.
----------------------+---------------------------
  Reporter:  Wenjing  |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  high     |  Milestone:  PostGIS 3.4.1
 Component:  postgis  |    Version:  3.4.x
Resolution:           |   Keywords:
----------------------+---------------------------
Comment (by mdavis):

 The issue is due to the inherent inaccuracy of finite-precision floating
 point arithmetic. There's a lot of arithmetic being carried out, so the
 likelihood of 2 transformed intersecting lines NOT intersecting in 3D is
 very high.

 You can't rely on topological relationships being preserved through
 floating-point operations. This is the essence of the well-known issue of
 geometrical robustness failures. The solution is usually either to use
 exact arithmetic (often impractical) or use tolerance values (not a
 panacea, but very often works).
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5557#comment:1>
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.