-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
attrs empty for open_mfdataset vs population for open_dataset #1037
Comments
This was certainly not an intentional change, but on the other hand, the original behavior was not tested or intentionally specified, either. It would be good to figure out where in |
@shoyer, the issue is at variables, coord_names, dims = merge_core(dict_like_objects, compat, join)
merged = Dataset._construct_direct(variables, coord_names, dims) drop the attributes. The solution is to do something like a merge of the |
In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity |
This should have been closed by #1038. |
Previously, a dataset would store
attrs
corresponding to netCDF global attributes. For some reason, this behavior does not appear to be supported anymore. Using this dataset: https://github.com/pydata/xarray-data/raw/master/rasm.ncThe attributes for
open_mfdataset
are missing whereas in previous versions of xarray I do not believe that this was the case because one of my scripts is failing because it does not obtain attributes when using theopen_mfdataset
initialization.@shoyer and @jhamman, is this the expected behavior and was the prior behavior simply an unspecified side-effect of the code vs a design decision? My preference would be to keep as many attributes as possible when using
open_mfdataset
to best provenance the dataset, i.e.,ds.attrs
should not be empty following initialization.The text was updated successfully, but these errors were encountered: