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

 Replying to [comment:8 dustymugs]:
 > Replying to [comment:7 mloskot]:
 > > Replying to [comment:3 dustymugs]:
 > > > From my initial read of
 [http://svn.osgeo.org/postgis/spike/wktraster/doc/RFC2-WellKnownBinaryFormat
 RFC-2], it looks like the WKB output is following spec
 > >
 > > Please, let me repeat what has been also confirmed with Sandro:
 > >
 > > '' That canonical representation of WKB doesn't necessarily have to
 match ST_AsBinary output.''
 > >
 > > It's also important to keep in mind, that this RFC marks very early
 stage of low-level design and does not discuss or even consider public
 APIs that followed.
 >
 > So, the WKB spec is open to change?


 I'm not saying any such thing, I'm saying that WKB storage is one thing,
 public API is the other.

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