issue_comments: 391144127
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/1809#issuecomment-391144127 | https://api.github.com/repos/pydata/xarray/issues/1809 | 391144127 | MDEyOklzc3VlQ29tbWVudDM5MTE0NDEyNw== | 1217238 | 2018-05-22T21:18:41Z | 2018-05-22T21:18:41Z | MEMBER | See https://stackoverflow.com/questions/50475453/xarray-cannot-serialize-coordinates/50475925. It seems like WRF may often produce netCDF files that lead to this issue. If the problem can be reproduced by simply opening and resaving a netCDF file then we may want to revisit our logic in xarray, because we always want |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
286072335 |