issue_comments: 848914165
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/5376#issuecomment-848914165 | https://api.github.com/repos/pydata/xarray/issues/5376 | 848914165 | MDEyOklzc3VlQ29tbWVudDg0ODkxNDE2NQ== | 88113 | 2021-05-26T16:23:13Z | 2021-05-26T16:23:13Z | NONE | I don't think I am familiar enough to really judge between the suggestions, @benbovy, but I'm intrigued. I think there's certainly something to be won just by having a data structure which says these arrays/datasets represent a multiscale series. One real benefit though will be when access of that structure can simplify the client code needed to interactively load that data, e.g. with prefetching. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
902009258 |