Mateusz Loskot :: hacking on, working out, living up

PostGIS Raster regular blocking explained

15 Feb 2012 | mloskot

I have been involved in PostGIS Raster development for almost four years now, but my project punch card confirms irregular activity.

Regular blocking concept

Regular blocking - take 1

Regular blocking - take 2

Frank: I would like to encourage treating cases 1 and 2 as the same thing. It was never my intention that the regular blocking would require a complete set of tiles. Missing tiles would just be treated as the nodata value, or zero if there is no nodata value.

it would be foolish not to address it in some fashion.

http://lists.osgeo.org/pipermail/postgis-devel/2007-July/002652.html > Blocking storage techniques, pyramid structures and data compression > are the three key approach to improve the performance of PostGIS > PGRaster in data processing and visualization

The padding is a technique that was introduced to fulfil requirement of regular grid without gaps, teeth or any kind of irregularities.

At the moment, there is no way to determine, if padding is present and if it is, how much padding is present.

“The right most column, and bottom row of blocks may have portions that extend beyond the raster extent”

Real extent feature lost after metadata as views

[specw1]http://trac.osgeo.org/postgis/wiki/WKTRaster/SpecificationWorking01

Fork me on GitHub