issue_comments: 159723927
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/665#issuecomment-159723927 | https://api.github.com/repos/pydata/xarray/issues/665 | 159723927 | MDEyOklzc3VlQ29tbWVudDE1OTcyMzkyNw== | 6628425 | 2015-11-25T20:29:27Z | 2015-11-25T20:29:27Z | MEMBER | @spencerahill I recall we only had this specific issue with the 2D time_bounds variable. Perhaps you have a specific example in mind, but in my experience xray handles reading in 2D lat and lon bounds variables OK. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
118525173 |