Hi. If someone chooses the scalar approach, isn't it necessary to declare the coordinates via the coordinates attribute on the measurement variables?
Grace and peace, Jim Jim Biard Research Scholar Cooperative Institute for Climate and Satellites Remote Sensing and Applications Division National Climatic Data Center 151 Patton Ave, Asheville, NC 28801-5001 [email protected] 828-271-4900 On May 1, 2012, at 12:21 PM, John Caron wrote: > On 4/30/2012 8:40 PM, andrew walsh wrote: >> Hi John and CF-Metadata list, >> >> Based on your earlier advice I decided using the Scalar way to represent >> the coordinate lat, long and time rather than Vector way i.e lat(lat0, >> lon(lon), time(time) >> mainly for reason of simplicity. > > the correct other choice is lat(profile), lon(profile), time(profile). not > sure if you caught that. > > the scalar choice is fine for 1 profile per file. the other is used to store > multiple profiles in one file. > >> >> I have run the Scalar sample through the BADC netCDF checker (*Note) >> at http://titania.badc.rl.ac.uk/cgi-bin/cf-checker.pl and I now get this >> error >> on each of the lat, lon, time variables: >> >> ERROR (4): Axis attribute is not allowed for auxillary coordinate variables. >> I don't get this error with the Vector approach. It looks like the checker >> thinks >> my scalar lat, lon, time are 'auxilliary coordinate variables' and axis >> attributes >> are not allowed on these. Is the checker interpreting things correctly? > > i think we recently clarified that axis is acceptable on auxiliary > coordinates. OTOH, its unecessary, as long as you follow the other rules for > identifying coordinates (chapter 4). > > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
_______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
