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 [email protected]): Folks: The most recent approach to providing a CF compliant construct for allowing data variables to share ancillary variables discussed in this ticket elevates number_of_observations and status_flag to standard_names. One of these standard_names are assigned to the applicable ancillary variable, and the multiple data variables that have the designated relationship with the ancillary variable indicate so with an ancillary_variables attribute assigned to the variable name of the shared ancillary variable. The most recent question surrounding the most recent approach to providing a CF compliant construct for allowing data variables to share ancillary variables revolve around whether all four current standard_name modifiers current defined in appendix C (detection_minimum, number_of_observations, standard_error, & status_flag) can make use of this extension. Only the standard_name modifiers with dimensionless units (number_of_observations, states_flag) make sense because the other two standard_name modifiers, detection_minimum and standard_error, need to have the same units as the data variable. For multiple data variables needing to share the same ancillary variable, it would be overly restrictive to require they have the same units. Has consensus been reached. ? very respectfully, randy -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:36> 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.
