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/.

#104: Clarify the interpretation of scalar coordinate variables
-----------------------------+----------------------------------------------
  Reporter:  jonathan        |       Owner:  [email protected]
      Type:  enhancement     |      Status:  new                          
  Priority:  medium          |   Milestone:                               
 Component:  cf-conventions  |     Version:                               
Resolution:                  |    Keywords:                               
-----------------------------+----------------------------------------------
Comment (by jonathan):

 Dear all

 Thank you for your thoughtful comments, Alison.

 Following the above useful discussions with John and Steve, and further
 email discussions, I'd like to add one more change to this proposal:

 In Section 1.2, change the definition

   scalar coordinate variable: A scalar variable that contains coordinate
 data. Functionally equivalent to either a size one coordinate variable or
 a size one auxiliary coordinate variable.

 to

   scalar coordinate variable. A scalar variable (i.e. one with no
 dimensions) that contains coordinate data. Depending on context, it may be
 functionally equivalent either to a size-one coordinate variable (Section
 5.7) or to a size-one auxiliary coordinate variable (Sections 6.1 and
 9.2).

 This is in order to define what "scalar" means, and to provide pointers to
 the relevant parts of the document where the role of scalar coordinate
 variables is clarified.

 It's become clear from these discussions that it would be better to
 indicate the role of scalar coordinate variables explicitly. I will make a
 proposal in another ticket to define new `cf_role` values for that
 purpose. However, if agreed, that wouldn't be implemented until CF 1.7 or
 1.8. At the moment we are discussing the interpretation and the data model
 of CF 1.5. None of the changes proposed in this ticket intend to change
 anything about CF-netCDF; they are concerned only with clarifying what CF
 1.5 means. I don't want to make a proposal to modify CF metadata in this
 ticket, because I fear that it would delay the conclusion of the data
 model discussion, which has already been in progress for a couple of years
 (beginning in ticket 68)!

 If this ticket is agreed, we can go back to continuing the data model
 discussion in ticket 98. Following other comments by John, we will there
 propose inserting some text about the correspondence between
 dimension/auxiliary and independent/dependent coordinates in the data
 model.

 Cheers

 Jonathan

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