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
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
: 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 peace,
Jim
Jim
On 4/29/2012 5:33 PM, andrew walsh wrote:
Hi John,
My responses inline below.
Andrew
- Original Message - From: John Caron ca...@unidata.ucar.edu
To: cf-metadata@cgd.ucar.edu
Sent: Saturday, April 28, 2012 2:39 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions
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
@cgd.ucar.edu mailto: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
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 ca...@unidata.ucar.edu
To: cf-metadata@cgd.ucar.edu
Sent: Saturday, April 28, 2012 2:39 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF
Hi John,
My responses inline below.
Andrew
- Original Message -
From: John Caron ca...@unidata.ucar.edu
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
-
From: John Caron ca...@unidata.ucar.edu
To: andrew walsh awa...@metoc.gov.au
Cc: cf-metadata@cgd.ucar.edu; Luke Callcut l...@metoc.gov.au;
g...@metoc.gov.au
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
To: andrew walsh awa...@metoc.gov.au
Cc: cf-metadata@cgd.ucar.edu; Luke Callcut l...@metoc.gov.au;
g...@metoc.gov.au
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: andrew walsh awa...@metoc.gov.au
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
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 when we do I can send you a file
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. An
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 advice
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 required
; 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 how it is going to encode
data, including single CTD casts, in CF
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's a
*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 issue raised in my response to Jim which was based on the tunnel vision
of having pressure
*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 issue raised in my response to Jim which was
based on the tunnel vision of having
...@metoc.gov.au ;
cf-metadata@cgd.ucar.edu mailto:cf-metadata@cgd.ucar.edu ;
sdn2-t...@seadatanet.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
Subject: TR: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Hello Roy and All,
I am involved in Argo data-management, OceanSITES and the MyOcean EU
project.
These 3 projects are intensive users of NetCDF CTD data files.
Within these communities :
ยท The natural vertical
/down due the motion of the CTD instrument.
- Original Message -
From: Jonathan Gregory j.m.greg...@reading.ac.uk
To: cf-metadata@cgd.ucar.edu
Sent: Wednesday, April 04, 2012 12:47 AM
Subject: Re: [CF-metadata] Ocean CTD data following CF Conventions v1.6
Dear Andrew and Nan
If your
, 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
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
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,
...@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 how it is going to encode data,
including single CTD casts, in CF-compliant NetCDF and so I think
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.
Regarding
27 matches
Mail list logo
