[gdal-dev] File Size Output is wrong --
Clive Swan
cliveswan at gmail.com
Mon Dec 12 13:45:20 PST 2022
Files: /data/coastal-undefended-rcp26-2020.vrt
/vsis3/summer-outputs/3_data_ready_for_spectra/coastal-undefended-rcp26-2020.tif
/vsis3/summer-outputs/5_UK_prod_rasters/coastal-undefended-rcp26-2020.tif
Size is 450000, 225000
Coordinate System is:
GEOGCRS["WGS 84",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,
LENGTHUNIT["metre",1]]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433]],
CS[ellipsoidal,2],
AXIS["geodetic latitude (Lat)",north,
ORDER[1],
ANGLEUNIT["degree",0.0174532925199433]],
AXIS["geodetic longitude (Lon)",east,
ORDER[2],
ANGLEUNIT["degree",0.0174532925199433]],
ID["EPSG",4326]]
Data axis to CRS axis mapping: 2,1
Origin = (-180.000000000000000,90.000000000000000)
Pixel Size = (0.000800000000000,-0.000800000000000)
Corner Coordinates:
Upper Left (-180.0000000, 90.0000000) (180d 0' 0.00"W, 90d 0' 0.00"N)
Lower Left (-180.0000000, -90.0000000) (180d 0' 0.00"W, 90d 0' 0.00"S)
Upper Right ( 180.0000000, 90.0000000) (180d 0' 0.00"E, 90d 0' 0.00"N)
Lower Right ( 180.0000000, -90.0000000) (180d 0' 0.00"E, 90d 0' 0.00"S)
Center ( 0.0000000, 0.0000000) ( 0d 0' 0.01"E, 0d 0' 0.01"N)
Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=-9999
Band 2 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 3 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 4 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 5 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 6 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 7 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 8 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
Band 9 Block=128x128 Type=Float32, ColorInterp=Undefined
NoData Value=-9999
On Mon, 12 Dec 2022 at 17:39, Javier Jimenez Shaw <j1 at jimenezshaw.com>
wrote:
> 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 <cliveswan at gmail.com> 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
>> gdal-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>
--
Regards,
Clive Swan
--
M: +44 7766 452665
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20221212/3d26d4a6/attachment-0001.htm>
More information about the gdal-dev
mailing list