how to handle url's which aren't xarray friendly

intake / intake-thredds

Intake interface to THREDDS data catalogs

https://intake-thredds.readthedocs.io/

Apache License 2.0

11 stars 7 forks source link

how to handle url's which aren't xarray friendly #24

Open raybellwaves opened 3 years ago

raybellwaves commented 3 years ago

This came recently as I was struggling to open a url using xarray. Goes back to https://github.com/pydata/xarray/issues/2233; https://github.com/pydata/xarray/issues/2368

@rsignell-usgs suggested using NetCDF4 https://stackoverflow.com/a/66247797/6046019

Just an FYI. Not sure if it will cause a headache here.

aaronspring commented 3 years ago

While the data is available via thredds, these are challenges on open_dataset we probably won't cover here. Only what works in intake-xarray will work here as well

pbranson commented 3 years ago

Whilst I agree that here isnt the place to handle this just flagging that the diaspora of intake-xarray, fsspec and xarray-backends is causing a number of usability issues for intake+netcdf_opendap

https://github.com/intake/intake-xarray/issues/98