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

#95: Development of CF 1.5 Data Model
-----------------------------+----------------------------------------------
  Reporter:  markh           |       Owner:  [email protected]
      Type:  task            |      Status:  new                          
  Priority:  medium          |   Milestone:                               
 Component:  cf-conventions  |     Version:                               
Resolution:                  |    Keywords:                               
-----------------------------+----------------------------------------------
Comment (by markh):

 Replying to [comment:20 jonathan]:
 > I think we may have made a mistake in the last bit. I think it should
 say "CF requires there to be auxiliary coordinate constructs of latitude
 and longitude if there is two-dimensional horizontal variation but the
 horizontal coordinates are not latitude and longitude", not "recommends".
 I believe that's what the start of sect 5 means, but it is obscurely
 stated. Steve Hankin and I have separately been discussing ways to
 rephrase it which could be proposed as a defect ticket.

 I do not think this should feature in the data model, I do not think it is
 required.

 While I can see the NetCDF interoperability benefits which come from
 software which looks for latitude and longitude coordiantes, I think this
 is a NetCDF implementation benefit which clutters the data model
 unnecessarily.

 CF model datasets may be fully defined by coordinates and transforms
 (coordinate reference systems) such that extra latitude and longitude
 coordinates are not required, they are inferrable from the defined
 properties.

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