Replaces: #235

See issue #216 for discussion of these changes, specifically in [this 
comment](https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-564107540)
 suggesting adding to the CF documentation usage examples for status_flag, 
quality_flag, and related QC flag standard names proposed in #216.

This PR includes the following:

- adds to Chapter 3.4 new text describing usage of ancillary variables as 
status/quality flags, and a new Example 3.3 illustrating their use
- adds `status_flag` attributes to Example 3.5 as suggested in #216 and earlier 
discussions in the CF mailing list surrounding the addition of `quality_flag`.  
See [this 
thread](http://mailman.cgd.ucar.edu/pipermail/cf-metadata/2019/020995.html) in 
the CF list archives for related discussion. 
You can view, comment on, or merge this pull request online at:

  https://github.com/cf-convention/cf-conventions/pull/264

-- Commit Summary --

  * Add explanation of status_flag, quality_flag, others to 3.4
  * Change example numbers in Chapter 3.4

-- File Changes --

    M ch03.adoc (66)
    M toc-extra.adoc (9)

-- Patch Links --

https://github.com/cf-convention/cf-conventions/pull/264.patch
https://github.com/cf-convention/cf-conventions/pull/264.diff

-- 
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/pull/264

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].

Reply via email to