Whether or not the entire netCDF4 enhanced data model is adopted, can I suggest that all features of the model are acknowledged and those that are not compatible with the 2.0 conventions are explicitly identified.
As an example, I currently find nothing in the current conventions to say that the use of groups is incompatible with the conventions, yet from the discussions here, there is an inherent assumption that groups are not allowed. This makes the specification hard to interpret for a CF convention neophyte like myself. Regards, Tim Patterson --------------------- Dr. Timothy Patterson Instrument Data Simulation Product Format Specification EUMETSAT Eumetsat-Allee 1 64295 Darmstadt Germany -----Original Message----- From: CF-metadata [mailto:[email protected]] On Behalf Of Charlie Zender Sent: Friday, September 19, 2014 6:20 PM To: CF Metadata Mail List Subject: [CF-metadata] CF-2.0 Convention discussion I like the idea of a Google Doc to consolidate the issue list. Whether it will prove unwieldy is hard to guess. A 3-month period for listing use-cases seems reasonable. It seems more CF-like to be use-case driven than to presume the entire netCDF4 data model will be adopted. This has the advantage of parsimony--only implement what is necessary. From a technical point-of-view, however, it is advantageous to know already what netCDF4 can and cannot easily do. In my view the intersection of important use-cases and netCDF4 capabilities is the "sweet spot" for CF-2.0. Once the smoke clears I may summarize use-cases for handling ensembles/replicants and for handling large integer numbers. These could raise the issues of having groups and 64-bit ints in CF-2.0. But first let's settle the framework for discussions. Best, Charlie -- Charlie Zender, Earth System Sci. & Computer Sci. University of California, Irvine 949-891-2429 )'( _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
