GDAL/Georaster not support import the pyramid data!

[bicealyh]

Hi everyone, If the image have pyramid data, using the gdal_translate just import the original data not include the pyramid data. After that, it will use more time to build the pyramid through ORACLE's SDO_GEOR.generatePyramid way. For example, I just import 4.5G image into Oracle Georaster,it will use half an hour, and build pyramid will use twenty minutes. So that it is very important to make it! The sooner the better, I am waiting to use!

[warmerdam]

Hi,

Are you suggesting that it would be better to import pyramids from the source image if the they are available, rather than building them within oracle?

Traditionally GDAL has not bothered to copy pyramids with images under the assumption that it is not significantly faster or more useful than just building them from scratch in the target environment. I'm not sure why that would be less true of the oracle georaster environment.

Ivan - any thoughts on this?

[ilucena]

If I understand the number correctly. It takes 10 minutes to load 4.5G of raster data to Oracle GeoRaster using GDAL and it would take another 20 minutes just to create Pyramids. That discussion is also on Oracle's OTN:

 http://forums.oracle.com/forums/thread.jspa?threadID=984916&tstart=0

The point is not if we should let the driver to copy Overviews to Pyramids at CreateCopy?() the point is that the IBuildOverviews() would work much faster if it was generating and updating Pyramids by itself instead of issuing a Pl/SQL statement to do that:

http://trac.osgeo.org/gdal/browser/trunk/gdal/frmts/georaster/georaster_wrapper.cpp#L2231

I agree that this would be a important enhancement.