Hi Mike, Bruce,
We went to that discussion a couple of year ago, and by that time there was some strong opinion
against storing raster data on databases, but it look like time has changed things a little bit. Am
I right to say that? I can see basically three reasons for that.
1. Data volume.
Raster images are getting more and more accessible and whoever deals with big volume of those are
starting to feel the pain of managing it on files. I bet that people have started to think about why
spending so much money buying and maintaining huge Network Attached Storage (NAS) and end up making
a person do the job of a database server. They must realize that shared folders accessible by end
users is a problem not a solution. Yes, the systematical and disciplinary use of file based storage
is possible too, adding to that some sort of raster catalog, but adding to that also the trouble of
managing permission access on the NAS, backup procedures, temporary files management, and the result
is a full time position or two.
The myth says: the is always a overhead to access your raster data from a database in comparison to
accessing it directly from the file system. If you are talking about a single computer that might
be the case since fopen(), read(), write() doesn't need to make connections, check permission,
parse SQL statement to finally figure out where to read BLOBs with the same C functions. But as the
complexity of your storage grows the file based options will start to experience overhead too and
there will be not RDBMS server to do connection pooling or caching for you. Again, you can go to the
whole trouble of managing overviews and tile cache yourself. That means overhead for a file based
raster data server and more cost of maintaining it. Are we tied?
Satellite companies, data provider, government agency and consulting firms are giving good testimony
of their use of raster on database, so it might be true for the FOSS options too. The two examples
provided by Bruce are pretty good. Rasdaman only works with PostgreSQL while Terralib works with
directly with PostgreSQL, MySQL and commercial RDBMS systems. Both have some big projects to
showcase their muscles.
Please keep us posted.
Bruce Bannerman wrote:
A product for managing (muti-dimensional) raster data within a database that I've been monitoring since around 2002 has just been released under GPL.
They have also applied for OSGeo Incubation.
This product, Rasdaman, can be used with Postgres as its data store.
Rasdaman has its lineage going back to around 1995 (I think). They are claiming
the French government as a client using the product to manage TB image mosaics.
I understand that there is a sister product that will soon be merged in with
Rasdaman that offers good OGC support (WCS 1.1 and 2.0, WMS and WCPS).
We intend investigating this product as a potential tool for managing grid, model and multi/hyperspectral remotely sensed data relating to the Climate domain.
If you look at the product, let me know. I'll be happy to share experiences.
See  for Rasdaman product information and  for example implementations.
Another option is the Brazillian Terralib Project .
They have developed an integrated suite of server and framework tools for developing integrated applications based around the use of imagery and the management of imagery within a database (Postgres from memory).
I'm not doing them justice with this brief description. They have done some
very impressive work. I'd recommend Gilberto Camara's intro paper at  for an
overview of Terralib.
From: discuss-boun...@lists.osgeo.org [discuss-boun...@lists.osgeo.org] On
Behalf Of Mike Toews [mwto...@gmail.com]
Sent: Tuesday, 4 May 2010 6:11 AM
Subject: [OSGeo-Discuss] Raster catalog ideas
I'm wondering what existing open source options are available to store rasters
For example, I have several hundred air photos from northern Canada spanning from the
1940s to now. They have different projections (UTM zones), cell sizes, etc. This data
store needs to be accessed from both web and desktop GIS software, but needs to have a
definition query for the year attribute (so I can take all air photos from
1962, or between 1973 to 1978, or whatever is required).
Our (my company) present solution is to use ESRI's raster catalog on a
geodatabase. We've had a mixed range of problems on File/Personal/SDE
Geodatabases. We've experienced corruption on all levels of storage options, so
we keep our file path attributes to the original GeoTIFFs so the raster
catalogs can be restored, if