#6353 closed defect (fixed)

gdaladdo suggests BIGTIFF instead of BIGTIFF_OVERVIEW when crashing due to size

Reported by: kthujvu Owned by: warmerdam
Priority: normal Milestone: 2.1.0
Component: default Version: 2.0.1
Severity: normal Keywords:


I just spent some hours waiting again and again for gdaladdo to crash with "ERROR 1: TIFFAppendToStrip:Maximum TIFF file size exceeded. Use BIGTIFF=YES creation option." where my attempts to create pyramids failed due to size.

My commandline was "gdaladdo -ro --config INTERLEAVE_OVERVIEW PIXEL --config COMPRESS_OVERVIEW JPEG somefile.vrt 2 4 8 16"

First I did as it said and added "--config BIGTIFF YES". That still crashed.

I then read http://www.gdal.org/gdaladdo.html and as it suggested I then used "--config BIGTIFF_OVERVIEW YES" instead. Crashed again.

I had to have BOTH "--config BIGTIFF YES" AND "--config BIGTIFF_OVERVIEW YES" for it to work.

Please make sure the suggestion in the crash is correct and maybe add a note to the documentation! I am also confused why the documentation says "The default value is IF_NEEDED." but I still had to explicitly enable it. :)

Using GDAL 2.0.1, released 2015/09/15 on Archlinux.

Change History (1)

comment:1 Changed 16 months ago by Even Rouault

Milestone: 2.1.0
Resolution: fixed
Status: newclosed

I can't see how "--config BIGTIFF YES" could have any effect, as it is not a recognized configuration option.

trunk r33379 "GTiff: use more appropriate error message when 4GB threshold is reached with external overviews, and try to make doc of BIGTIFF=IF_NEEDED/IF_SAFER clearer (#6353)"

Note: See TracTickets for help on using tickets.