#117: add example to 5.7 for multi-time dimension data
-----------------------------+------------------------------
Reporter: graybeal | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Comment (by jonathan):
Dear John
As Martin says, the existing `forecast_period` standard name is your time
offset. I would not be in favour of a generic name, unless a generic use-
case comes up which requires it - being more specific is generally more
informative.
I agree that two time dimensions is an more efficient way to handle this
situation if all combinations are present. We could have examples of this
too. However, in a separate email discussion, I think (if I have
understood correctly - not having read the emails very carefully) it's
been suggested that some software would be upset by having more than one
multivalued time dimension. The arrangement with a single time dimension
and multiple auxiliary coordinate variables is more flexible, and
especially it can deal with the case of missing combinations, so I think
we should add it (the main purpose of this ticket).
Best wishes
Jonathan
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/117#comment:13>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
