[gdal-dev] Does it hurt to *always* use BIGTIFF when using gdal_translate

[Even Rouault]

Richard,

BigTIFF doesn't have a formal status like classic TIFF, so its adoption 
might be lower by non-libtiff-4.0-or-later based software, in 
particularly outdated proprietary software.

BIGTIFF=IF_SAFER could be a reasonable compromise (BIGTIFF=IF_NEEDED is 
the default behaviour, but not super appropriate when compression is used)

Even

Le 12/10/2022 à 11:51, Richard Duivenvoorde a écrit :
> Hi Devs,
>
> In QGIS we have a GUI for gdal_translate, the "Georeferencer".
>
> It was reported that when Georeferencing huge Tiffs (user was talking 
> about 8GB), that QGIS ended up with a broken 3.99GB Tiff, see 
> https://github.com/qgis/QGIS/issues/47362
>
> One of the 'easy' solutions (on QGIS side) would be to *always* add 
> the BIGTIFF=yes option.
>
> Question to you: would that hurt anybody? Is creating a BIGTIFF maybe 
> not preferable because of technical or user limitations?
>
> Thanks for any pointers, or feel free to add it to the issue above.
>
> Regards,
>
> Richard Duivenvoorde
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.