This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#105: Scalar Coordinates -----------------------------+---------------------------------------------- Reporter: markh | Owner: [email protected] Type: enhancement | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by markh): Replying to [comment:6 davidhassell]: Hello David I'll try to answer your questions > ''"The right hand column shows a number of current uses of scalar coordinates we have encountered in software creating CF NetCDF datasets. All of these examples become invalid if #104 is implemented but remain valid if #105 is implemented."'' > > Please could you say which software libraries these are? The software I am most aware of is a range of in house code bases, written in a variety of programming languages and interfacing to the NetCDF API, to write datasets. I know some of these interface to libraries, such as CDAT and Met Office IDL libraries, others make us of tools such as NCO and CDO and others are pretty self contained. There is quite a range of architectures. > What do you mean by ''"retaining backwards compatibility with pre 1.7 CF data sets."''? #104 proposes a change in interpretation of scalar coordinate variables. If 104 is adopted, we will need to retain the capability to recognise one interpretation of scalars for <= 1.6 datasets and another for >= 1.7 data sets. > The same holds, in my view, for your forecast times example. In general, a single forecast can have many times (and therefore forecast periods) but only one forecast reference time The models which output data don't define the nature of the three time coordinate inter-relationship, the only define that there are two degrees of freedom. All interpretations of this statement are equally valid, and useful, when the data is created. The representation you have used is not one I would choose to use, even if I no longer had access to scalar coordinates, it does not represent my understanding of the use of time in our forecast models. mark -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/105#comment:7> CF Metadata <http://cf-pcmdi.llnl.gov/> 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.
