[postgis-devel] [PostGIS] #501: [wktraster] Implement a ST_Value based on world coordinates instead of raster coordinates

[PostGIS]

#501: [wktraster] Implement a ST_Value based on world coordinates instead of
raster coordinates
------------------------+---------------------------------------------------
  Reporter:  pracine    |       Owner:  pracine        
      Type:  defect     |      Status:  new            
  Priority:  medium     |   Milestone:  WKTRaster 0.1.6
 Component:  wktraster  |     Version:  trunk          
Resolution:             |    Keywords:                 
------------------------+---------------------------------------------------
Comment (by robe):

 Pierre,

 Not sure what you mean.
 st_value(rast raster, band integer, pt geometry)

 would be the one I would use for world coordinates.  The other one is
 totally unnecessary.

 The common use case is

 SELECT r.value,st_value(r.rasst, 1, ptgeom) as val
 FROM rastetable INNER JOIN geomtable  ON ST_Intersects(rastertable.rast,1,
 geomtable.ptgeom);

 Can't really think why one would ever want a

 st_value(rast raster, band integer, x float, y float)

 It would just add unnecessary confusion and function bloat to me.

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