issue_comments: 871681764
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/5436#issuecomment-871681764 | https://api.github.com/repos/pydata/xarray/issues/5436 | 871681764 | MDEyOklzc3VlQ29tbWVudDg3MTY4MTc2NA== | 31376402 | 2021-06-30T19:49:24Z | 2021-06-30T19:49:24Z | CONTRIBUTOR | Hey guys! First of all thank you for the work on maintaining this package 😃 I am running into the same issue and it is partially blocking an open-source package (used in experimental quantum computing) from adopting the latest version of xarray. For our typical dataset this happens:
As default behavior this is totally unexpected because the variables attributes have nothing to do with the dataset itself. I am just trying to put all my data in a single container. (Am i using the wrong function for this?) And second, My suggestion is to do nothing by default, i.e. I understand there might be cases where combining the attributes makes sense, so maybe my suggestion only applies when only Hope my use case helps this discussion. In the meantime the workaround seems to be:
```bash <xarray.Dataset> Dimensions: (dim_0: 5) Dimensions without coordinates: dim_0 Data variables: x0 (dim_0) float64 1.0 1.0 1.0 1.0 1.0 y0 (dim_0) float64 1.0 1.0 1.0 1.0 1.0 === <xarray.DataArray 'x0' (dim_0: 5)> array([1., 1., 1., 1., 1.]) Dimensions without coordinates: dim_0 Attributes: name: x long_name: X position units: m batched: False ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
911513701 |