[postgis-devel] [PostGIS] #1319: [raster] Make raster_columns a constraint-based view, replace AddRasterColumn with ApplyRasterConstraints and expand # of constraints on raster columns
PostGIS
trac at osgeo.org
Wed Nov 30 09:52:36 PST 2011
#1319: [raster] Make raster_columns a constraint-based view, replace
AddRasterColumn with ApplyRasterConstraints and expand # of constraints on
raster columns
----------------------------+-----------------------------------------------
Reporter: robe | Owner: dustymugs
Type: task | Status: assigned
Priority: critical | Milestone: PostGIS 2.0.0
Component: postgis raster | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Comment(by dustymugs):
> Agreed. But you don't need regular_blocking anymore right? We are not
planning to set this constraint, right Bborie?
I don't really see an overt need for regular_blocking unless you're
interested in the "perfect" condition of a table with no overlaps and no
gaps. I know all my raster tables would fail this constraint as I put a
year's worth or daily rasters into one table so for the whole table, there
definitely would be overlap.
Having same alignment be a constraint is desirable because users don't
need to be concerned of resampling a raster before conducting a 2-raster
operation.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1319#comment:32>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list