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

[Kurt Schwehr]

I keep trying to find if anyone has examples for tools that still don't
understand bigtiff, but haven't found anything that has a release in the
last 5 years that can't handle BIGTIFF.  I can't remember where I've asked
before, but I'm asking again on twitter...

https://twitter.com/kurtschwehr/status/1580281226157445120

On Wed, Oct 12, 2022 at 12:17 PM thomas bonfort <thomas.bonfort at gmail.com>
wrote:

> this is one of the reasons we built https://github.com/airbusgeo/cogger
> (supposing you are creating a tiled tif): first create your tif with your
> usual gdal tooling , unconditionally setting bigtiff=yes, and then as a
> postprocessing step run cogger on the resulting file. You'll get a COG
> which depending on the final output size will be bigtiff if really needed
> or a standard tiff if not.
>
> regards,
> thomas
>
> Le mer. 12 oct. 2022, 13:59, Andrea Giudiceandrea via gdal-dev <
> gdal-dev at lists.osgeo.org> a écrit :
>
>> Il 12/10/2022 11:51, Richard Duivenvoorde ha scritto:
>> > One of the 'easy' solutions (on QGIS side) would be to *always* add
>> > the BIGTIFF=yes option.
>>
>> Hi all,
>> while there are also the IF_NEEDED and IF_SAFER values for the BIGTIFF
>> creation option, another possibility would be to have an option to let
>> GDAL to retry to create the raster file as a BIGTIFF if the the normal
>> TIFF creation fails or to let QGIS to inform the user if the normal TIFF
>> creation fails and then offer the possibility to retry using the
>> BIGTIFF=YES option.
>>
>> Regards.
>>
>> Andrea
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20221012/6f2b8d4c/attachment.htm>