[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):

 I'd like to throw an error as I think comparing a 2D and 3D is highly
 illogical and anyone who does it is probably misinformed and should be
 told to use ST_ClosestPoint.

 pramsey says the same force to 0 exists in &&& so the problem seems more
 pervasive.  I'd wait off on doing anything.

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