issue_comments: 385492564
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-385492564 | https://api.github.com/repos/pydata/xarray/issues/2042 | 385492564 | MDEyOklzc3VlQ29tbWVudDM4NTQ5MjU2NA== | 601025 | 2018-04-30T18:48:16Z | 2018-04-30T18:48:16Z | NONE | So far as I have run into open_rasterio takes care of most things out of the box. Besides how to deal with chunks, there is also how to deal with several types of metadata:
Whether xarray/open_rasterio uses the same interface or not, there will be a need to deal with file metadata and per-band metadata. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
312203596 |