[OSGeo-Discuss] Image Handling in RDBMS
Lucena, Ivan
ivan.lucena at pmldnet.com
Sat Feb 23 08:35:13 PST 2008
Dear Gilberto,
Unfortunately I could not follow the discussion since my last reply to
Bruce. I spent more time on air than on land in the last three days.
I believe that your message is a reply to Paul Ramsey message:
http://lists.osgeo.org/pipermail/discuss/2008-February/003202.html. Am I
correct?
What I would like to reply to both is that there is a new open source
initiative on
http://trac.osgeo.org/*gdal*/browser/trunk/gdal/frmts/*terralib*, a GDAL
driver for Terralib *raster*. It is in a very preliminary stage. So far
it only returns gdalinfo queries but it will be available for all gdal
tools and API soon.
I hope that it will help to dismistify the raster-on-db issue at least a
little bit.
Best regards,
Ivan Lucena
Gilberto Camara wrote:
> Dear OSGEO
>
> I also beg to differ with Paul about the number of cases where image data handling in RDBMS is useful or necessary.
>
> In corporate applications where vectors and raster live together, and data processing and editing operations are used, handling different types of data together in a database is convenient. Control is more important than performance.
>
> Our TerraAmazon system (presented in the latest FOSS4G conference) does this, and we handle large files without problems.
>
> For one-way image servers, on a write once, read mostly basis, then the case for handling raster data inside the DBMS is less clear. Since the output is an image delivered to the user, either as a file or as a visualization, DBMS features such as concurrency control and long transactions are not needed. Performance is more important than control in this case.
>
> Best regards,
> Gilberto
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/discuss
More information about the Discuss
mailing list