[postgis-devel] [PostGIS] #2122: [raster] Real extent feature lost after metadata as views

Sandro Santilli strk at keybit.net
Fri Nov 30 07:53:18 PST 2012

On Fri, Nov 30, 2012 at 03:46:30PM +0000, Mateusz Loskot wrote:

> Imagine, PostGIS geometry is 3D only storage. User loads 2D geometry, the loader
> adds extra data, the Z. Then, SQL queries return 3D byte stream
> and there is no functionality that enables 2D only queries.
> That's close analogy I could think of ATM.
> The point is, raster is not (always) 1:1 mapping of raster in file
> or 1:1 equivalent to raster definition by GDAL.
> The loader may change physical raster data if requested parameters
> of storage require such change. That is an important flexibility of PostGIS.

Yep, fully understood. The loader should do some book-keeping somewhere.

I think even outside of the db would be `nough  (returning the padding
numbers in a format to be used as input for the dumper, to cut that much).
But as you say it'd be a regression to move the feature outside so better
done within the db. 


More information about the postgis-devel mailing list