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/.
#95: Development of CF 1.5 Data Model -----------------------------+---------------------------------------------- Reporter: markh | Owner: [email protected] Type: task | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by davidhassell): Hello, (I might not have written this if had seen Stephen's post first. But I didn't, so I did, so you might as well see it!) Global attributes apply to each data variable in the dataset, do they not? unless superceded locally by a data variable's attribute. Therefore CF- netCDF global attributes are an encoding convenience - they allow us to avoid adding them to every data variable in the dataset, thus reducing redundancy of information and dataset size (good things). So I think that there should be no logical distinction between global and data attributes in the data model. They're all just 'field attributes'. I also think that it's not the preserve of the data model to ensure that a CF-netCDF dataset written out is identical to one read in. So long as the logical content of the input and output datasets is the same then the data model has done its job, regardless, in fact, of the formats of the two datasets. As Bryan says, software built on the CF data model will make decisions on how to format its output within the confines of creating a CF compliant file. All the best, David -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:70> 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.
