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

 Slight correction to my previous statement.  I odn't like the infinite
 line idea because your shortest line / ST_3DClosestPoint for one side case
 ends up returning an object that is not on the point.  And what pretell
 will you do when someone asks for a 3D Point / 2 Polygon - you have an
 infinite polyhedral?

 I don't like the current 0 case either because there isn't any reason in
 my mind why Z=0 is different from any other Z. So in short Z should be
 like NULL, not 0 and NOT inifinity when not specified.

 The answer to an undefined element make the whole operation undefined.
 That to me was one of the benefits of breaking out 3D functions from 2D.
 so we don't have to entertain these ambiguous questions.

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