[postgis-tickets] [PostGIS] #3298: ST_3DClosestPoint, ST_3DLongestLine, ST_3DMaxDistance regression between 2.1.8 and 2.2.0rc1 (was: ST_ClosestPoint 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:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.2.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 These may just require change in error messages and a breaking change
 notice.

 The issue is not just limited to polyhedralsurfaces. I thought it was
 maybe any 2D, but while this:
  fails (ST_3DLongestLine fails as well) -- works in 2.1.8

 {{{

 SELECT ST_3DClosestPoint('LINESTRING(-11.1111111 55,55
 -11.1111111)'::geometry,'MULTILINESTRING((-10 40,40 -10),(-10 55,55
 -10),(-10 70,70 -10),(0 40,40 0),(0 55,55 0),(0 70,70 0),(10 40,40 10),(10
 55,55 10),(10 70,70 10),(20 40,40 20),(20 55,55 20),(20 70,70 20),(30
 40,40 30),(30 55,55 30),(30 70,70 30),(40 55,55 40),(40 70,70 40),(50
 40,40 50),(50 55,55 50),(50 70,70 50))'::geometry)
 }}}


 {{{
 ERROR:  Unsupported geometry type: MultiLineString
 }}}

 This works:


 {{{
 SELECT ST_3DLongestLine('LINESTRING(1 2, 3 4)'::geometry, 'LINESTRING(1 2,
 3 5)'::geometry);

 }}}

 This fails:


 {{{
 SELECT ST_3DLongestLine('LINESTRING(1 2, 3 4)'::geometry,
 ST_Multi('LINESTRING(1 2, 3 5)'::geometry))

 }}}

 Why whether a string is multi or not I don't know why that would make a
 difference.

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