Dear @atmodatcode Thanks for your proposal. In fact the [rules for changing the conventions](https://urldefense.us/v3/__http://cfconventions.org/rules.html__;!!G2kpM7uM-TzIFchu!gylT2XXC8WSaHPC0A1ZMshzVxtz2GadZcG5Fz59sWJO_IdgIryZzsIaHo6OzakimUdXLFw9fPks$ ) require a test file to be produced for each change, but that rule has never been followed, and no test files have ever been presented. As far as I know, the examples in the document exist only "on paper", and no netCDF files have been produced. Your request for the example files is reasonable and our rules anticipate it, but unfortunately we haven't got any to give you!
I suppose that one obstacle to producing files when changes are proposed is that the proposal typically affects only one feature, whereas an example file needs a lot more contents that aren't relevant to the change. A strict requirement to create such a file might delay or prevent changes being implemented, because of the extra work. In any case, that wouldn't address the request for files to illustrate the _existing_ conventions. It would be useful to know what people think about whether and how such files could be provided. Best wishes Jonathan -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/348*issuecomment-1008911432__;Iw!!G2kpM7uM-TzIFchu!gylT2XXC8WSaHPC0A1ZMshzVxtz2GadZcG5Fz59sWJO_IdgIryZzsIaHo6OzakimUdXLVSjU80k$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/348/[email protected]> 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].
