Thanks all for the comments! My desire here is to unite the geospatial (OSGeo) and CF-conventions here to simplifying things when transitioning between the communities.
Much of the inspiration for this thought came when attempting to match PROJ parameters to the CF conventions as documented [here](https://github.com/cf-convention/cf-conventions/wiki/Mapping-from-CF-Grid-Mapping-Attributes-to-CRS-WKT-Elements#table-3---common-projection-parameter-names). There are several parameters that do not match up and in several cases a grid mapping does not exist.This is problematic for users who wish to convert back and forth between the two. However, since PROJ supports reading in the WKT string, the full CRS can be properly represented in that manner and no information is lost. Additionally, the [PROJ FAQ](https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems) strongly discourages the use of PROJ strings to represent the CRS and instead recommends using the WKT string. > Maybe the core of your proposal is actually best made to the GDAL / PROJ > project to modify default behavior when working with CF data? This would indeed be problematic and confusing for users of GDAL to change this as the behavior would differ from the CF spec. This is already done in `pyproj` and an issue exists due to users noting that the behavior differs from the spec [here](https://github.com/pyproj4/pyproj/issues/401). ### Alternative proposal? Thoughts on stating in the spec that if the CRS cannot be properly represented using the CF grid mapping parameters, that the CRS WKT form is recommended as a fall back (noting of course that this may not be compatible with some software)? Also, it would be good to note for users to make an issue in this repo with their CRS WKT that cannot be represented using the grid mapping parameters so the CF spec can be updated accordingly. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/222#issuecomment-569789956 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
