Hi John,
Thanks, I think we have reached a near conclusion to our discussions
about how best to encode a 'single' profile CTD cast following CF standard v1.6.
This not been easy as CF allows more than 1 way to do it and the standard is
large.
Thanks also Jonathon, Roy, Nan, Jim, Upendra, Thierry, Karl for your valuable
inputs,
hope I haven't missed anyone else!
Jonathon, thanks for clarifying that 'axis' attribute will be allowed on
'auxilliary coordinate variables', yes the standard was confusing.
To summarise I will use a 'Scalar' method for simplicity, noting that
the 'Vector' method is also acceptable.
Attached for reference is the netCDF file and CDL (.txt) of the same.
Convention attribute has been updated to 'CF-1.6'
Andrew
----- Original Message -----
From: "John Caron" <caron at unidata.ucar.edu>
To: <cf-metadata at cgd.ucar.edu>
Sent: Wednesday, May 02, 2012 2:21 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
> 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
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ScalarCTD2.txt
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120502/a24d0d69/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ScalarCTD2.nc
Type: application/octet-stream
Size: 5508 bytes
Desc: not available
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120502/a24d0d69/attachment.obj>
Received on Tue May 01 2012 - 18:34:38 BST
