issue_comments: 385451826
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-385451826 | https://api.github.com/repos/pydata/xarray/issues/2042 | 385451826 | MDEyOklzc3VlQ29tbWVudDM4NTQ1MTgyNg== | 306380 | 2018-04-30T16:26:13Z | 2018-04-30T16:26:13Z | MEMBER | When writing https://github.com/pydata/xarray/issues/2093 I came across this issue and thought I'd weigh in. The GIS community seems like a fairly close neighbor to XArray's current community. Some API compatibility here might be a good to expand the community. I definitely agree that GeoTiff does not implement the full XArray model, but it might be useful to support the subset of datasets that do, just so that round-trip operations can occur. For example, it might be nice if the following worked: ```python dset = xr.open_rasterio(...) do modest modifications to destdset.to_rasterio(...) ``` My hope would be that the rasterio/GDAL data model would be consistent enough so that we could detect and err early if the dataset was not well-formed. |
{
"total_count": 4,
"+1": 4,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
312203596 |