gdalinfo of the three files (two inputs and one output) may help to understand better the conditions. One option is that file A is not compressed, while the output is LZW. .___ ._ ..._ .. . ._. .___ .. __ . _. . __.. ... .... ._ .__ Entre dos pensamientos racionales hay infinitos pensamientos irracionales.
On Mon, 12 Dec 2022 at 17:47, Clive Swan <[email protected]> wrote: > Greetings, > > I am writing the output on the local AWS Instance to avoid write > permissions error, then copying to a Bucket. > I get an error message if I leave out --config GDAL_SWATH_SIZE 1000000 > > I want to merge File A into File B, updating the 6GB file. The output is > 622MB NOT 6GB?? > (A) /vsis3/summer/1/coastal-2020.tif = 6GB > (B) /vsis3/summer/2/coastal-2020.tif = 622MB > > Is this wrong?? > (A) (B) > gdalbuildvrt -o /data/coastal-2020.vrt /vsis3/summer/1/coastal-2020.tif / > vsis3/summer/2/coastal-2020.tif > > The output in /data/coastal-2020.tif should be 6GB > gdal_translate /data/coastal-2020.vrt /data/coastal-2020.tif -co > BIGTIFF=YES -co COMPRESS=LZW - -co NUM_THREADS=ALL_CPUS --config > CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE YES --config GDAL_SWATH_SIZE > 1000000 > ##--config AWS_ACCESS_KEY_ID set in ./config > ##--config AWS_SECRET_ACCESS_KEY set in ./config > > -- > > Regards, > > > Clive Swan > > -- > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
