#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 taylor13):
Hi David,
Could you expand on why you think software will want to extract the so-
called "bounds" values for variables appearing in formula_terms along with
the values themselves? I would have thought that for parametric
coordinates you would want to primarily associate formula terms with the
coordinate values they are used to transform. So for the coordinates
themselves you would associate the parameter values in the formula_terms
that is attached to the parametric coordinate. For the *bounds* on that
coordinate you would associate the parameter values in the formula_terms
attached to the parametric coordinate's bounds.
Why is there any need to associate the parameter values used for
coordinate bound transformations with the parameter values used for
coordinate transformations. I should think these two sets of parameter
values will invariably be used independently. I suppose one might want to
put into a container all the coordinate and bound information, but I don't
think you would ever put the coordinate information and the coordinate and
bounds parameters together without also including the coordinate bounds
themselves. If this is the case then your code could easily construct
such a container without a "bounds" attribute attached to the parameter
variables.
I'm sorry if I'm a bit slow on this, but you seem to have a specific use
case where "working out" needed relationships is difficult. Could you
describe it in a bit more detail? This could help us reach consensus.
Sorry this seems to be taking up your valuable time, but I assure you if
there is a compelling use case, then I'll favor including Jonathan's
alternative.
best regards,
Karl
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:9>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
