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/2308#issuecomment-428177967,https://api.github.com/repos/pydata/xarray/issues/2308,428177967,MDEyOklzc3VlQ29tbWVudDQyODE3Nzk2Nw==,8699967,2018-10-09T12:46:54Z,2018-10-09T12:46:54Z,CONTRIBUTOR,Feel free to re-open if this becomes something of interest. Thanks!,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,344058811
https://github.com/pydata/xarray/issues/2308#issuecomment-407862762,https://api.github.com/repos/pydata/xarray/issues/2308,407862762,MDEyOklzc3VlQ29tbWVudDQwNzg2Mjc2Mg==,8699967,2018-07-25T19:07:27Z,2018-07-25T19:07:27Z,CONTRIBUTOR,"@fmaussion, I guess the main reason for the proposed change is to be able to read in the raster using `open_rasterio()` and be able to generate a netCDF using `to_netcdf()` that would be compatible with the rasterio model when using `rasterio.open()`. 

Also, since: ""xarray.Dataset is an in-memory representation of a netCDF file"", to me it makes more sense to store the data in a standard netCDF location that is consistent regardless of the backend. In doing so, other parts of xarray and libraries build off of xarray won't be required to find the same data in multiple locations.

Thanks for taking the time to consider this idea. I have used it quite a bit and it has made the datasets compatible across the various GIS tools I use (rasterio, GDAL, QGIS). It has definitely made my life easier and so I wanted to share what I have learned. But, it is just an idea. I really appreciate the work of the xarray developers and whatever y'all decide is fine with me.

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,344058811
https://github.com/pydata/xarray/issues/2308#issuecomment-407610465,https://api.github.com/repos/pydata/xarray/issues/2308,407610465,MDEyOklzc3VlQ29tbWVudDQwNzYxMDQ2NQ==,8699967,2018-07-25T02:12:16Z,2018-07-25T02:12:16Z,CONTRIBUTOR,That is strange. Was the variable put in `data_vars` and not in `coords`?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,344058811
https://github.com/pydata/xarray/issues/2308#issuecomment-407541054,https://api.github.com/repos/pydata/xarray/issues/2308,407541054,MDEyOklzc3VlQ29tbWVudDQwNzU0MTA1NA==,8699967,2018-07-24T20:28:28Z,2018-07-24T20:28:28Z,CONTRIBUTOR,I don't think so. The `crs` should already exist on the dataset beforehand and I think it may be a bit too much to expect it to add it to the dataset in that function as there are some that don't have it and not all xarray datasets are geospatially located.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,344058811