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:
Keywords: |
----------------------------+------------------------------
\
\
In his post http://mailman.cgd.ucar.edu/pipermail/cf-
metadata/2006/001008.html, Jonathan thoroughly summarizes possible
scenarios that require multiple time axes in a CF file (for example, for
handling both forecast (valid) times, and the run time of the forecast.
He concludes with the proposal to add an example as described below.
From a look at section 5.7, it doesn't appear the example has been added.
This ticket proposes adding it.
Reference also ticket #104, though I don't believe the changes resulting
from that ticket affect this one.
> I think what we need to do is add an example of structure (b), and here
is one (an instance of case v) from the earlier discussion.
>> 20030101 12:00 analysis (at 00hr) and 12hr,36hr forecasts
>> 20030101 00:00 analysis 6hr,12hr,18hr,24hr forecasts
>> 20030101 06:00 analysis 6hr,18hr forecasts
>could be expressed as follows (ordering the time samples as they are
above)
variables:
double reftime(record);
time1:standard_name = "forecast_reference_time" ;
time1:units = "hours since 2003-01-01 00:00" ;
double valtime(record);
time2:standard_name = "time" ;
time2:units = "hours since 2003-01-01 00:00" ;
float temp(record,level,lat,lon);
temp:long_name = "Air temperature on model levels" ;
temp:standard_name = "air_temperature" ;
temp:units = "K" ;
temp:coordinates = "valtime reftime"
data:
reftime = 12., 12., 12., 0., 0., 0., 0., 6., 6. ;
valtime = 12., 24., 48., 6., 12., 18., 24., 12., 24. ;
\
\
\
--
Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/117>
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.
