I think for gdal_translate I need both open and creation options (-oo and -co), right?
On Tue, 29 Jul 2025 at 18:30, Even Rouault <even.roua...@spatialys.com> wrote: > Javier, > > for gdal_translate to COG, both should be equivalent. > > for gdalwarp, -wo NUM_THREADS=ALL_CPUS -co NUM_THREADS=ALL_CPUS (ie > enabling multithreading for warping and GeoTIFF output) will be > equivalent to --config GDAL_NUM_THREADS=ALL_CPUS > > Note that you can also do gdalwarp directly to COG. This should do the > right things > > Even > > Le 29/07/2025 à 18:25, Javier Jimenez Shaw via gdal-dev a écrit : > > Hi > > > > I am running a gdalwarp from UTM xx to EPSG:3857 and later a > > gdal_translate to COG (the input is a normal GeoTIFF). Two steps. All > > inputs and outputs are TIFF. > > > > Is there any difference between using the config variable > > GDAL_NUM_THREADS=ALL_CPUS > > than using the creation option for the TIFFs > > NUM_THREADS=ALL_CPUS > > > > What is the fastest combination? > > > > Thanks. > > > > > > _______________________________________________ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/gdal-dev > > -- > http://www.spatialys.com > My software is free, but my time generally not. > >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
