[postgis-devel] [PostGIS] #232: Implementation of ST_AsBinary for RASTER type

[PostGIS]

#232: Implementation of ST_AsBinary for RASTER type
--------------------------+-------------------------------------------------
  Reporter:  mloskot      |       Owner:  mloskot          
      Type:  enhancement  |      Status:  assigned         
  Priority:  high         |   Milestone:                   
 Component:  wktraster    |     Version:  trunk            
Resolution:               |    Keywords:  st_asbinary,bytea
--------------------------+-------------------------------------------------
Old description:

> This is just a record of the plan I've made to start implementing
> ST_AsBinary function for [wiki:WKTRaster WKT Raster]. The function is
> listed in the [wiki:WKTRaster/PlanningAndFunding big plan].
>
> The first version of [ST_AsBinary I'm going to implement will do nearly
> the same what ST_byte function does. It's prototype is:
>
> {{{
> bytea ST_AsBinary(raster r1);
> }}}
>
> At the moment, I don't aim to implement compression support, but later it
> can be extended to provide it:
> {{{
> bytea ST_AsBinary(raster r1, text compression);
> }}}
>
> I haven't planned to handle endianness as PostGIS'
> [http://postgis.refractions.net/documentation/manual-1.4/ST_AsBinary.html
> ST_AsBinary] does. So, it is expected that WKB is returned with
> endianness native to the machine running the PostgreSQL database - it can
> vary. Feel free to share your suggestions of solutions fot this.

New description:

 This is just a record of the plan I've made to start implementing
 ST_AsBinary function for [wiki:WKTRaster WKT Raster]. The function is
 listed in the [wiki:WKTRaster/PlanningAndFunding big plan].

 The first version of [ST_AsBinary I'm going to implement will do nearly
 the same what ST_byte function does. It's prototype is:

 {{{
 bytea ST_AsBinary(raster r1);
 }}}

 At the moment, I don't aim to implement compression support, but later it
 can be extended to provide it:
 {{{
 bytea ST_AsBinary(raster r1, text compression);
 }}}

 I haven't planned to handle endianness as PostGIS'
 [http://postgis.refractions.net/documentation/manual-1.4/ST_AsBinary.html
 ST_AsBinary] does. So, it is expected that WKB is returned with
 [http://en.wikipedia.org/wiki/Endianness endianness] native to the machine
 running the PostgreSQL database - it can vary (i.e. Intel returns NDR,
 PowerPC returns XDR).
 Feel free to share your suggestions of solutions fot this.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/232#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS