[gdal-dev] Gdaladdo feels slow with Rasterlite

Even Rouault even.rouault at mines-paris.org
Thu Jul 5 11:07:54 PDT 2012

> One issue there is still.  My original was a highly compressed (deflate)
> tiff with a file size of 550 MB.  Initial transform into Rasterlite with
> png tiles yielded a 1.2 GB Rasterlite db. Condiderably bigger but still
> understandable.  However, gdaladdo has no option to compress internal
> overviews which make most sense with Rasterlite. 

Good point. Support for specifying options was actually missing. Added in 
trunk in r24660.

See below diff for the syntax :

Index: frmts/rasterlite/frmt_rasterlite.html
--- frmts/rasterlite/frmt_rasterlite.html	(révision 24659)
+++ frmts/rasterlite/frmt_rasterlite.html	(copie de travail)
@@ -76,6 +76,10 @@
 <p>If no internal overview is detected, the driver will try using external 
overviews (.ovr files).</p>
+<p>Starting with GDAL 2.0, options can be used for internal overviews 
building. They can be specified with the
+RASTERLITE_OVR_OPTIONS configuration option, as a comma separated list of the 
above creation options. See below
@@ -172,6 +176,12 @@
+<li>Creating internal overviews with options (GDAL 2.0 or later):
+$ gdaladdo RASTERLITE:my_db.sqlite,table=source 2 4 8 16 --config 

More information about the gdal-dev mailing list