Dear Roy I understand the need but I tend to think this would not be an appropriate use of the Conventions attribute, which is a general netCDF attribute, not specific to CF, and refers to files. I do appreciate the logical similarity but I would have thought it better to define something more specific in CF for this purpose.
If this is a need which several users have and is required for exchange of data, then it is reasonable to propose to add something to CF. Since it's an extra piece of information referring to flags, maybe an attribute such as flag_convention_name would work? We could make it a requirement that this attribute was allowed only if the variable had flag_meanings as well, to prevent its being used as a substitute for spelling out what the flags mean (as is necessary for the file to be self-describing). Best wishes Jonathan ----- Forwarded message from "Lowry, Roy K." <r...@bodc.ac.uk> ----- > From: "Lowry, Roy K." <r...@bodc.ac.uk> > To: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> > Date: Wed, 23 Jan 2013 08:20:49 +0000 > CC: Michele FICHAUT <michele.fich...@ifremer.fr> > Subject: [CF-metadata] Usage of the 'Conventions' attribute > > Dear All, > > Currently, the 'Conventions' attribute is restricted to be a global > attribute. There is currently a requirement to label multiple QC flag > variables following different conventions with their source convention and > having the 'Conventions' attribute as a variable attribute for these > non-co-ordinate variables would seem a convenient and consistent mechanism. > Is there any support for or objections to this suggestion? > > Cheers, Roy. > > Please note that I now work part-time from Tuesday to Thursday. E-mail > response on other days is possible but not guaranteed! > > > > > ________________________________ > This message (and any attachments) is for the recipient only. NERC is subject > to the Freedom of Information Act 2000 and the contents of this email and any > reply you make may be disclosed by NERC unless it is exempt from release > under the Act. Any material supplied to NERC may be stored in an electronic > records management system. > _______________________________________________ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata ----- End forwarded message ----- _______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
