Re: [gdal-dev] parsing of netcdf4 no-data values in hdf5 reader

2018-10-10 Thread Even Rouault
On mercredi 10 octobre 2018 17:28:59 CEST Bekaert, David (334H) wrote: > Dear GDAL developers, > > I generated a netcdf4 file using python netCDF4 module. > As indicated in the documentation, GDAL opens this file with the HDF5 reader > without problem. I am also able to properly display the geoco

[gdal-dev] parsing of netcdf4 no-data values in hdf5 reader

2018-10-10 Thread Bekaert, David (334H)
Dear GDAL developers, I generated a netcdf4 file using python netCDF4 module. As indicated in the documentation, GDAL opens this file with the HDF5 reader without problem. I am also able to properly display the geocoded file with QGIS (no-data not applied) and panoply (no-data applied). From re

Re: [gdal-dev] vsis3/vsicurl allowed-extensions per path?

2018-10-10 Thread Robert Coup
Hi Sean, Configuration management doesn't have to be so bad. I have an example of > how to do Rasterio-style configuration contexts, including reset, using > GDAL's Python bindings at > > > https://rasterio.readthedocs.io/en/latest/topics/configuration.html#gdal-example > (I love context managers

Re: [gdal-dev] vsis3/vsicurl allowed-extensions per path?

2018-10-10 Thread Sean Gillies
Hi Rob, On Wed, Oct 10, 2018 at 7:39 AM Robert Coup wrote: > Hi all, > > Wondering about being able to set CPL_VSIL_CURL_ALLOWED_EXTENSIONS on a > specific dataset rather than as a global option. This would allow opening > multiple files in the same process without needing to manage setting & >

Re: [gdal-dev] vsis3/vsicurl allowed-extensions per path?

2018-10-10 Thread Robert Coup
Hi Even, On Wed, 10 Oct 2018 at 15:42, Even Rouault wrote: > > eg. gdal.Open("/vsis3?ext=.tif/mybucket/mypath/my.tif", ...) > > Hum, we should treat the path to the object as a real URL argument then, > so something like > > /vsis3?ext=.tif&object=mybucket/path/to/my.tif > If we're splitting it

Re: [gdal-dev] vsis3/vsicurl allowed-extensions per path?

2018-10-10 Thread Even Rouault
On mercredi 10 octobre 2018 14:38:51 CEST Robert Coup wrote: > Hi all, > > Wondering about being able to set CPL_VSIL_CURL_ALLOWED_EXTENSIONS on a > specific dataset rather than as a global option. This would allow opening > multiple files in the same process without needing to manage setting & >

Re: [gdal-dev] gdalautotest

2018-10-10 Thread Alan Stewart
Thank you, that worked! Alan Stewart Senior Software Engineer TerraGo Technologies 3200 Windy Hill Road, Suite 1550W Atlanta, GA 30339 USA O. +1 678.391.9615   www.terragotech.com -Original Message- From: Even Rouault Sent: Tuesday, October 09, 2018 5:39 PM To: gdal-dev@lists.osgeo.org

[gdal-dev] vsis3/vsicurl allowed-extensions per path?

2018-10-10 Thread Robert Coup
Hi all, Wondering about being able to set CPL_VSIL_CURL_ALLOWED_EXTENSIONS on a specific dataset rather than as a global option. This would allow opening multiple files in the same process without needing to manage setting & resetting configuration contexts. eg. gdal.Open("/vsis3?ext=.tif/mybucke

Re: [gdal-dev] WCS: Bug in WCSDataset110::GetCoverageRequest()

2018-10-10 Thread Ari Jolma
Hi Odd Ragnar, Without going very deep into this, I would do (and tried) gdalinfo "WCS:https://wms.geonorge.no/skwms1/wcs.hoyde-dtm1_32"; This tells me that the preferred version of the service is 2.0.1 and it serves coverage Coverage1. However, if I want to use service version 1.1.1, I do

Re: [gdal-dev] WCS: Bug in WCSDataset110::GetCoverageRequest()

2018-10-10 Thread Odd Ragnar Lydersen
I have investigated some more now, and I've found that the problem is perhaps the way I'm using the data source/service description file. Here is what I do: 1) I open the wcs by providing the coverage I want by using describecoverage in the url: std::string wcsDescribeCoverage = "WCS:https://wm