issue_comments: 406696890
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/2042#issuecomment-406696890 | https://api.github.com/repos/pydata/xarray/issues/2042 | 406696890 | MDEyOklzc3VlQ29tbWVudDQwNjY5Njg5MA== | 1828519 | 2018-07-20T18:57:38Z | 2018-07-20T18:58:10Z | CONTRIBUTOR | I'd like to add to this discussion the issue I brought up here #2288. It is something that could/should probably result in a new xarray add-on package for doing these type of operations. For example, I work on the pyresample and satpy projects. Pyresample uses its own "AreaDefinition" objects to define the geolocation/projection information. SatPy uses these AreaDefinitions by setting Edit: by "add-on" I mean something like "geoxarray" where it is an optional dependency for a user that depends completely on xarray. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
312203596 |