issue_comments: 407394381
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/2288#issuecomment-407394381 | https://api.github.com/repos/pydata/xarray/issues/2288 | 407394381 | MDEyOklzc3VlQ29tbWVudDQwNzM5NDM4MQ== | 1828519 | 2018-07-24T12:47:55Z | 2018-07-24T12:47:55Z | CONTRIBUTOR | @snowman2 I thought about that too, but here are the reasons I came up with for why this might not be the best idea:
The result of this github issue should either be a new package that solves all (90+%) of these topics or an easy to implement, easy to use, geolocation description best practice so that libraries can more easily communicate. I think with the CF standard CRS object we would definitely need a new library to provide all the utilities for converting to and from various things. Lastly, I don't know if I trust CF to be the one source of truth for stuff like this. If I've missed some other obvious benefits of this or if working with WKT or the CF standard CRS attributes isn't actually that complicated let me know. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
341331807 |