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 jonathan):

 Dear Randy

 Thank you for the helpful summary. I think this is a reasonable approach
 i.e. add `status_flag` and `number_of_observations` as standard names of
 dimensionless quantities. Regarding these, I would note:

   * Although the standard name of the ancillary variable will no longer
 identify the quantity it belongs to, the `ancillary_variables` attribute
 serves to link them.

   * So far, we have not abolished any existing facility of CF. We do not
 need to withdraw `status_flag` or `number_of_observations` as standard
 names. We could deprecate them i.e. recommend against using them. In that
 case the CF checker would give a warning (rather than an error) if they
 were used in a file conforming to the version of CF in which this change
 was made. I suggest that this option should be considered.

 A separate ticket can deal with any proposal for `standard_error` and
 `detection_minimum`, as you suggest.

 Cheers

 Jonathan

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