Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring comparison with grid mapping parameters (#222)

2020-01-13 Thread Dave Allured
Moving toward WKT would be facilitated by a few software modules that interpret WKT and translate to familiar CF grid_mapping parameters, when reasonably compatible. @snowman2 wrote: > with the GDAL Barn changes (https://gdalbarn.com/), reading in a WKT is much > more practical with PROJ as a

Re: [CF-metadata] [cf-convention/cf-conventions] Correct the wording in the conformance document section 2.3 "Naming Conventions" (#226)

2020-01-13 Thread Andrew Barna
Should the CF conventions documentation adopt [BCP 14](https://tools.ietf.org/html/bcp14) [[RFC2119](https://tools.ietf.org/html/rfc2119)] [[RFC8174](https://tools.ietf.org/html/rfc8174)]? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or

Re: [CF-metadata] [cf-convention/cf-conventions] Correct the wording in the conformance document section 2.3 "Naming Conventions" (#226)

2020-01-13 Thread taylor13
likewise, I think this correction should be made. -- 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/226#issuecomment-573759928 This list forwards relevant notifications

Re: [CF-metadata] [cf-convention/cf-conventions] Correct the wording in the conformance document section 2.3 "Naming Conventions" (#226)

2020-01-13 Thread Rosalyn Hatcher
I agree with this and am happy with the PR. -- 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/226#issuecomment-573758270 This list forwards relevant notifications from

Re: [CF-metadata] [cf-convention/cf-conventions] 2.3 must -> should (#227)

2020-01-13 Thread David Hassell
@davidhassell pushed 1 commit. c3fa6fd5ac220a707250b7523bfbd6c1cdb103d6 Move to Requirements -- You are receiving this because you are subscribed to this thread. View it on GitHub:

[CF-metadata] [cf-convention/cf-conventions] 2.3 must -> should (#227)

2020-01-13 Thread David Hassell
See issue #226 for discussion of these changes. You can view, comment on, or merge this pull request online at: https://github.com/cf-convention/cf-conventions/pull/227 -- Commit Summary -- * 2.3 must - should -- File Changes -- M conformance.adoc (2) -- Patch Links --

[CF-metadata] [cf-convention/cf-conventions] Correct the wording in the conformance document section 2.3 "Naming Conventions" (#226)

2020-01-13 Thread David Hassell
**Title:** Correct the wording in the conformance document section 2.3 "Naming Conventions" **Moderator:** @RosalynHatcher **Requirement Summary:** The conventions say, in section 2.3, that "Variable, dimension, attribute and group names _should_ begin with a letter, ...", but the

Re: [CF-metadata] [cf-convention/cf-conventions] Should we clarify the backwards compatibility objective? (#207)

2020-01-13 Thread Daniel Lee
Closed #207 via 27b466fd332e22ca8f2853e6ba2ac0eb15444ca0. -- 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/207#event-2943535447 This list forwards relevant notifications

Re: [CF-metadata] [cf-convention/cf-conventions] Should we clarify the backwards compatibility objective? (#207)

2020-01-13 Thread Daniel Lee
Dear all, Thanks for the productive conversation around this topic - consensus seems to have been reached and therefore as noted previously I am merging this request. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: