CF Compliance Check

[ErikKusch]

We should have a function that can check netcdfs for their CF compliance (not fix issue, just identify and communicate them).

[pvanlaake]

The ncdfCF package will flag certain CF formatting issues (such as mismatched coordinates attribute values, over-dimensioned boundary variables, or missing external_variables attributes) when opening a netCDF file. Other issues may be added to a future release of the package with some effort, like ordering of dimensions, the cell_methods attribute, character-type coordinate variables. The package cannot do a full compliance check (because it does not cover the full CF Metadata Standards).

But what is the purpose of doing the compliance check?

[ErikKusch]

The purpose is to gently introduce a wider audience to CF and also to streamline checking (but not fixing) CF compliance for a more advanced audience. Seeing how we build data discovery around CF compliant variable names, this seems like a good idea to round our data handling off. What do you think?