Re: [gdal-dev] FW: gdal_merge.py

2018-03-28 Thread Even Rouault
On mercredi 28 mars 2018 17:58:37 CEST Raphael Das Gupta wrote: > On 28.03.2018 16:31, Marcos Dione wrote: > > in my opinion, gdal_merge should be used only if the merged version > > > > will be used for more things or if you're going to use it with something > > that doesn't know how to read

Re: [gdal-dev] FW: gdal_merge.py

2018-03-28 Thread Raphael Das Gupta
On 28.03.2018 16:31, Marcos Dione wrote: > in my opinion, gdal_merge should be used only if the merged version > will be used for more things or if you're going to use it with something > that doesn't know how to read the .vrt files (i.e., is not using gdal). Even then it seems to be faster to

Re: [gdal-dev] FW: gdal_merge.py

2018-03-28 Thread Marcos Dione
On Wed, Mar 28, 2018 at 02:28:57PM +0200, Raphael Das Gupta wrote: > On 27.03.2018 22:56, Ian Reese wrote: > > Maybe this is a bug or am I using gdal_merge.py improperly. > I've recently become unsure whether (and when) gdal_merge.py should be > used at all, or whether gdalbuildvrt followed by gdal

Re: [gdal-dev] FW: gdal_merge.py

2018-03-28 Thread Raphael Das Gupta
Hi Ian, heya GDALers On 27.03.2018 22:56, Ian Reese wrote: > Maybe this is a bug or am I using gdal_merge.py improperly. I've recently become unsure whether (and when) gdal_merge.py should be used at all, or whether gdalbuildvrt followed by gdaltranslate or gdalwarp is always preferable. (Also ask

[gdal-dev] FW: gdal_merge.py

2018-03-27 Thread Ian Reese
HI Gdal, Just wanted to follow this up. Cheers, Ian From: Ian Reese Sent: Monday, 12 March 2018 6:55 p.m. To: gdal-dev@lists.osgeo.org Subject: gdal_merge.py Hi Gdal, I am having some issues with gdal_merge.py. When I merge two tifs together, the original nodata value is converted to 0, no