Hi, To me, that's a bit unexpected and possibly a bug, but not a problem I've ever run into in practice. You're probably aware of this already, but instead of:
> export AWS_S3_ENDPOINT=... > gdalmdiminfo ... > unset AWS_S3_ENDPOINT > gdalmdiminfo ... you can do: > AWS_S3_ENDPOINT=... gdalmdiminfo ... > gdalmdiminfo ... Laurentiu On Wed, Feb 19, 2025, at 02:50, Michael Sumner via gdal-dev wrote: > This may well just be a hapless user-question, can we set configs to empty > and expect that to mean "unset"? > > In a fresh session all is well (standard public bucket): > > gdalmdiminfo /vsis3/mur-sst/zarr > > Our non-standard public bucket can't be found of course, so set the endpoint: > > export AWS_S3_ENDPOINT=projects.pawsey.org.au > gdalmdiminfo > /vsis3/idea-10.7289-v5sq8xb5/www.ncei.noaa.gov/data/sea-surface-temperature-optimum-interpolation/v2.1/access/avhrr/198109/oisst-avhrr-v02r01.19810901.nc > > but now > > gdalmdiminfo /vsis3/mur-sst/zarr > ERROR 4: `/vsis3/mur-sst/zarr' not recognized as being in a supported file > format. > > this fails, but I expected it to work: > > export AWS_S3_ENDPOINT= > gdalmdiminfo /vsis3/mur-sst/zarr > > this succeeds: > > unset AWS_S3_ENDPOINT > gdalmdiminfo /vsis3/mur-sst/zarr > > My question is what is the right way to revert the non-standard endpoint? > We have to unset the option? Or, is an empty value a desirable way to mean > "default"? > > Thanks for your help. > > Cheers, Mike > > > > -- > Michael Sumner > Research Software Engineer > Australian Antarctic Division > Hobart, Australia > e-mail: mdsum...@gmail.com > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
