Closed cwerner closed 3 years ago
I don't know if this is well documented, but if you have multiple chained protocols in your url, then storage_options should be split for each protocol, so the block would look like
storage_options:
s3:
anon: true
default_fill_cache: false
client_kwargs:
endpoint_url: 'https://s3.imk-ifu.kit.edu:8082'
and this would allow you to specify options for the simplecache part separately, if you want to.
Oh wow! So easy... and totally not what I'd have expected to be the cause. Thanks a bunch!
Would be glad to see examples like this added to the docs or examples folder - or even mentioned in the intake or fsspec pages.
Hi 👋
[and sorry for bothering the list again - please let me know if usage questions should go elsewhere].
I came across another roadblock for my use of
intake-xarray
and was wondering if this is a known problem or if I do things the wrong way...I want to read a NetCDF file from our local S3 server (NetApp). I can do it manually like so:
However, with my catalog.yml I cannot seem to load this file. This is currently the intake catalog:
I try to load the data like this:
This results in a huge traceback (
NoCredentialsError
). I wonder if intake parses any environment variables that interfere or if the catalog is not correct?