See issue #216 for discussion of these changes, specifically in the [comment on 
Dec 
10](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, currently numbered '3.2.1' 
pending agreement on where this section belongs in the docs. (I used 
'3.2.1' because I didn't want to renumber all the examples until 
there was agreement on whether this text and example is in the proper location 
with respect to other material in Chaps 3.4 and 3.5)
- resolves a mis-ordering issue in the accompanying text for Example 3.4 in the 
master branch of draft 1.8 docs (text for Example 3.4 and Example 3.5 appear to 
be reversed). 
- corrects a dead link in toc-extra.adoc (the current master branch includes 
duplicate links in the 'List of Examples' section to Example 3.5 - i.e. 
both Example 3.4 and 3.5 links point to 3.5).  This PR fixes the dead link to 
Example 3.4.
- 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.

I will revise the PR to change Example 3.2.1 to 3.3 (or whichever appropriate 
number)  when there's agreement on whether and where this addition belongs, 
bumping the other Chapter 3 example numbers accordingly.

cc @davidhassell: Because this PR resolves some outstanding issues in the 1.8 
CF docs, may I suggest it be considered for inclusion before CF 1.8 is released 
next month?  I know it's late to the game, but I think it will benefit the 
new release overall.  The release notice you sent out a few days ago prompted 
me to polish off this PR and submit in case.  

Happy to revise content of descriptions or examples if necessary, some 
rewording may be needed.  I see several phrases I'd like to change in 
putting this PR together.  



You can view, comment on, or merge this pull request online at:

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

-- Commit Summary --

  * Add explaination of status_flag, quality_flag, others to 3.4

-- File Changes --

    M ch03.adoc (85)
    M toc-extra.adoc (3)

-- Patch Links --

https://github.com/cf-convention/cf-conventions/pull/235.patch
https://github.com/cf-convention/cf-conventions/pull/235.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/235

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