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/.
#108: Defining a domain for a cell_method
-----------------------------+------------------------------
Reporter: markh | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
\
\
\
\
\
\
Comment (by davidhassell):
Replying to [comment:8 taylor13]:
Hell Karl,
I would suggest that the presence of a "dimensions" attribute could be
enough to signify a dummy variable. The dummy variable may then be given a
netCDF type in usual manner. I.e. your
{{{
character rsut
rsut: dimensions="time lat lon";
rsut: type="float";
rsut: standard_name="toa_outgoing_shortwave_flux";
rsut: cell_methods="time: mean";
}}}
would become
{{{
float rsut
rsut: dimensions="time lat lon";
rsut: standard_name="toa_outgoing_shortwave_flux";
rsut: cell_methods="time: mean";
}}}
Scalar variables would be dealt with by assigning an empty string to the
"dimensions" attribute:
{{{
double scalar_var
scalar_var: dimensions="";
scalar_var: standard_name="something_or_other";
scalar_var: cell_methods="time: mean";
}}}
This is essentially the approach that I have used in the
[http://www.met.reading.ac.uk/~david/cfa/0.4/index.html "CFA-netCDF"
conventions], which describes the single file netCDF storage of datasets
aggregated across multiple files - in many ways a fully generalised
version NcML storage - and uses dummy netCDF variables.
Hope that helps,
All the best,
David
\
\
\
--
Ticket URL: <http://kitt.llnl.gov/trac/ticket/108#comment:9>
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
"majord...@lists.llnl.gov" with "unsubscribe cf-metadata" in the body of your
message.
