[gdal-dev] not enough disk space for gdal_merge even though I have ~1TB free

Ujaval Gandhi ujaval at spatialthoughts.com
Wed Nov 9 23:20:54 PST 2022


Your inputs must be compressed and you are trying to write uncompressed output.
Add -co COMPRESS=DEFLATE and it should work. Also I find that instead of using
gdal_merge.py for merging large files, creating a virtual raster first and then
using gdal_translate to convert to geotiff is much more efficient. See the
workflow at https://courses.spatialthoughts.com/gdal-tools.html#merging-tiles
[https://courses.spatialthoughts.com/gdal-tools.html#merging-tiles]

---
Ujaval Gandhi
Spatial Thoughts
www.spatialthoughts.com [http://www.spatialthoughts.com]




[data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=3D]
On Thu, Nov 10, 2022 at 3:50 AM Terra Frost <terrafrost at gmail.com> wrote:

> When I do "gdal_merge -o result.tif bottom.tif top.tif" I get the following
> error:
> 
> 
> > ERROR 3: result.tif: Free disk space available is 1011663560704 bytes,
> > whereas 61588097799713184 are at least necessary. You can disable this check
> > by defining the CHECK_DISK_FREE_SPACE configuration option to FALSE.
> > Creation failed, terminating gdal_merge.
> 
> 
> 
> I don't understand. The two TIFs I'm trying to merge are 1.27GB and 64MB and
> it's saying 61588097799713184 bytes are needed? That's 61.58 PB. Why would
> gdal_merge think it'd need 61.58 PB?
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org [gdal-dev at lists.osgeo.org]
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
> [https://lists.osgeo.org/mailman/listinfo/gdal-dev]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20221110/03446702/attachment.htm>


More information about the gdal-dev mailing list