issues: 636493109
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 636493109 | MDU6SXNzdWU2MzY0OTMxMDk= | 4142 | Should we make "rasterio" an engine option? | 291576 | closed | 0 | 6 | 2020-06-10T19:28:49Z | 2021-05-27T16:17:53Z | 2021-05-27T16:17:53Z | CONTRIBUTOR | In a similar vein to how #4003 is going for zarr files, I would like to see if a rasterio engine could be created so that geotiff files could get opened through open_mfdataset() and friends. I am willing to put some cycles to putting this together. It has been a long time since I did the initial prototype for the pynio backend back in the xray days. Does anyone see any immediate pitfalls or gotchas for doing this? |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4142/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |