[raster] Width and Height column of raster_columns view may need changing
|Reported by:||Bborie Park||Owned by:||Bborie Park|
With tiles no longer being padded, right and bottom edge tiles of a coverage may be of different width and/or height. The constraints (blocksize x and blocksize y) themselves need to be changed to constrain as a set (width AND height = X AND Y).
Constraint testing would be something like the following, just in a function:
SELECT dim FROM ( SELECT ROW(4,4) AS dim UNION ALL SELECT ROW(2,4) AS dim UNION ALL SELECT ROW(4,2) AS dim UNION ALL SELECT ROW(2,2) AS dim ) foo INTERSECT SELECT ROW(2,3) AS dim
So what should be the value(s) in the width/height columns of raster_columns? The "desired" tile size (the one specified with -t in raster2psql or tilewidth/tileheight in ST_Tile()), which would be a singular value. Or should the columns be an array of the permitted widths or heights? Or is having two seperate columns no longer appropriate and there should just be one column (say "tile_size") with an array of sets (each set indicating a width/height).