Re: [gdal-dev] gdal_merge on large files

2010-01-28 Thread Even Rouault
Peter, In fact, tiling the input or output won't help for the issue. The main limitation of gdal_merge.py is that it ingests each input file in one gulp. So the limit is on the dimensions of the input files. The buffer must hold in RAM and be smaller than 2GB (the maximum size of a 32bit intege

Re: [gdal-dev] gdal_merge on large files

2010-01-28 Thread Chaitanya kumar CH
Peder, The problem here is the lack of or very large tiles/blocks in the image. BandReadAsArray() was asked to read a whole 27989 x 62863 block into memory. That's 1.76 Giga pixels. Too big. Greg Coats' tiff file had tiles of 512 x 512 size. Creating tiled tiffs is a good place to start. Use the

Re: [gdal-dev] gdal_merge on large files

2010-01-28 Thread Greg Coats
On Jan 28, 2010, at 3:13 AM, Peder Axensten wrote: > What is the raster size restrictions in gdal/numpy? I have successfully used gdal_merge.py to create a 142 GB .tif file, on a computer with only 3 GB RAM, under Apple Mac OS X 10.6. Greg tiffinfo dcua0002.tif Image Width: 26 Image Lengt

[gdal-dev] gdal_merge on large files

2010-01-28 Thread Peder Axensten
I want to run gdal_merge (and another program I made, based on gdal_merge) on rather large files -- typically 3-7 Gbytes. Not surprisingly I run into problems. I'm not very experienced in Python, but am I right to assume that the error below probably is an indication on a size problem? What is t