[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 12:34:20 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 mloskot):
Replying to [comment:31 pracine]:
> Replying to [comment:30 mloskot]:
> > Indeed, ST_SameAlignment can not be used as replacement for the
regular_blocking flag.
>
> Agreed. But you don't need regular_blocking anymore right?
This constraint is supposed to serve certain use-cases where a table
stores regular grid of tiles, so a client application can recognize this
kind of configuration quickly and easily, and treat it in such specific
case. The tiles storage/cache is one of important use cases for PostGIS
Raster. Please, with all my respect, don't be scientific-ignorant here
guys and don't make PostGIS Raster just another GRASS, please.
If you decide to get rid of this flag, then the only way to determine if a
table is tiles storage or not is to perform slow (!) query.
So, for the sake of best possible performance, I do use it myself.
Per analogia, where vector folks here store SRID information?
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1319#comment:37>
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