issue_comments: 415633883
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-415633883 | https://api.github.com/repos/pydata/xarray/issues/2288 | 415633883 | MDEyOklzc3VlQ29tbWVudDQxNTYzMzg4Mw== | 1828519 | 2018-08-24T02:41:00Z | 2018-08-24T02:41:00Z | CONTRIBUTOR | FYI I've started a really basic layout of the CRS object in geoxarray: https://github.com/geoxarray/geoxarray It doesn't actually do anything yet, but I copied all the utilities from pyresample that are useful (convert PROJ.4 to cartopy CRS, proj4 str to dict, etc). I decided that the CRS object should use the CF conventions naming for projection parameters based on a conversation I had with @dopplershift. The main factor being they are much more human readable than the PROJ.4 names. The issue with this is that I have much more experience dealing with PROJ.4 parameters. I can probably also get a lot of information from metpy's CF plotting code: https://github.com/Unidata/MetPy/blob/master/metpy/plots/mapping.py |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
341331807 |