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/4142#issuecomment-642554262,https://api.github.com/repos/pydata/xarray/issues/4142,642554262,MDEyOklzc3VlQ29tbWVudDY0MjU1NDI2Mg==,10050469,2020-06-11T10:20:02Z,2020-06-11T10:20:02Z,MEMBER,"As a not-so-active-but-still-interested xarray dev my opinion doesn't count much, but I would be a proponent of having the rasterio backend live outside of xarray proper. 

At the time we wrote the  rasterio->DataArray conversion we already noticed a lot of issues regarding differences between the two datamodels, and  rio-xarray shows that there is a lot of logic and dev work necessary for this to go smoothly, which would be better handled outside of xarray. 

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,636493109