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

#100: Clarifications to the preamble of section 5
-----------------------------+----------------------------------------------
  Reporter:  jonathan        |       Owner:  [email protected]
      Type:  defect          |      Status:  new                          
  Priority:  medium          |   Milestone:                               
 Component:  cf-conventions  |     Version:                               
Resolution:                  |    Keywords:                               
-----------------------------+----------------------------------------------
Comment (by Dave.Allured):

 Jonathan,

 Thanks to you and Steve for working on clarification.  In the current
 document (CF 1.6), I have trouble understanding the intent of section 5,
 paragraph 7:

   If the coordinate variables for a horizontal grid are not longitude and
 latitude, it is recommended that they be supplied in addition to the
 required coordinates.  For example, the Cartesian coordinates of a map
 projection should be supplied as coordinate variables in addition to the
 required two-dimensional latitude and longitude variables that are
 identified via the coordinates attribute ...

 If the required two-dimensional latitude and longitude variables are
 present and correctly identified, are the one-dimensional Cartesian
 coordinates also required, or optional?  Either way, could you please add
 an explicit statement about this?

 In two different use cases that I have encountered, when the data variable
 is a single horizontal grid, the Cartesian coordinates will increase file
 size by roughly 67%.  I would favor making the Cartesian coordinates
 explicitly optional.  Thanks for your consideration.

 --Dave

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