issue_comments: 1099797820
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/6448#issuecomment-1099797820 | https://api.github.com/repos/pydata/xarray/issues/6448 | 1099797820 | IC_kwDOAMm_X85BjZU8 | 1197350 | 2022-04-15T02:38:48Z | 2022-04-15T02:38:48Z | MEMBER | I am guilty of sidetracking this issue into the politics of CRS encoding. That discussion is important. But in the meantime, @wankoelias's original issue reveals is narrower technical issue with Xarray's Zarr writer: Xarray won't let you serialize a dictionary attribute to zarr, even though zarr has no problem with this. That is a problem we can fix pretty easily. The We could refactor this function to be more flexible to account for zarr's broader range of allowed attribute types (as we have evidently already done for h5netcdf). Or we could just bypass it completely in the @wankoelias - you seem to understand the issue pretty well. Would you be game for making a PR? We would be glad to support you along the way. |
{
"total_count": 2,
"+1": 0,
"-1": 0,
"laugh": 2,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1194993450 |