[gdal-dev] -srcnodata in gdalwarp and gdalbuildvrt

I have a question that is probably more "user" than "developer". Is there different place that I should post my question? I don't think that I understand -srcnodata. I assume that -srcnodata "0 0 0" on a 3 band image means that all 3 bands have to be 0 to be "no data" but I think what I'm seeing

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

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

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] GDAL can't open MBTiles sample from the MapBox site

Hi Even, Thanks, after updating my GDAL to a more recent 2.3.0dev version ogrinfo indeed shows that information. -Jukka- Lähettäjä: Even Rouault Lähetetty: 28. maaliskuuta 2018 17:47 Vastaanottaja: gdal-dev@lists.osgeo.org

Re: [gdal-dev] GDAL can't open MBTiles sample from the MapBox site

On mercredi 28 mars 2018 14:28:14 CEST Rahkonen Jukka (MML) wrote: > Hi, > On page https://www.mapbox.com/help/define-mbtiles/ there is a link into > https://www.mapbox.com/help/data/trails.mbtiles > > My GDAL 2.3.0dev does list MBTiles as a supported format but it can't still > open this

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

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-dev] GDAL can't open MBTiles sample from the MapBox site

Hi, On page https://www.mapbox.com/help/define-mbtiles/ there is a link into https://www.mapbox.com/help/data/trails.mbtiles My GDAL 2.3.0dev does list MBTiles as a supported format but it can't still open this database gdalinfo trails.mbtiles ERROR 4: `trails.mbtiles' not recognized as a

Re: [gdal-dev] Extension based file identification in drivers

On mercredi 28 mars 2018 15:05:34 CEST Andrew C Aitchison wrote: > On Tue, 27 Mar 2018, Even Rouault wrote: > > The identification logic of drivers is supposed to operate fast > > > > (extension based, or on the content of the first kilobyte of the header), > > If I understand correctly Frank

[gdal-dev] Extension based file identification in drivers

On Tue, 27 Mar 2018, Even Rouault wrote: The identification logic of drivers is supposed to operate fast (extension based, or on the content of the first kilobyte of the header), If I understand correctly Frank Warmerdam did not favour extension based file identification:

Re: [gdal-dev] gdal_merge.py

On lundi 12 mars 2018 05:55:10 CEST Ian Reese wrote: > No matter which variation of merge I run, those regions that once contained > 'nodata' or '-' are converted to '0' and the nodata value is not > retained after the merge. When I load the test_merge_wnodata.tif into > QGIS, those regions

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

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