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

Sandro Santilli strk at keybit.net
Fri Nov 30 10:54:30 PST 2012

On Fri, Nov 30, 2012 at 10:35:52AM -0800, dustymugs wrote:
> On 11/30/2012 10:24 AM, Mateusz Loskot wrote:
> > On 30 November 2012 18:08, dustymugs <dustymugs at gmail.com> wrote:

> >> So are we all in agreement
> >> that the correct solution is to add a new constraint "data_extent" which
> >> will indicate the table's maximum extent in which data is present?
> > 
> > Either to add new constraint, or to correct what the current extent represents.
> > Juggling two extents may be confusing (two extents?). What you think?
> I'm fine with two extents as the extents represent different things.
> The extent currently in place is the maximum spatial extent of the
> table.  The extent being added is the maximum data extent (represented
> spatially).

I also think two extents are confusing.
Especially when only one would be in raster_columns.
Do we really need that padding ?


More information about the postgis-devel mailing list