issue_comments: 159717471
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/667#issuecomment-159717471 | https://api.github.com/repos/pydata/xarray/issues/667 | 159717471 | MDEyOklzc3VlQ29tbWVudDE1OTcxNzQ3MQ== | 2443309 | 2015-11-25T20:04:48Z | 2015-11-25T20:04:48Z | MEMBER | I think ultimately, these are going to end up as Variables, not Coordinates. The CF convention refers to them as "Boundary Variables", and although they are essentially metadata for the Coordinates, I don't think that sort of complexity makes sense for xray right now. It shouldn't be too hard to fix the 2-d bounds problem though. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
118910006 |