issue_comments: 284273455
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/1295#issuecomment-284273455 | https://api.github.com/repos/pydata/xarray/issues/1295 | 284273455 | MDEyOklzc3VlQ29tbWVudDI4NDI3MzQ1NQ== | 1217238 | 2017-03-05T23:40:57Z | 2017-03-05T23:40:57Z | MEMBER | I think it's confusing to use "coordinate" to refer to only variables matching dimension names and that "auxiliary coordinates" are not a type of coordinate. It just doesn't make any sense in terms of the usual rules for categorizing things. This is especially problematic for software like xarray which people use without looking carefully at the docs, and for which many users aren't familiar with CF conventions. So I feel pretty strongly that CF/NUG conventions get this one wrong, and for xarray we should say that anything in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
211888882 |