[postgis-tickets] [PostGIS] #2069: [raster] ST_Tile() should no longer pad tiles with NODATA

[PostGIS]

#2069: [raster] ST_Tile() should no longer pad tiles with NODATA
-------------------------+--------------------------------------------------
 Reporter:  pracine      |       Owner:  dustymugs    
     Type:  enhancement  |      Status:  assigned     
 Priority:  high         |   Milestone:  PostGIS 2.1.0
Component:  raster       |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by dustymugs):

 From the description:

 {{{
  So we can tile rasters which width and height do not have a common
 divisor without increasing the size of the coverage. Ex. width=1591 and
 height=1446
 }}}

 I don't see the problem with doing away with padding in the first place.
 Why take extra space and fill in NODATA (or min possible value) when the
 spec has an exemption in it?  Based upon your specs...

 {{{
 This constraint ensures that all tile are of the same size and hence, do
 not overlap and do not leave gaps in the coverage. The exceptions for
 right-most and bottom tiles are to ensure that the coverage conserve the
 same extent as the original loaded raster. Reading applications have to
 check for the width and height of rasters (or tiles) before blindly copy
 their data into buffers having their sizes determined by blocksize_x and
 blocksize_y.
 }}}

 It doesn't look it it matters to be padded in the database anymore.  It's
 the client's responsibility to handle the possibility that edge tiles can
 have smaller dimensions.

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