[postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values

[PostGIS]

#2034: ST_3DClosestPoint with mixed dimensionality in input values
-------------------------+--------------------------------------------------
 Reporter:  nicklas      |       Owner:  nicklas      
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.0.2
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------
 In the example in #2034, there is input of 2d and 3d. ST_3DClosestPoint
 then by design assumes that the 2d value have a zero Z-value. But I guess
 it is more like undefined.

 So I think that the most correct solution maybe is to handle the POINT(6
 0) in ST_3DClosestPoint function as a infinite vertical line crossing
 POINT(6 0). Then the answer would be what strk expects in #2032.

 I want feedback before I try to do anything about it.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2034>
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.