#140: Clarifying the role of attributes on boundary variables.
-----------------------------+------------------------------------------
Reporter: davidhassell | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords: boundary variable, attribute
-----------------------------+------------------------------------------
Comment (by jonathan):
Dear Karl and David
I agree with this text as well, thank you. I suggest a reordering of the
penultimate sentence, and I think with this rewording "the" is better than
"a" in the final sentence:
If a parametric coordinate variable with a `formula_terms` attribute
(ref section 4.3.2) also has a `bounds` attribute, it is strongly
recommended that its boundary variable has a `formula_terms` attribute
too. Because the same standard name must describe both variables, the
formula must have the same terms (as specified in Appendix D), but a
different variable must be named by the two `formula_terms` attributes for
any term which depends on the vertical dimension, because the boundary
variables have one more dimension. In addition, any formula terms variable
which is an auxiliary coordinate variable may have a `bounds` attribute to
identify its boundary variable. In that case, the `formula_terms`
attribute of the boundary variable and the `bounds` attribute of the
formula terms variable must be consistent.
I'm very glad we seem likely agree this at last! I think an example is
also needed, as we previously discussed, presumably the one with both
methods shown. David, please could you repeat the proposed example? Also,
please could you draft the required changes to the conformance document?
We can discuss that if you like.
I assume that if we accept this ticket we also accept the uncontroversial
main part of David's proposal in the initial statement, about all the
other attributes of boundary variables. I'm still happy with that part.
Are you, Karl?
In addition, if we accept this ticket, we can close ticket 147, since this
one has dealt with the issue. It's a long-standing issue in CF, and it's
good to have it resolved!
Best wishes
Jonathan
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:15>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
