[postgis-tickets] [PostGIS] #2217: [raster] ST_AsBinary semantic discrepancy

[PostGIS]

#2217: [raster] ST_AsBinary semantic discrepancy
---------------------+------------------------------------------------------
 Reporter:  mloskot  |       Owner:  dustymugs
     Type:  defect   |      Status:  new      
 Priority:  medium   |   Milestone:           
Component:  raster   |     Version:  trunk    
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by dustymugs):

 Replying to [comment:18 mloskot]:
 > Replying to [comment:16 dustymugs]:
 > > > Let's turn this ticket this way:
 > > >  * I'm a user.
 > > >  * I have table with raster registered as out-db
 > > >  * I call SQL API.
 > > > How can I query and fetch complete blob of WKB data for the whole
 raster?
 > >
 > > Convert the raster with out-db bands to in-db (this functionality does
 not exist) and then call ST_AsBinary()?  That would abide by the WKB
 format...
 >
 >
 > I'm sorry, but IMHO you simply don't understand the purpose of this
 format.
 > The flag if data is stored in-database or out-database is for sole use
 by the raster implementation in PostGIS. It is for PostGIS to be able to
 locate physical storage, not for client (user of public SQL API). It is
 not even of interested of any client. Fullstop.
 >
 >

 I would consider the first sentence of the RFC describing WKB as explicit
 as can be.

 {{{
 The WKB format for RASTER is meant for transport.
 }}}

 If the WKB is kept the same, then what should the output from ST_Binary
 be?  Another format?  If so, please define that format.

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