@roy-lowry Ah, poor quality control on the quality control examples! I fixed the error in my [example](https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-563339265) above.
> Using alphanumeric sorting of labels to establish semantic relationships is a > technique I used in the 1990s until I saw the error of my ways. Ok, I see your point about relying on similar alphanumeric name structure. If there's a way to establish a linkage using mappings, that sounds much better. I'm not too familiar with the standard name table so forgive my naive suggestions. > I guess you could replace 'Result' at the start of the descriptions with 'A > quality flag that reports the result' I am OK with making this change when these names are added - @jessicaaustin any thoughts? Should we update the comment above with new phrasing? I do think improved examples in Chapter 3.5 in the conventions document would go a long way to clarifying usage of the collection of 'flag' standard names. After the lengthy discussion on the new `quality_flag` name, it would be shame for a newcomer to CF that wants to encode measurement quality information in CF to opt for `status_flag` when `quality_flag` (or any of the flags proposed here) might be more optimal, just because `status_flag` is used in the only example (Example 3.3) shown there with a standard name. To me, the standard names list is rather opaque, good examples go a long way to explain the intended usage. Someone would have to read Chapter 3.5, go to the standard names page, search for 'flag', and then compare the definitions to see what name is most appropriate for their situation. There was a lot of good background shared in that discussion on best practice, but it's basically lost unless the documentation gets an update (IMO). Thanks for your feedback thus far. Looking forward to merging these new terms if there's no dissent. -- 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/216#issuecomment-564107540 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].
