issue_comments: 1236756285
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/6752#issuecomment-1236756285 | https://api.github.com/repos/pydata/xarray/issues/6752 | 1236756285 | IC_kwDOAMm_X85Jt2c9 | 4160723 | 2022-09-05T09:26:36Z | 2022-09-05T09:26:36Z | MEMBER | Thanks for the issue report @lukasbindreiter, I opened #6987. As a workaround, you could use Regarding (de)serialization (from)to netCDF or other formats, I wonder if building multi-indexes or other custom indexes when opening the dataset couldn't be done via some custom Xarray IO backend (https://docs.xarray.dev/en/stable/internals/how-to-add-new-backend.html). I'm not sure how easy / hard it is to implement a custom backend on top of an existing one, though. For the serialization, Xarray doesn't support custom writable backends (yet), but since multi-index levels are now real coordinates maybe a custom backend is not really needed. Right now Xarray raises |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1293460108 |