Re: [gdal-dev] merge with gdalwrap

2009-07-30 Thread Frank Warmerdam
steve.tout...@inspq.qc.ca wrote: gdalwarp -srcnodata -3.4028234663852886e+38 \ EstRN.img EstSh.img icu.tif I thought I must launch gdalwrap once for each file. Didn't know I could specify several input files Steve, This is a relatively new feature - likely new in 1.6.0. I think I

Re: [gdal-dev] merge with gdalwrap

2009-07-30 Thread Steve . Toutant
qc.ca Frank Warmerdam 30/07/2009 02:19 PM A steve.tout...@inspq.qc.ca cc gdal-dev@lists.osgeo.org Objet Re: [gdal-dev] merge with gdalwrap steve.tout...@inspq.qc.ca wrote: > > Hi, > I tried gdal_merge.py but I got a memory Error because I use the -n > nodata value option

Re: [gdal-dev] merge with gdalwrap

2009-07-30 Thread Frank Warmerdam
steve.tout...@inspq.qc.ca wrote: Hi, I tried gdal_merge.py but I got a memory Error because I use the -n nodata value option. Several threads sugest that I must use gdalwrap instead. This behavior of gdal_merge.py is very important to me in this particular case "In areas of overlap, the last

[gdal-dev] merge with gdalwrap

2009-07-30 Thread Steve . Toutant
Hi, I tried gdal_merge.py but I got a memory Error because I use the -n nodata value option. Several threads sugest that I must use gdalwrap instead. This behavior of gdal_merge.py is very important to me in this particular case "In areas of overlap, the last image will be copied over earlier one