issue_comments: 279101252
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/pull/1260#issuecomment-279101252 | https://api.github.com/repos/pydata/xarray/issues/1260 | 279101252 | MDEyOklzc3VlQ29tbWVudDI3OTEwMTI1Mg== | 1217238 | 2017-02-11T00:14:36Z | 2017-02-11T00:14:36Z | MEMBER | Getting optional coordinates is hard is because the current "backends" system in xarray was really only designed for handling netCDF-like libraries. For example, every backend gets passed through One alternative would be to simply write a function for reading files with rasterio straight into xarray Dataset objects. There are probably hacks that can get this working with data stores but this really calls out for the bigger refactor like https://github.com/pydata/xarray/pull/1087. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
206905158 |