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.
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?
If the scalar approach is breaking the CF rules then I would prefer to go
back to the vector approach which is what I proposed in the
first email to this topic on April 2.
For reference attached are netCDF files for the Scalar and Vector alternative
and
corresponding text files.
Andrew
(*Note: I set the 'Conventions' global attribute temporarily to CF-1.5 in the
netCDF file
because the checker doesn't recognise CF-1.6 yet, only works up to 1.5.
The 'Conventions' attribute will be CF-1.6 in the final file.)
----- Original Message -----
From: "John Caron" <caron at unidata.ucar.edu>
To: "andrew walsh" <awalsh at metoc.gov.au>
Cc: <cf-metadata at cgd.ucar.edu>
Sent: Monday, April 30, 2012 10:46 PM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
> On 4/29/2012 5:33 PM, andrew walsh wrote:
>> Hi John,
>>
>> My responses inline below.
>>
>> Andrew
>>
>>
>> ----- Original Message ----- From: "John Caron" <caron at unidata.ucar.edu>
>> To: <cf-metadata at cgd.ucar.edu>
>> Sent: Saturday, April 28, 2012 2:39 AM
>> Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
>>
>>
>>> Hi Andrew:
>>>
>>> You can use a dimension=1 instead of a scalar.
>>
>> OK, you mean if one used the vector method.
>
> yes
>
>>
>>>
>>> But you cant use
>>>
>>> lat(lat)
>>> lon(lon)
>>> time(time)
>>>
>>> the correct usage in the single profile case would be:
>>>
>>> lat(profile)
>>> lon(profile)
>>> time(profile)
>>
>> So, do you mean in the vector method have this? (simpler I guess to
>> have common profile dimension = 1)
>
> yes, you cant use incorrect dimensions, even when they are all = 1.
>
>>
>> dimensions:
>> profile=1
>> pressure = 57
>>
>> variables:
>> lat(profile)
>> lon(profile)
>> time(profile)
>> pressure(pressure)
>> temperature(pressure)
>>
>> Instead of this?
>>
>> Dimensions:
>> time=1
>> lat=1
>> lon=1
>> pressure=57
>>
>> Variables:
>> time(time)
>> lat(lat)
>> lon(lon)
>> pressure(pressure)
>> temperature(pressure)
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: VectorCTD.txt
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120501/df4882b3/attachment-0002.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ScalarCTD.nc
Type: application/octet-stream
Size: 5508 bytes
Desc: not available
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120501/df4882b3/attachment-0002.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ScalarCTD.txt
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120501/df4882b3/attachment-0003.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VectorCTD.nc
Type: application/octet-stream
Size: 5568 bytes
Desc: not available
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20120501/df4882b3/attachment-0003.obj>
Received on Mon Apr 30 2012 - 20:40:22 BST
