[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:  new
  Priority:  high     |  Milestone:  PostGIS 2.2.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by nicklas):

 Ok, this is a little scary.

 When dealing with mixed dimensionality in #2034 I put check to not let
 multi-geometries through.

 But now I cannot see the problem to just let them go through. It seems to
 work as expected, and I have an idea about why I was afraid of it.

 But I think and hope that I was wrong then because not that check is
 removed.

 Please test this. What it is about is different combinations of
 multi/multi, multi/single in ST_3DClosestPoint and ST_3DShortestLine

 The problem is that it is so hard to verify if the answer is right more
 than in the most simple examples.

 commit in r14179

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