issue_comments: 338247940
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/1621#issuecomment-338247940 | https://api.github.com/repos/pydata/xarray/issues/1621 | 338247940 | MDEyOklzc3VlQ29tbWVudDMzODI0Nzk0MA== | 1217238 | 2017-10-20T15:57:14Z | 2017-10-20T15:57:14Z | MEMBER |
Rich, I know you've been involved in CF conventions and standard names, but I don't think the CF conventions on time apply directly here. These are "time difference" units, which are a distinct type of quantity. And assuredly the period of a wave is a type of "time difference" as well -- it's just not one that is useful to decode into an array with dtype Is there some other sort of metadata we could use to make this distinction of "physical" vs. "human" time differences? Now is a good time to make changes, since we are on the verge of making a major release (v0.10). Throwing out some ideas, none of which I particularly like (but to be clear, I don't like the status quo either):
1. We could unilaterally stop automatic decoding into |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
264321376 |