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

 Yah I was thinking about that.  There is no good z to use.  I think the
 only thing we could do is return same answer as 2D (whic is what you are
 doing) or return an error (which assumes the user accidentally used 3D
 functon when they wanted 2D).  I would just leave it as is.

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