issue_comments: 130827459
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/pull/523#issuecomment-130827459 | https://api.github.com/repos/pydata/xarray/issues/523 | 130827459 | MDEyOklzc3VlQ29tbWVudDEzMDgyNzQ1OQ== | 950575 | 2015-08-13T20:17:10Z | 2015-08-13T20:35:08Z | CONTRIBUTOR |
I disagree. Maybe not even xray should "fix" this. There are two issues here: 1) Interpreting year 0 as 1; 2) Non-standard calendars. Maybe (2) should be in (1) is an UDUNITS ~~aberration~~ interpretation that made into some Conventions (CF and COARDS) and does not belong in the netCDF4 package. Does xray wants to became a CF CDM? I sure hope not! I have iris for that but for everything else I use xray. And if people really want to get those niche date specification from xray they can just read the raw time data and parse it using one of the several UDUNITS wrappers or convention compliance/checkers out there. Here is another one that should do the right thing here for that case: https://pypi.python.org/pypi/coards/1.0.5 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
99847237 |