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/6448#issuecomment-1098400102,https://api.github.com/repos/pydata/xarray/issues/6448,1098400102,IC_kwDOAMm_X85BeEFm,8699967,2022-04-13T19:21:59Z,2022-04-13T19:21:59Z,CONTRIBUTOR,">  GDAL doesn't actually need the CRS stored with the _CRS convention as documented in their ZARR driver specification?

GDAL may need to update the ZARR driver. The NetCDF driver does support CF. It would be good for them to be consistent.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1194993450
https://github.com/pydata/xarray/issues/6448#issuecomment-1098342334,https://api.github.com/repos/pydata/xarray/issues/6448,1098342334,IC_kwDOAMm_X85Bd1--,8699967,2022-04-13T18:11:21Z,2022-04-13T18:11:21Z,CONTRIBUTOR,"Top reasons for using CF over a CRS attribute:

- Supported by geospatial & netCDF software (GDAL/Esri/Unidata)
- Attributes are easily lost [ref](https://corteva.github.io/rioxarray/stable/getting_started/manage_information_loss.html)
- Encourage more usage of standard mechanisms of CRS storage","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1194993450
https://github.com/pydata/xarray/issues/6448#issuecomment-1098333054,https://api.github.com/repos/pydata/xarray/issues/6448,1098333054,IC_kwDOAMm_X85Bdzt-,8699967,2022-04-13T18:00:12Z,2022-04-13T18:00:12Z,CONTRIBUTOR,This document is also a useful reference for storing CRS in xarray: https://corteva.github.io/rioxarray/stable/getting_started/crs_management.html,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1194993450
https://github.com/pydata/xarray/issues/6448#issuecomment-1098331427,https://api.github.com/repos/pydata/xarray/issues/6448,1098331427,IC_kwDOAMm_X85BdzUj,8699967,2022-04-13T17:58:19Z,2022-04-13T17:58:19Z,CONTRIBUTOR,"> Instead, it recommends to use CF conventions for encoding CRS. This is more compatible with NetCDF, but won't be parsed correctly by GDAL.

GDAL does support the CF conventions for storing the CRS.

https://gdal.org/drivers/raster/netcdf.html#georeference

""The driver first tries to follow the CF-1 Convention from UNIDATA looking for the Metadata named “grid_mapping”.""","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1194993450