issue_comments: 289916013
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/1092#issuecomment-289916013 | https://api.github.com/repos/pydata/xarray/issues/1092 | 289916013 | MDEyOklzc3VlQ29tbWVudDI4OTkxNjAxMw== | 23484003 | 2017-03-28T21:51:30Z | 2017-03-28T21:51:30Z | NONE | One important reason to keep the tree-like structure within a dataset is that it provides some assurance to the recipient of the dataset that all the variables 'belong' in the same coordinate space. Constructing a tree (from a nested dictionary, say) whose leaves are datasets or dataArrays doesn't guarantee that the coordinates/dimensions in all the leaves are compatible, whereas a tree within the dataset does make a guarantee about the leaves. As far as motivation for making trees, I find myself with several dozen variable names such as As far as implementation, the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
187859705 |