Dear Jonathan, et al., > In particular, if no-one thinks this is a material change to the > standard, it could be made with a defect ticket.
That sounds reasonable to me. From a backwards compatibility view point, it sounds like any existing software built on the common netCDF libraries will already correctly interpret these attributes on coordinates ... is that a fair assumption? David ---- Original message from Jonathan Gregory (06PM 12 Apr 12) > Date: Thu, 12 Apr 2012 18:27:34 +0100 > From: Jonathan Gregory <[email protected]> > To: [email protected] > User-Agent: Mutt/1.5.21 (2010-09-15) > Subject: [CF-metadata] Using add_offset & scale_factor with coordinate > variables > > Dear Brian > > > Jonathan, are you thinking that CF disallows packing of coordinates because > > we neglected to explicitly include them in Table A.1? I think this was > > just an oversight. I don't have any recollection that we intended to > > disallow packing coordinates, and I don't find anything in the convention > > document itself that leads to this conclusion (although I'm not as familiar > > with it as I used to be :) > > I have a recollection that we deliberately decided to disallow them, and it > was not just an oversight. However, if you can't remember, and no-one can > think of a reason why it would be a problem, I don't object. In particular, > if no-one thinks this is a material change to the standard, it could be made > with a defect ticket. > > Best wishes > > Jonathan > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata -- David Hassell National Centre for Atmospheric Science (NCAS) Department of Meteorology, University of Reading, Earley Gate, PO Box 243, Reading RG6 6BB, U.K. Tel : 0118 3785613 Fax : 0118 3788316 E-mail: [email protected] _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
