[postgis-tickets] [PostGIS] #3298: ST_3DClosestPoint, ST_3DLongestLine, ST_3DMaxDistance regression between 2.1.8 and 2.2.0rc1

[PostGIS]

#3298: ST_3DClosestPoint, ST_3DLongestLine, ST_3DMaxDistance  regression between
2.1.8 and 2.2.0rc1
----------------------+---------------------------
  Reporter:  robe     |      Owner:  nicklas
      Type:  defect   |     Status:  closed
  Priority:  high     |  Milestone:  PostGIS 2.2.0
 Component:  postgis  |    Version:  trunk
Resolution:  fixed    |   Keywords:
----------------------+---------------------------

Comment (by nicklas):

 The tin/empty thing I think was a missing check in 2.1, if I recall right.

 The change in answer is the result of #2034.

 But your first example might reveal a problem. Is it right to return 2d
 from a 3d function? I think we have said before that the answer shall be
 3d. But then, what z-value to use? the result of #2034 is about that
 unknown is not 0. so 0 shouldn't be the answer. Is NULL an option or is 2d
 the best way to go?

 What does ST_force3d put in z-coord whith 2d as input?

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