-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Break up intake-xarray into separate drivers? #61
Comments
You may well have a point, but the original rationale was: that all these call xarray loader function |
Yes, I think that is sensible early on, just as we currently package a bunch of unrelated drivers together in |
Seems fine to me... |
Happy to write it up as a separate issue, but if this would help load zarrs which were not written with xarray, I'd also be in favor. I'm currently running into a KeyError on Stacktrace
|
LIke |
Thanks, @martindurant. |
Intake-xarray lumps together several different I/O backends. Grouping drivers by what they return (xarray in this case) is different from the usual pattern. We propose to break intake-xarray into intake-netcdf, intake-tiff with rasterio support (and maybe also tifffile support?), intake-png, and intake-zarr. We can maintain intake-xarray going forward as a metapackage that depends on these as a convenience and for back-compat.
The text was updated successfully, but these errors were encountered: