issue_comments: 416811165
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-416811165 | https://api.github.com/repos/pydata/xarray/issues/2288 | 416811165 | MDEyOklzc3VlQ29tbWVudDQxNjgxMTE2NQ== | 6413369 | 2018-08-29T03:21:49Z | 2018-08-29T03:21:49Z | NONE | Also, please let me know about your ideas for features you would like to see in a crs library, either here or raise as an issue. Creating library specific objects might be a good idea, if you want to give some use cases and reasonings. In what ways are library soecific crs objects difficult to create? Don’t they provide shortcuts for creating from proj4 strings? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
341331807 |