Hi Rosalyn, Thanks for the clarification. That leads me to another question though, if the *station_name *is defined as an aux co-ordinate, is it mandatory to have associated units with it? Can the units for the *station_name *variable be left blank? Is the *station_name *variable supposed to be monotonic?
Thanks, Ajay On Mon, May 12, 2014 at 5:22 AM, Rosalyn Hatcher <[email protected]>wrote: > Hi Ajay, > > In your netcdf file is *station_name* identified as an aux coordinate > variable by listing it in the *coordinates* attribute? > > There is a mistake in the H2 example (and others) where *station_name*should > be identified as a aux coord var on the > *coordinates* attribute for humidity > > I raised this and other defects in ticket 103 - > http://kitt.llnl.gov/trac/ticket/103 > > Hope this helps, > Regards, > Ros. > > On 08/05/14 21:38, Ajay Krishnan - NOAA Affiliate wrote: > > > Hi Everyone, > > Can anybody tell me the correct usage of the *cf_role* attribute? > > From my gathering, the *cf_role* attribute should only be attached to a > coordinated variable (See appendix > A<http://cfconventions.org/1.6.html#attribute-appendix> > ). > > But in the CF conventions document Example H.2., the *cf_role* is being > attached to the *station_name* variable. > > When we do this, the CF compliance checker gives out an INFO message > stating that the *cf_role *attribute is being used in a non-standard way. > > Any inputs? > > Thanks, > Ajay > > > > _______________________________________________ > CF-metadata mailing > [email protected]http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > > -- > Rosalyn Hatcher > NCAS Computational Modelling Services > Dept. of Meteorology, University of Reading, > Earley Gate, Reading. RG6 6BB > Email: [email protected] Tel: +44 (0) 118 378 5429 > >
_______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
