Re: [CF-metadata] [cf-convention/cf-conventions] Clarification of newline usage (Issue #347)
I think we should see `ncdump` as what it is, that is essentially a 3rd party debug tool. As such, its specific choice of output format, regrettable as it may be, doesn't have bearing on the CF conventions and imho poses no challenge to standards. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/347*issuecomment-1010234388__;Iw!!G2kpM7uM-TzIFchu!jmG9ULyq9pZjIw_Rp34Nun-fQBEG9L89zaJzU-uucN1wBI7rvTEE7YL-rS-SyUAnmYKZgirfWZI$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
Dear @JonathanGregory, such a clash is called a `conflict` in git lingo and indeed does occur. But it is also one of the most common problems in versioning and as such one of the core abilities and raison d'etre of git is to help with their resolution. So don't worry, this will be easy to address. Cheers Klaus -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/343*issuecomment-1010099749__;Iw!!G2kpM7uM-TzIFchu!hA5hDuCghUqHKq87ObIWy4siQqjYnDB2KJ_GhR1BTT2DxoZtJNlmp7tVQdXSLKoAg2Fvz7Gw6Oc$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
[CF-metadata] [cf-convention/cf-conventions] Correct errors in 1.9 Lossy Compression by Coordinate Subsampling (Issue #352)
# Moderator @davidhassell # Requirement Summary Ensure internal consistency and correctness of figure numbering, formulas, terms, examples # Technical Proposal Summary This issue addresses: - Correction of typos in formulas; - Correct figure numbering and change all figure numbering to consist of chapter number and figure number (such as Figure 8.2); - Correcting CDL examples to be consistent with chapter 8 body text; - Improve formulation of selected paragraphs; - Correct index in Figure J.2; - Make the term interpolation_subarea_flags mandatory in quadratic methods to avoid ambiguities in the interpretation of the flag variable. # Benefits Users of the conventions, in particular those implementing the conventions # Detailed Proposal See PR #351 -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/352__;!!G2kpM7uM-TzIFchu!kWrvK-c99j0PoVSJz3HqdjXge2vIIFaUwRI3OZXnRugmwx5IffRt3_S4_AQ1g_cSBp8zj0_YU7o$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Single-source the version number (Issue #343)
Dear @zklaus I've done a [pull request](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350__;!!G2kpM7uM-TzIFchu!h_4-L8njdnQuYrvIVsBWFfZZyiaEw7GB2tpt1NklqxCHzaGqwx_s6szUJC6W_hRzXiEzSDkGdyU$ ) to delete the `Conventions` attribute in the two examples, [as proposed](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/349__;!!G2kpM7uM-TzIFchu!h_4-L8njdnQuYrvIVsBWFfZZyiaEw7GB2tpt1NklqxCHzaGqwx_s6szUJC6W_hRzXiEzc5yb6to$ ). I suppose that might lead to a clash when merging, if your change updates the attributes, would it? I am not a git expert (as is well-known). 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/343*issuecomment-1009765855__;Iw!!G2kpM7uM-TzIFchu!h_4-L8njdnQuYrvIVsBWFfZZyiaEw7GB2tpt1NklqxCHzaGqwx_s6szUJC6W_hRzXiEzgJ2INvM$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
[CF-metadata] [cf-convention/cf-conventions] Issue349 (PR #350)
See issue 349 for discussion of these changes. # Release checklist - [NA] Authors updated in `cf-conventions.adoc`? - [NA] Next version in `cf-conventions.adoc` up to date? Versioning inspired by [SemVer](https://urldefense.us/v3/__https://semver.org__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwppnjGeDY$ ). - [Y] `history.adoc` up to date? - [NA] Conformance document up-to-date? # For maintainers After the merge remember to delete the source branch. Tags are set at the conclusion of the annual meeting; until then `master` always is a draft for the next version. You can view, comment on, or merge this pull request online at: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwpdPxuCOs$ -- Commit Summary -- * issue 349, delete Conventions attribute from ex 7.15 and 7.16 * updated history.adoc -- File Changes -- M ch07.adoc (2) M history.adoc (3) -- Patch Links -- https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350.patch__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwp15rj2c0$ https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350.diff__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwp97CguFQ$ -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/350__;!!G2kpM7uM-TzIFchu!hQgyxRXTKvpetADIxmFvwz7YuKdN_k6pMbdKcq_FNy7CfrLb-H8U203i00BaxtaJedwpdPxuCOs$ You are receiving this because you are subscribed to this thread. Message ID: cf-convention/cf-conventions/pull/3...@github.com This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Clarification of newline usage (Issue #347)
Yes, I agree with @Dave-Allured, especially as [section 2.6.2](https://urldefense.us/v3/__http://cfconventions.org/Data/cf-conventions/cf-conventions-1.9/cf-conventions.html*description-of-file-contents__;Iw!!G2kpM7uM-TzIFchu!kzQkK2mbh5fJEpI5XqSfg09DHBIi6I_9U8fyyvXd3XepTE8YIQbjLVgXomj3YzKXrwHAvia5oUA$ ) only is a *recommendation* that some may follow and others may not, and the word "readability" may be interpreted differently. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/347*issuecomment-1009726673__;Iw!!G2kpM7uM-TzIFchu!kzQkK2mbh5fJEpI5XqSfg09DHBIi6I_9U8fyyvXd3XepTE8YIQbjLVgXomj3YzKXrwHA7qX7Nt4$ You are receiving this because you are subscribed to this thread. Message ID: This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
