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/.
#79: Handling and formatting of vector quantities in CF -----------------------------+---------------------------------------------- Reporter: lavergne | Owner: [email protected] Type: enhancement | Status: reopened Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: vector -----------------------------+---------------------------------------------- Comment (by pbentley): Replying to [comment:57 markh]: > Perhaps we could define the following to deliver to the scope of this ticket. > * Container variable ... * container_type ... * container_name ... > > what do you think? I think that your proposed scheme, or something close to it, would be workable. As I hinted at back in comment:48, however, I do wonder to what extent we could - or should - exploit the basic machinery for handling groups of variables as provided by the netCDF-4 library (in combination with the enhanced data model). It would seem to make sense to exploit that capability, rather than retro-fit it to the netCDF-3 world. If we were to endorse a netCDF-3 classic implementation - either exclusively, or as an option - then I can foresee a scenario whereby countless developers of netCDF client tools will each roll their own custom (and potentially incompatible) solutions for handling groups of variables. From comments made earlier against this ticket, I realise that there is some resistance to going down the full netCDF-4 path. But if we are unwilling to adopt a feature as compelling as netCDF-4 groups to handle, erm, grouping of variables, then I wonder what, if anything, might prompt us to make the transition? I realise that I have drifted off topic somewhat. Apologies for that. To reiterate: yes, I think the metadata/data model being proposed could be made to work using either the netCDF-3 or netCDF-4 data models. But if we were to endorse/support both approaches then I suspect that developers probably will only target the former. Phil -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/79#comment:58> 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.
