Changes between Initial Version and Version 3 of Ticket #232
- Timestamp:
- 08/05/09 07:50:42 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #232
- Property Owner changed from to
- Property Status new → assigned
- Property Keywords bytea added
-
Ticket #232 – Description
initial v3 1 1 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]. 2 2 3 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:3 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: 4 4 5 5 {{{ … … 11 11 bytea ST_AsBinary(raster r1, text compression); 12 12 }}} 13 14 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.