From: <chr...@nv...> - 2011-11-22 11:08:32
|
Short answer, geotools does NOT use the raster_column table. Cheers Christian Zitat von Pierre Racine <Pie...@sb...>: > (Forgot to CC some people. Please reply to all those in this mail... sorry) > > Hi all, > > If I'm writing to you it is because you have been implementing some > piece of code querying PostGIS raster (GDAL driver, Geotools, QGIS > plugin, gvSIG plugin, etc...).... > > We are planning to simplify the raster_column table to its most > simple expression in order to make it a view like PostGIS folks are > making a view of geometry_column. > > Before doing so we would like to know two things from you: > > 1) Is your application querying/relying on some columns of the > raster_column table? > > Considering the facts that: > > -Any internal SQL query might break the integrity of this table, > -Any append operation performed with the -a option of > raster2pgsql.py might also break the integrity of this table, -Any > import of a series of raster using the wildcard (*) with > raster2pgsql.py might also break the integrity of this table, -There > are other ways to get the information provided by raster_column, > > 2) Why do you need to query this table column? What are you doing > with this information? > > A raster_column view would not provide all the information provided > by the current raster_column table but by making it a view we can > insure that whatever is provided in the view is consistent with what > is actually in the raster tables by enforcing of table constraints > that force maintained consistency. We will work to provide you with > other means to get this information if they don't already exist. > > Please at least answer the two questions before starting a long discussion. > > Thanks, > > Pierre Racine > Kind of manager for the PostGIS Raster project. > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |