This message came from the CF Trac system. Do not reply. Instead, enter your
comments in the CF Trac system at http://kitt.llnl.gov/trac/.
#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 markh):
> It is not recommended to have two multiple-valued time dimensions for
the data variable.
I am concerned about this 'recommendation'. Having a time dimension with
a time(time) coordinate and a forecast_period dimension with a
forecast_period(forecast_period) coordinate is a useful case which is
common in many of our data sets.
In this case there is generally a 2D auxiliary coordinate of
forecast_reference_time(time, forecast_period); this quite often
degenerates to a single value.
Similarly we have numerous data sets which have a time dimension with a
time(time) coordinate and a forecast_reference_time dimension with a
forecast_reference_time(forecast_reference_time) coordinate.
In this case there is generally a 2D auxiliary coordinate of
forecast_period(time, forecast_reference_time).
Both of these cases are deemed practical and are in widespread use in the
communities I am in contact with. There are a number of data analysis
processes which are assisted by the data sets being structured in this
way.
What is the intent of 'not recommended'?
Is this proposal intending to tell users not to encode their data sets in
this way?
Is this proposal intending to have a validation rule for CF to indicate
that this is invalid?
mark
\
\
\
--
Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/117#comment:5>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
This message came from the CF Trac system. To unsubscribe, without
unsubscribing to the regular cf-metadata list, send a message to
"[email protected]" with "unsubscribe cf-metadata" in the body of your
message.
