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 ngalbraith): I agree with Martin - 'sea_water_potential_temperature' could easily have an ancillary variable called 'sea_water_temperature number_of_observations.' (I'd tend to name these after observed variables and carry them over to calculated ones, but that should be left to the data writer.) If we wanted to require that the NOBS variable name included the 'target' data variable name (e.g. sea_water_potential_temperature had to have a NOBS ancillary variable called 'sea_water_potential_temperature number_of_observations' or 'sea_water_temperature sea_water_potential_temperature number_of_observations' we wouldn't need to bother with the ancillary variable attribute at all. I'm in favor of exploiting the flexibility this attribute gives us. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:11> 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.
