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/5782#issuecomment-924395904,https://api.github.com/repos/pydata/xarray/issues/5782,924395904,IC_kwDOAMm_X843GSmA,8699967,2021-09-21T21:24:03Z,2021-09-21T21:24:12Z,CONTRIBUTOR,"> xr.open_rasterio() is being used earlier in the pipeline

What issues do you have if you change to use `rioxarray.open_rasterio`?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,991857313
https://github.com/pydata/xarray/issues/5782#issuecomment-924395141,https://api.github.com/repos/pydata/xarray/issues/5782,924395141,IC_kwDOAMm_X843GSaF,8699967,2021-09-21T21:23:01Z,2021-09-21T21:23:01Z,CONTRIBUTOR,"This appears to not be an `xarray` issue since the code uses `open_dataset` and the `rio.crs` accessor. The `rio.crs` accessor is from `rioxarray`. From what I can tell, the issue has to do with the data is stored in the netCDF file: https://corteva.github.io/rioxarray/stable/getting_started/crs_management.html

My guess is that there is an attribute named `crs` with the contents `+init=EPSG:XXXX`. If that is the case, I recommend using `rioxarray` to do:

```python
data.rio.write_crs(""ESPG:XXXX"", inplace=True)
```

Hopefully this is helpful.




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