[postgis-tickets] [PostGIS] #2645: ST_LineInterpolatePoint incorrect output for 3D linestring

[PostGIS]

#2645: ST_LineInterpolatePoint incorrect output for 3D linestring
------------------------------+---------------------------------------------
 Reporter:  bencaradocdavies  |       Owner:  pramsey      
     Type:  defect            |      Status:  new          
 Priority:  critical          |   Milestone:  PostGIS 2.1.2
Component:  postgis           |     Version:  2.1.x        
 Keywords:                    |  
------------------------------+---------------------------------------------

Comment(by pramsey):

 There's a lot of 2.5D thinking in the code base, in general, unless a
 function has a "3D" string in the signature. The linear referencing
 functions are certainly going to think that X/Y are the primary axes and
 other axes are along for the ride. I'm concerned about touching this in
 2.1 branch for fear it creates a "bug" for anyone who is working with 2.5D
 data expecting X/Y primacy. And generally concerned about changing the
 behaviour going forward. I don't think your interpretation is a slam dunk
 for all users.

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