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

[raybellwaves]

This came recently as I was struggling to open a url using xarray. Goes back to pydata/xarray#2233; pydata/xarray#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]

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]

+1

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

intake/intake-xarray#98