I'm trying to make a NetCDF CF-compliant, where the
crs variable uses a WKT string. I'm using this compliance checker, testing against CF 1.7. I'm getting errors that certain attributes should be defined, even though the information requested is already in the WKT string.
This seems like a bug, but in example 5.12 in this section of the CF 1.8 conventions, there are attributes defined that are also in the WKT string, e.g. false easting/northing, lon/lat of projection meridian/origin. Is there a reason for this? Or, does this seem like something to bring up with contributors to the CF convention, or developers of the compliance checker?