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

2022-10-12 Thread 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/sta

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

2022-10-12 Thread thomas bonfort
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 depe

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

2022-10-12 Thread Andrea Giudiceandrea via gdal-dev
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 le

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

2022-10-12 Thread 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 su

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

2022-10-12 Thread Richard Duivenvoorde
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) woul

Re: [gdal-dev] four threads are huh, five are buh? Regressions w/ GDAL 3.5.2/PROJ_9.1.0

2022-10-12 Thread Even Rouault
Le 12/10/2022 à 08:59, Christian Brock a écrit : Hi Even, Thanks for the fast answer. We do not share any gdal datasets, BUT we share all spatial references and all coordinate transformations between threads. It used to work in the past, hmm ... I assume this is a problem? yes, this was ne

Re: [gdal-dev] four threads are huh, five are buh? Regressions w/ GDAL 3.5.2/PROJ_9.1.0

2022-10-12 Thread Christian Brock via gdal-dev
Hi Even, As a PS: We also open the same file using gdal.Open() or gdal.OpenShared() again and again ... We tried GeoTiff, external and internal and also HFA -- all show the issue Thx --Chr. -Original Message- From: Christian Brock Hi Even, Thanks for the fast answer. We do not shar

Re: [gdal-dev] four threads are huh, five are buh? Regressions w/ GDAL 3.5.2/PROJ_9.1.0

2022-10-12 Thread Christian Brock via gdal-dev
Hi Even, Thanks for the fast answer. We do not share any gdal datasets, BUT we share all spatial references and all coordinate transformations between threads. It used to work in the past, hmm ... I assume this is a problem? Cheers --Chr. -Original Message- From: Even Rouault Chris