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-379651950,https://api.github.com/repos/pydata/xarray/issues/2042,379651950,MDEyOklzc3VlQ29tbWVudDM3OTY1MTk1MA==,10050469,2018-04-09T06:49:16Z,2018-04-09T06:49:16Z,MEMBER,"> I do not care about the ``to_rasterio`` but I do care about a ''to_tiff''
Yes sorry, I meant ``to_tiff``
> If xarray has no way to output tiffs then I cannot use xarray.
I'm not saying it shouldn't exist, I'm just asking whether it should be in the xarray codebase or elsewhere.
If you'd like to parse new attributes when opening the geotiff file this could be added easily. PRs are welcome!","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,312203596
https://github.com/pydata/xarray/issues/2042#issuecomment-379572622,https://api.github.com/repos/pydata/xarray/issues/2042,379572622,MDEyOklzc3VlQ29tbWVudDM3OTU3MjYyMg==,10050469,2018-04-08T18:45:40Z,2018-04-08T18:45:40Z,MEMBER,"> if the profile and tags were propagated through open_rasterio, then the second open would not be necessary and would be generally useful.
We have been adding new attributes like this recently (https://github.com/pydata/xarray/pull/1583 and https://github.com/pydata/xarray/pull/1740), so I don't see much trouble in adding a few more. Note that the rasterio object is available via the (undocumented) ``_file_obj`` attribute. So a quick workaround for you in the mean time would be to access the info you need directly via this object.
As for the ``to_rasterio`` method, I'm currently against it. I'm already starting to think that these kind of domain specific tools should exist in dedicated projects, not in the main xarray codebase. For rasterio in particular, it turns out that the geotiff/GDAL data model is fairly different from the xarray/NetCDF model. The rasterio folks have also shown only limited interest in our endeavor (https://github.com/mapbox/rasterio/issues/920), which is understandable. I don't have a strong opinion though, and I am curious if the @pydata/xarray crew sees it differently.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,312203596