<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style="font-family:Arial;">Hi,<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">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:<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">> export AWS_S3_ENDPOINT=...<br></div><div style="font-family:Arial;">> gdalmdiminfo ...<br></div><div style="font-family:Arial;">> unset AWS_S3_ENDPOINT<br></div><div style="font-family:Arial;">> gdalmdiminfo ...<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">you can do:<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">> AWS_S3_ENDPOINT=... gdalmdiminfo ...<br></div><div style="font-family:Arial;">> gdalmdiminfo ...<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Laurentiu<br></div><div style="font-family:Arial;"><br></div><div>On Wed, Feb 19, 2025, at 02:50, Michael Sumner via gdal-dev wrote:<br></div><blockquote type="cite" id="qt" style=""><div dir="ltr"><div><div>This may well just be a hapless user-question, can we set configs to empty and expect that to mean "unset"?<br></div><div><br></div><div>In a fresh session all is well (standard public bucket): <br></div><div><br></div><div>gdalmdiminfo /vsis3/mur-sst/zarr<br></div><div><br></div><div>Our non-standard public bucket can't be found of course, so set the endpoint: <br></div><div><br></div><div>export AWS_S3_ENDPOINT=<a href="http://projects.pawsey.org.au">projects.pawsey.org.au</a><br></div><div>gdalmdiminfo /vsis3/idea-10.7289-v5sq8xb5/<a href="http://www.ncei.noaa.gov/data/sea-surface-temperature-optimum-interpolation/v2.1/access/avhrr/198109/oisst-avhrr-v02r01.19810901.nc">www.ncei.noaa.gov/data/sea-surface-temperature-optimum-interpolation/v2.1/access/avhrr/198109/oisst-avhrr-v02r01.19810901.nc</a><br></div><div><br></div><div>but now <br></div><div><br></div><div>gdalmdiminfo /vsis3/mur-sst/zarr<br></div><div>ERROR 4: `/vsis3/mur-sst/zarr' not recognized as being in a supported file format.<br></div><div><br></div><div>this fails, but I expected it to work: <br></div><div><br></div><div>export AWS_S3_ENDPOINT=<br></div><div>gdalmdiminfo /vsis3/mur-sst/zarr<br></div><div><br></div><div>this succeeds: <br></div><div><br></div><div>unset AWS_S3_ENDPOINT<br></div><div>gdalmdiminfo /vsis3/mur-sst/zarr<br></div><div><br></div><div>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"?<br></div></div><div><br></div><div>Thanks for your help. <br></div><div><br></div><div><div>Cheers, Mike<br></div><div><br></div><div><br></div></div><div><br></div><div><span class="qt-gmail_signature_prefix">--</span><br></div><div dir="ltr" class="qt-gmail_signature"><div dir="ltr"><div>Michael Sumner<br></div><div>Research Software Engineer<br></div><div>Australian Antarctic Division<br></div><div>Hobart, Australia<br></div><div>e-mail: <a href="mailto:mdsumner@gmail.com" target="_blank">mdsumner@gmail.com</a><br></div></div></div></div><div>_______________________________________________<br></div><div>gdal-dev mailing list<br></div><div><a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br></div><div><a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></div><div><br></div></blockquote><div style="font-family:Arial;"><br></div></body></html>