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

#86: Allow coordinate variables to be scaled integers
---------------------------------------+------------------------------------
  Reporter:  [email protected]  |       Owner:  
[email protected]         
      Type:  defect                    |      Status:  new                      
             
  Priority:  medium                    |   Milestone:                           
             
 Component:  cf-conventions            |     Version:                           
             
Resolution:                            |    Keywords:  coordinate variables, 
scaled inetegers
---------------------------------------+------------------------------------
Comment (by [email protected]):

 Folks:

 Almost a month has elapsed since the last correspondence.  The subject of
 this trac item captures the intent of this change "Allow coordinate
 variables to be scaled integers".

 To update the CF metadata conventions standard document requires changing
 a two rows in Table A.1 Attributes in Appendix A.

 (1) In the "add_offset" row, the "Use" column needs to change from "D" to
 "C, D"

 (2) In the "scale_factor" row, the "Use" column needs to change from "D"
 to "C, D"

 In addition, the following statement will be added to the "Description"
 cell in Table A.1 Attributes for attributes scale_factor and add_offset.

 "The use of packed coordinate variables is allowed, but not preferred to
 primarily support use cases where dataset sizing constraints exist."

 I support this enhancement. Does the conventions committee support this
 enhancement ?


 very respectfully,

 randy

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