> This would be a non-trivial piece of work but until it is done I don't think > we can really know what we are missing in the CF attributes what WKT can > describe and needs to be included in use cases of CF datasets.
@JonathanGregory, this is currently supported in `pyproj` master: https://github.com/pyproj4/pyproj/blob/6390041fc2bfb569e90f615adb7ba75160d41aa8/pyproj/crs/_cf1x8.py You can see the tests that were run to check the conversion to/from the CF format of the projection [here](https://github.com/pyproj4/pyproj/blob/6390041fc2bfb569e90f615adb7ba75160d41aa8/test/crs/test_crs_cf.py). I didn't find any parameters that weren't able to be supported by WKT. However, there are many projections that WKT can describe that aren't supported by CF. There is an extensive list [here](https://proj.org/operations/projections/index.html) for projections supported by PROJ. Only a subset is supported by CF conventions. -- 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-586055272 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].
