ethod 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"
To:
Sent
du
Sent: Wednesday, May 02, 2012 4:51 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
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
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
Nation
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 choi
Dear Andrew
> 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
-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"
To: "andrew walsh"
Cc:
Sent: Monday, April 30, 2012 10:46 PM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conve
to:cf-metadata@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)
; - Original Message - From: "John Caron"
>> To:
>> 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 dim
On 4/29/2012 5:33 PM, andrew walsh wrote:
Hi John,
My responses inline below.
Andrew
- Original Message - From: "John Caron"
To:
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 d
Hi John,
My responses inline below.
Andrew
- Original Message -
From: "John Caron"
To:
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 m
quot;John Caron"
To: "andrew walsh"
Cc: ; "Luke Callcut" ;
Sent: Thursday, April 26, 2012 10:48 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi andrew:
The file you sent (20110818T001140Z_M_HI504BEN.nc) appears to be a
single profile.
s,
Andrew
- Original Message -
From: "John Caron"
To: "andrew walsh"
Cc: ; "Luke Callcut" ;
Sent: Thursday, April 26, 2012 10:48 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi andrew:
The file you sent (20110818T001140Z_M
ew walsh"
Sent: Thursday, April 05, 2012 10:44 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
ok
On 4/4/2012 6:42 PM, andrew walsh wrote:
Hi John,
Thank for your offer to check a sample netCDF CTD data file. At
moment we don't have
some real .nc file but wh
AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
ok
On 4/4/2012 6:42 PM, andrew walsh wrote:
Hi John,
Thank for your offer to check a sample netCDF CTD data file. At moment we
don't have
some real .nc file but when we do I can send you a file for checking
55 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi all:
Lets see, I havent followed the entire conversation, but:
1) Andrew if you can send me a sample file (not just the CDL) I can check if it
works in the CDM with the new 1.6 conventions, and maybe give you some a
Dear Andrew
Thanks for your email.
> 1) What distinguishes an 'auxilliary coordinate variable' from a plain old
> 'coordinate variable'?
A plain old coordinate variable is as defined by the Unidata netCDF user's
guide. It is 1D, monotonic, and its name is the same as the name of its
dimension. A
, Glider and XBT
instruments.
Regards,
Andrew
- Original Message -
From: Upendra Dadi
To: cf-metadata@cgd.ucar.edu
Sent: Wednesday, April 04, 2012 4:48 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi,
I think Jim is talking about NCML (virtual
PS: To clarify, the netCDF CTD data we produce will have monotonic pressures.
The raw data we get in may go up/down due the motion of the CTD instrument.
- Original Message -
From: "Jonathan Gregory"
To:
Sent: Wednesday, April 04, 2012 12:47 AM
Subject: Re: [CF-metadata]
: "Thierry Carval"
To: "'Lowry, Roy K.'"
Cc: "'Luke Callcut'" ; ; "'Upendra
Dadi'" ; ; ;
"'andrew walsh'"
Sent: Wednesday, April 04, 2012 4:31 AM
Subject: TR: [CF-metadata] Ocean CTD data following CF Conven
dra Dadi <mailto:upendra.d...@noaa.gov> ; andrew
walsh <mailto:awa...@metoc.gov.au>
*Cc:* Luke Callcut <mailto:l...@metoc.gov.au> ;
cf-metadata@cgd.ucar.edu <mailto:cf-metadata@cgd.ucar.edu> ;
sdn2-t...@seadatanet.org <mailto:sdn2-t..
atanet.org <mailto:sdn2-t...@seadatanet.org>
*Sent:* Tuesday, April 03, 2012 9:31 AM
*Subject:* RE: [CF-metadata] Ocean CTD data following CF
Conventions v1.6
Hi Upendra,
I like the idea of a station dimension. It goes a long way
to resolving the
w walsh
> *Cc:* Luke Callcut ; cf-metadata@cgd.ucar.edu ;
> sdn2-t...@seadatanet.org
> *Sent:* Tuesday, April 03, 2012 9:31 AM
> *Subject:* RE: [CF-metadata] Ocean CTD data following CF Conventions v1.6
>
> Hi Upendra,
>
> I like the idea of a station dimension. It goes
Dear all,
I second Jonathan's suggestion to treat lon, lat, and time as scalars
pointed to by the coordinates attribute, and to only keep "pressure" as
a true coordinate. It seems neater to me. In CMIP5, we've required all
size-1 dimensions of this kind be treated in this way.
Karl
On 4/3
Dear Andrew and Nan
> If your pressure isn't monotonic, and so can't be a coordinate
> variable, I don't know
> whether it's preferable to demote ALL the coordinates to auxiliary
> coordinate variable
> status,
> TEMPERATURE: coordinates = "TIME,PRESSURE,LATITUDE,LONGITUDE" ;
I don't think there'
r, millibar, decibar, atmosphere (atm), pascal (Pa), and hPa.
...
..."ΒΆ
Regards,
Andrew
- Original Message - From: Lowry, Roy K.
To: andrew walsh
Cc: Jim Biard ; Upendra Dadi ; cf-metadata@cgd.ucar.edu ; Luke Callcut
; g...@metoc.gov.au ; sdn2-t...@seadatanet.org
Sent: Tuesd
To: andrew walsh
Cc: cf-metadata@cgd.ucar.edu; sdn2-t...@seadatanet.org; g...@metoc.gov.au; Luke
Callcut; Upendra Dadi
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi again,
The reason that I prefer depth to pressure as the dimension for CTD is that the
information re
, Roy K.
Cc: Jim Biard; Upendra Dadi; cf-metadata@cgd.ucar.edu; Luke Callcut;
g...@metoc.gov.au; sdn2-t...@seadatanet.org
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi Roy/All,
Agree totally it would be good to get this CTD netCDF done in an interoperable
way.
Rega
: andrew walsh
Cc: Jim Biard ; Upendra Dadi ; cf-metadata@cgd.ucar.edu ; Luke Callcut ;
g...@metoc.gov.au ; sdn2-t...@seadatanet.org
Sent: Tuesday, April 03, 2012 2:16 PM
Subject: RE: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hi Andrew,
SeaDataNet will very soon be considering
Hi Andrew,
Either way it should be okay as far as CF compliance is concerned. But
the dimensions - latitude, longitude and time are not really required. If
it is required to indicate that there is only one station(profile) in the
file, there could be a dimension for number of stations instead, w
Hi.
Here's my best understanding (which could be flawed, so I look forward to
finding out if I have missed something). Assuming that your time,
latitude, and longitude are all proper coordinate variables (no fill
values), either choice for the shape of your salinity variable works. If
you use th
Hi CF list,
We are working on coding up some 1000's netCDF files off CTD
instruments and want to make usre we are following the
latest netCDF conventions (v1.6) OK. As background the CTD records
a profile pressure, temperature and salinity.
Here is a summarised CDL version (not all attributes+va
31 matches
Mail list logo
