Hi Simone, due to performance reasons, the utility has now the possibility to produce a different output directory structure.
The details are here
http://trac.osgeo.org/gdal/ticket/3879
The actual source is here
https://svn.osgeo.org/gdal/trunk/gdal/swig/python/scripts/gdal_retile.py
The additional command line param will be available in GDAL 1.8.0 which will be released soon.
I will adapt the import utility for imagemoasicJDBC and I can remember you are also supporting the output structure of gdal_retile.py. Do you want to adapt your logic yourself or should I make a patch ?
Does it make sense to backport the modifications to 2.6.x ?
Cheers
Christian
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
On Sat, Dec 18, 2010 at 2:46 PM, <christian.mueller@anonymised.com> wrote:
Hi Simone, due to performance reasons, the utility has now the
possibility to produce a different output directory structure.
The details are here
http://trac.osgeo.org/gdal/ticket/3879
I may be wrong, but if each mosaic is contained in its own tree of folders
(0/1, 0/2, 0/3, ... 0/rows, 1/1, 1/1, .... 1/rows, ...) the current mosaic
code (used to read each of the pyramid levels) should be able to work
unaltered.
As far as I know, in fact, the mosaic code builds a mosaic from all the
tiles that it finds in the directory tree it's pointed at, that is, it behaves
ricursively by default
I may be wrong though
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------