[postgis-devel] [PostGIS] #2122: [raster] Real extent feature lost after metadata as views
strk at keybit.net
Fri Nov 30 07:48:18 PST 2012
On Fri, Nov 30, 2012 at 03:39:43PM +0000, Mateusz Loskot wrote:
> On 30 November 2012 15:35, Sandro Santilli <strk at keybit.net> wrote:
> > On Fri, Nov 30, 2012 at 02:51:26PM +0000, Mateusz Loskot wrote:
> >> On 30 November 2012 14:22, Sandro Santilli <strk at keybit.net> wrote:
> >> >
> >> > All of this seems to me as something that should be dealt with
> >> > in upper levels, not value level.
> >> What is the upper level?
> > Whoever is having problems with the extent now being larger than expected.
> > Is that the issue, right ?
> The problem is a feature has changed, implicitly, and is causing issues.
> The call is to fix the feature to its previous behaviour.
> > I see the extent in raster_columns is returned by:
> > _raster_constraint_info_extent(n.nspname, c.relname, a.attname) AS extent
> > Could that function figure if it's a "regular blocking" table by looking
> > at other constraints and encode padding in those constraints ?
> Perhaps, but how to distinguish if the padding has been added at loading
> or it is not really a padding but NODATA strips present in the source raster.
Couldn't (or doesn't) a constraint contain the original extent ?
The same information that you would have put into the raster_column field.
I hadn't look at those _raster_constraint_info_xxxy functions at all so don't
really know what constraints are currenty present
More information about the postgis-devel