Hi Jonathan et. al.,
As a general matter, I think we ought to get to the heart of this
"dataset" concept. CF "datasets", that are not simple files, have been
in routine use for a long time. It is routine that the data object we
think of as a "CF thingy" is actually an aggregation of many files.
From the data user's point of view this is wholly transparent. He/she
does not (and should not) need to know the file management details of
the CF dataset. From the data creator's point of view this has also
been a non-issue, because time aggregations have the simplifying
property that each individual file is a CF dataset in its own right.
The min/max concept under discussion illustrates one of the special
cases where one has to be careful extending files into datasets. The
"ensembles" discussions that have occupied us recently illustrate some
much more challenging cases, for example, requiring that global
attributes from individual files get promoted into arrays of strings in
the "dataset" along the ensemble axis.
- Steve
=====================================
Jonathan Gregory wrote:
> Dear John
>
>
>> I wonder if we want to promote characterizing whole datasets inside every constituent of the set. Does CF do this in other contexts?
>>
>
> No, because CF does not have a concept of "dataset" yet i.e. there are no
> specific conventions for linking files.
>
> Cheers
>
> Jonathan
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://www.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
--
--
Steve Hankin, NOAA/PMEL -- Steven.C.Hankin at noaa.gov
7600 Sand Point Way NE, Seattle, WA 98115-0070
ph. (206) 526-6080, FAX (206) 526-6744
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20070110/4e86bfbf/attachment-0002.html>
Received on Wed Jan 10 2007 - 10:15:34 GMT
