While the language in the NUG around “coordinate variables” is not completely
clear, I think it is clear that the NUG does not disallow `string x(x)` or
`char x(x,l)`, it even calls them out as “string-valued coordinate variables”.
The requirements for them are different than for numeric-valued
@martinjuckes I'm fine with must as opposed to shall.
Regarding the logical structure, Here's how I see the logical structure of the
paragraphs for dimension coordinate variables and auxiliary coordinate
variables. (I'm using the first version.)
As logic statements:
* IF dimension coordinate
FWIW, I think that 'must' will more naturally translate into 'required' in the
mind of the general reader than 'shall'. Hence, I too prefer 'must' over
'shall' in such situations.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
I also prefer the first version, and the option of keeping the recommendation
to avoid the form `x(x,l)` as it is.
I would prefer to use "must" rather than "shall". In most cases the existing
text uses "must", and introducing "shall" as a variation in a small number of
places looks confusing
@JonathanGregory I don't view the statement
> A one-dimensional auxiliary coordinate variable shall not have the same name
> as its dimension.
as a new requirement.
It is redundant to the statement in the previous paragraph
> A one-dimensional variable that is not a dimension coordinate variable
Dear Jim
Thanks for this text. I prefer the first version, since (as previously stated)
I don't think `string x(x)` should be allowed as a dimension coordinate
variable. Perhaps you could consider the following text from Hassell et al.
(2017, https://doi.org/10.5194/gmd-10-4619-2017):
>
@feggleton @japamment @ngalbraith @roy-lowry and others: thanks for publishing
the names, contributing to the discussion, and helping steer this through to
acceptance!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@feggleton thanks for publishing the names. I'm closing this issue now.
--
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/231#issuecomment-597603609
This list forwards
Closed #231.
--
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/231#event-3118573979
This list forwards relevant notifications from Github. It is distinct from
Closed #216.
--
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#event-3118570282
This list forwards relevant notifications from Github. It is distinct from
@feggleton thanks for publishing the names. I'm closing this issue now.
--
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-597603118
This list forwards
These changes have been published in version 72 of the standard name table.
Please close this issue if all discussions are complete.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
These changes have been published in version 72 of the standard name table. -
Please close this issue if all discussions are complete.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
13 matches
Mail list logo
