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/.
#74: Allow sharing of ancillary variables among multiple data variables ---------------------------------------+------------------------------------ Reporter: [email protected] | Owner: [email protected] Type: enhancement | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: "ancillary data" "standard name modifiers" ---------------------------------------+------------------------------------ Comment (by biard): Randy, Sorry it's taken so long to post on this again. I suggest that instead of modifying the second paragraph of section 3.3, we introduce a paragraph before the last sentence of the section that reads: In the special case where more than one data variable references an ancillary data variable (see Section 3.4, "Ancillary Data") that contains a derived quantity (such as number of observations) that applies to all of the referencing data variables, and where the referencing data variables do not all share the same standard name, the standard_name attribute for the ancillary data variable is comprised of a blank-separated list of the unique set of standard names from the referencing data variables followed by the common standard name modifier. Another way to resolve this question is to take an approach that is closer to Nan's suggestion. We could specify a special "placeholder" standard name - say, "?reference?", that would stand in for a specific standard name in the ancillary data variables standard_name attribute. The standard name table would have an entry for this new standard name that would explain that it is to be replaced by the standard name of a referencing data variable. This would allow us to keep the syntax of the standard_name attribute simple, avoid the headless standard name modifier problem, make it obvious that the contents of the ancillary data variable are applicable to one or more referencing data variables, and (eventually) lead to less confusion on the part of users than I think the multiple standard names approach may produce. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:21> 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.
