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:

 I think this is where we are:

 (1)
 staus_flag and number_of_observations become a special type of
 standard_name, and become the standard name of the applicable ancillary
 variable.

 (2)
 these special standard_names are associated with ancillary variables that
 provide status or number of observations for two or more other data
 variables in the same data set.

 (3)
 these other data variables must include the "ancillary_variables"
 attribute set to the variable name of the relevant ancillary variable.


 Has converge of an approach to allow sharing of a status_flag or
 number_of_observation ancillary variable been reached ?


 One other question that comes to mind ...

 Is this syntax used only when an ancillary variable is associated with
 more than one data variable ?

 very respectfully,

 randy

-- 
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:33>
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.

Reply via email to