[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.1.0
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by robe):

 The logical place where I would think this should happen would be in one
 of our Force functions:

 http://www.postgis.org/documentation/manual-2.0SVN/ST_Force_3D.html
 http://www.postgis.org/documentation/manual-2.0SVN/ST_Force_3DZ.html

 It would be nice if those functions took an extra argument like the Z to
 force to or something to use for interpolation.

 BTW: I noticed these functions don't conform to our naming standard.

 Wondering if its time to fix that and also in the process throw in an
 extra arg that allows you to specify the Z to force to.  Seems silly it
 just goes to 0.

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