Mike,
Homework for me for this question was to see if other options behave
this way in terms of "default", and I didn't get to that today.
The more reliable way is unset an option is through the API with
CPLSetConfigOption(option_name, NULL).
Setting an empty string will *sometimes* have
actually I didn't know that particular syntax, thanks! I generally use
gdalmdiminfo --config NAME VALUE ...
for transient situations, but I need to have this for other downstream
packages as well.
Homework for me for this question was to see if other options behave this
way in terms of "default
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=... gdalmdimi
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_ENDPO
