issue_comments: 43351948
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/131#issuecomment-43351948 | https://api.github.com/repos/pydata/xarray/issues/131 | 43351948 | MDEyOklzc3VlQ29tbWVudDQzMzUxOTQ4 | 2443309 | 2014-05-16T16:32:44Z | 2014-05-16T16:32:44Z | MEMBER | A couple more thoughts. I agree that staying metatdata unaware is the best course of action. However, I think you can do that but still carry the dataset and variable attributes (in the same manor that NCO and CDO do). You just want to be explicit in the documentation by saying that the attributes are from the original dataset and that xray is not attribute aware or a units system (except for the time variable I guess). |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
33637243 |