Le mardi 21 août 2012 09:53:50, Rahkonen Jukka a écrit :
> Even Rouault wrote:
> > Selon Rahkonen Jukka :
> > > Even Rouault wrote:
> > > >> Better after doing these. 4 minutes and 10 seconds for the biggest
> > > >> layer, record before this was 6 minutes. Big enough difference for
> > > >> being
> Yes, that makes gdalinfo fast. With my biggest layer the time went down
> from 3 minutes to 3 seconds. However, my gdal_translate test fails. It
> used to take three minutes before the zero appeared into the progress bar
> but after that translation itself took only few seconds. After updating
Even Rouault wrote:
> Jukka,
>>
>> Is gdalinfo perhaps walking through every single tile in the
>> rasterlite table for gathering the image layer info? Could
>> there be any other way to do it in more effective way on the
>> GDAL side?
> The Rasterlite driver needs to fetch the extent of the "XX
Jukka,
>
> Is gdalinfo perhaps walking through every single tile in the
> rasterlite table for gathering the image layer info? Could
> there be any other way to do it in more effective way on the
> GDAL side?
The Rasterlite driver needs to fetch the extent of the "_metadata" layers
to estab
Hi,
I converted 153600 x 249600 pixels of rasterdata into a
Rasterlite table. After creating overviews the result
behaves well in Quantum GIS once the table is opened.
Unfortunatly opening the table with QGis installed on a
mini PC takes ages.
I do not know what QGis is really doing but I guessed
