issue_comments: 73276393
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/316#issuecomment-73276393 | https://api.github.com/repos/pydata/xarray/issues/316 | 73276393 | MDEyOklzc3VlQ29tbWVudDczMjc2Mzkz | 1217238 | 2015-02-06T17:21:18Z | 2015-02-06T17:21:18Z | MEMBER | What a hassle! Unfortunately my experience has been that non-ISO conformant time units are not uncommon. I'll take a look into this. We did add one fix to improve the time unit parsing since the last release. You might want to try installing the dev version off github to see if it fixes your issue. Otherwise you can also do the sort of fixup you describe by loading the dataset with decode_cf=False, fixing the metadata and then calling xray.decode_cf. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
56817968 |