-boun...@cgd.ucar.edu] On
Behalf Of Christiane Textor [christiane.tex...@lsce.ipsl.fr]
Sent: 30 April 2009 17:13
To: Lowry, Roy K; Jonathan Gregory
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] new standard name request for pH
Dear all,
I am not an expert ocean acidification at all
advances on his
conventions obviously need consideration.
Cheers, Roy.
From: Christiane Textor [christiane.tex...@lsce.ipsl.fr]
Sent: 30 April 2009 20:41
To: Lowry, Roy K; Lowry, Roy K
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] new standard name
of the effects errors of that magnitude
have on deep ocean carbon budget calculations.
Cheers, Roy.
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
[mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of John Graybeal
Sent: 02 May 2009 01:28
To: CF Metadata List; Lowry, Roy K
Dear All,
During an exercise with Alison mapping the CF Standard Names to a units
vocabulary in the BODC vocabulary server I noticed that the units for salinity
were '1.00E-03', i.e. parts per thousand. My understanding in that since the
introduction of the Practical Salinity Scale that
Hi Bryan,
Steve's query presents something of a Standard Names crossroads. 'Chlorophyll'
is a very generic word covering a group of pigments (chlorophyll-a,
chlorophyll-b, divinyl chlorophyll-a, etc.) that some analytical techniques can
resolve whilst others cannot. 'Chlorophyll' is also a
[mailto:bryan.lawre...@stfc.ac.uk]
Sent: 29 July 2009 09:56
To: Lowry, Roy K
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Standard name definitions ... are these formal or
flexible
Hi Roy
Glad that it looks like Steve's specfiic problem isn't a problem given the name
change and definition you
Hello Martin,
There is another possible solution to your problem, which we are looking at for
dealing with a data source flag to be used with the GEBCO bathymetric grid.
This is to put a URI base into an attribute that when concatenated with a flag
values gives the flag definition from a
/
Cheers, Roy.
-Original Message-
From: John Caron [mailto:ca...@unidata.ucar.edu]
Sent: 27 October 2009 13:17
To: Lowry, Roy K
Cc: martin.juc...@stfc.ac.uk; cf-metadata@cgd.ucar.edu; Weatherall, Pauline
Subject: Re: [CF-metadata] Dealing with large numbers of flag values innetcdf cf
.
From: Richard Signell [rsign...@gmail.com]
Sent: 15 November 2009 15:00
To: Lowry, Roy K
Cc: ngalbra...@whoi.edu; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] CF point observation Conventions ready for review
Roy,
I come from this community also
measurement at a single
x,y,z,t. Is there a single point in your feature types? Why assign the term
point to a set of measurements with single x, y, and z and progressing t, as
opposed to a set of measurements with single x, y, t values but varying z?
Cheers -
Nan
Lowry, Roy K wrote:
..
The feature
Dear All,
I think a new Standard Name 'sea_floor_depth_below_sea_surface' is what's
needed here. My definition for this would be 'The vertical distance between
the sea surface and the seabed at a given point in space and at a given instant
in time or averaged over a time interval that is
into a wall.
Cheers, Roy.
-Original Message-
From: Jeff deLaBeaujardiere [mailto:jeff.delabeaujardi...@noaa.gov]
Sent: 28 January 2010 14:06
To: Lowry, Roy K
Cc: John Graybeal; cf-metadata@cgd.ucar.edu; Mike Garcia
Subject: Re: [CF-metadata] seeking CF name for total water column height
I
Dear Jonathan,
The alias structure has developed into a deprecation mechanism and some of the
more recent corrections have changed the meanings of the terms, so that the
term and its alias are no longer synonyms. Using the alias mechanism to
establish synonyms between undeprecated terms
Hello Nan,
I was arguing at the start of this thread that an instantaneous single-beam
echosounder measurement is the so close to being the same thing as a BPR
measurement in tidal mode with waves filtered out (ever looked at echosounder
data from an anchored ship?) that they should be called
Hello Jonathan,
I have concerns about having separate names for river, lake and sea. If you
have them for height, then the logic would extend to temperature. I have
temperature data from a boat that started in the North Sea, went up the Humber
and then up to the navigable limit of the
To: Lowry, Roy K
Cc: cf-metadata@cgd.ucar.edu
Subject: RE: [CF-metadata] water level with/without datum
Hi Roy,
Would simply inventing an artificial new term to represent
sea+lakes+rivers be an option here? Presumably, back in the day, there
was no word for a land-locked body of fresh water so
Hi Nan,
Using unqualified 'water' to signify water within a water body works for me.
Cheers, Roy.
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
[mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Nan Galbraith
Sent: 25 February 2010 16:47
To: Jonathan Gregory
Cc: John
Dear All,
The 'fast track' approach being discussed has promise and is pretty much in
line with the ISO vocabulary model (in which terms have proposed, accepted,
deprecated or deleted) used in resources like the GEMET thesaurus. However,
there are important details to consider, such as version
Hello Jonathan,
The term 'statistics' has a slightly different meaning for wave data.
Essentially, what wave instrumentation does is record vertical displacement of
the sea surface at very high frequency for a period of say ten minutes.
Spectral analysis techniques are then used to derive
Hello Andrew and Jonathan,
First, I think this discussion is heading towards reasonable compromise
avoiding my concerns of a massive proliferation in cell methods and the pitfall
of concepts that are explainable in the context of their parameter, but
meaningless in isolation (e.g. explaining
Dear All,
I'd just like to reinforce John's last point that the semantics of 'instrument'
and 'platform' are becoming blurred in these discussions. From my perspective
as one who has to map to CF datasets I would prefer it if the semantics of
terms used in Standard Names had a universally
Dear All,
As others have said, I think this debate is irrelevant as there should be no
need for string timestamps in NetCDF. Providing a Standard Name only encourages
what I consider to be bad practice.
Cheers, Roy.
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
Hi John,
ISO-8601 allows timestamps to any resolution from year to millisecond, so 2010,
2010-10, 2010-10-20 are all valid so the string can be any length from 4 to 27
(e.g. 2010-10-20T14:53:00.000Z-15), unless restricted through an 8601 profile
(as many communities do)
Cheers, Roy.
, it's a pain to represent
variable length strings in NetCDF, but there is a maximum length for
ISO8601 strings.)
Hope this helps,
Jon
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
[mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Lowry, Roy K
Sent: 20 October 2010 10:00
Hi Jon,
Full ISO8601 does carry time zone expressed in hours relative to UT in the
syntax Zx where x is the offset from Zulu at the right-hand end of the string.
Cheers, Roy.
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
[mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf
...@nsidc.org]
Sent: 22 October 2010 17:32
To: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Interpretation of unspecified time zone (was: New
standard names for satellite obs data (timeas ISO strings))
Hi,
On Fri, 22 Oct 2010, Lowry, Roy K wrote:
I wonder how many existing CF data files would have
Hi Alison,
If a community uses the term 'diameter' then I would stick with that and in our
experience with both sediment grain-size and aerosol size spectra 'diameter' is
the word exclusively used.
Cheers, Roy.
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu
Yes, that's my understanding. Cheers, Roy.
From: Lauret Olivier [mailto:olau...@cls.fr]
Sent: 03 December 2010 10:22
To: Lowry, Roy K.; Jonathan Gregory
Cc: Laurence Crosnier; cf-metadata@cgd.ucar.edu; Cristina Tronconi; Bruce
Hackett; o.go...@met.no; Thomas LOUBRIEU; Lia Santoleri; Philippe
Hi Benno,
That's a pretty thorough overview of the current position. One minor point is
that the URIs you give from my system serve version 9 - not the current
version. Replace the '9' by 'current' to get the latest version e.g.
http://vocab.ndg.nerc.ac.uk/list/P071/9
/16/CFSN0023
http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-ta
ble/16/cf-standard-name-table.html#air_temperature plus:
http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-ta
ble/16/cf-standard-name-table.xml
Cheers,
Dom
On 14/12/10 08:18, Lowry, Roy K
Hi Nan,
Let's consider how you're moored instrument data are mapped into NetCDF. If a
given parameter is stored as a 2-D array with time as one dimension and
instrument depth as the other then I would describe the data in that array as a
'profile series'. If they are stored as a set of 1-D
Hi Miles,
Should there be anything in the Standard Name to specify the wavelengths of
light detected in the measurement e.g.
luminous_intensity_of_shortwave_radiation_in air?
Cheers, Roy.
From: cf-metadata-boun...@cgd.ucar.edu
Hi Miles,
I would confirm with somebody who undestands the data before making any
decisions.
Cheers, Roy.
From: Miles Jordan [miles.jor...@aad.gov.au]
Sent: 07 January 2011 12:07
To: Lowry, Roy K.
Cc: Jonathan Gregory; cf-metadata@cgd.ucar.edu
Subject
measurement of
the intensity of visible light that passes through or is emitted from a given
area'. Anyone anything better?
Cheers, Roy.
-Original Message-
From: Miles Jordan [mailto:miles.jor...@aad.gov.au]
Sent: 11 January 2011 23:56
To: Lowry, Roy K.
Cc: Jonathan Gregory; cf-metadata
January 2011 02:23
To: Lowry, Roy K.
Cc: Miles Jordan; cf-metadata@cgd.ucar.edu; Jonathan Gregory
Subject: Re: [CF-metadata] Ambient light [Sec=Unclassified]
Is ''A photometric measurement of' a critical part of the definition? I can
imagine another magical technology that measures the intensity
Hi Martin,
There are two Standard Names 'downwelling_shortwave_flux_in_air' and
'downwelling_longwave_flux_in_air'. Do either of these fit your data. I have
associated the former with downwelling irradiance data from PAR
cosine-collector light meters.
Cheers, Roy.
-Original
Hi Karl,
Christina's problem is because her usage of standard name modifier is changing
the canonical units from those of the unmodified Standard Name. Only solutions
I can see are either to omit the Standard Name from this channel or set up a
new Standard Name for raw chorophyll as counts.
Dear Christina,
As this debate unfolds I am coming to the realisation that there might be a
significant difference between what you mean by 'chlorophyll count' (the
unmodified reading from a fluorometer analogue-to-digital converter that is a
function of chlorophyll concentration) and what CF
Hi Martin,
' It's only replacing an underescore by a blank anyhow ;-)'
This isn't strictly true. As the semantics infrastructure stands at the moment
the deprecation procedure is to label the deprecated Standard Name as an
'alias' with another Standard Name specified as its replacement.
I
Dear All,
This debate between Chris and Benno hinges upon how one determines the sampling
interval for a time series. Benno depends upon semantics encoded in the units
of measure field - something I have done in the past although I am now
convinced that it is not best practice. Chris
Hi John,
We label Units of Measure with a URI (e.g. SDN:P061::ULAA represents metres),
which represents a term in the P061 vocabulary
(http://vocab.ndg.nerc.ac.uk/P061/list/current). The vocab (born in the late
70s) is a work of pragmatism that contains a mixture of 'dimensional units'
plus
Hello Justin/Jonathan,
To me, the term or concept 'bathymetry' is the spatial variation of seafloor
depth and should only be applied to a grouping of depth measurements with
associated co-ordinate variables and not to just a depth parameter.
Cheers, Roy.
-Original Message-
From:
Hello Jonathan,
Paul's neutral density definition looked OK to me, although I'm not a physical
oceanographer. If it helps I used
http://oceanworld.tamu.edu/resources/ocng_textbook/chapter06/chapter06_05.htm
As an aid to checking it out.
Cheers, Roy.
-Original Message-
From:
Dear Uwe,
It exists. A copy of the Standard Names is served through the NERC Vocabulary
Server (http://www.bodc.ac.uk/products/web_services/vocab/). The references to
the Standard Names list are:
Live terms: http://vocab.ndg.nerc.ac.uk/list/P071/current/
Deprecated terms:
Dear All,
I think the point we're missing here is that the existing salinity Standard
Name is a much broader term than the TEOS-10 recommendations, covering true
practical salinity from conductivity measurements, other types of salinity
measurement and salinity computed by a whole host of
was definitely not
Practical Salinity.
With best wishes,
Trevor
-Original Message-
From: Lowry, Roy K. [mailto:r...@bodc.ac.uk]
Sent: Friday, 22 July 2011 7:10 AM
To: McDougall, Trevor (CMAR, Hobart); ngalbra...@whoi.edu;
CF-metadata@cgd.ucar.edu; Durack, Paul (CMAR, Hobart
Hi Nan,
Encoding what I would regard as usage metadata into ancilliary variables is one
solution, but I would much rather see a formalised metadata model for doing
this. As you say a standard way of doing this is long overdue. My hope is that
SeadataNet II starting later this year will take
metadata.
Cheers, Roy.
From: Nan Galbraith [ngalbra...@whoi.edu]
Sent: 05 August 2011 16:30
To: Lowry, Roy K.; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] per-variable metadata?
Hi Roy and all -
Do you see a possible place for this metadata in a more
structured
of internet access becomes an
issue then we need to look at URI resolution to physical XML files sitting with
the NetCDF.
Cheers, Roy.
From: John Graybeal [jbgrayb...@mindspring.com]
Sent: 05 August 2011 17:57
To: Lowry, Roy K.
Cc: ngalbra...@whoi.edu; cf
is defined that can sit side-by-side with
internal encodings for a usage metadata subset would make me happy and shut me
up (on this issue at least).
Cheers, Roy.
From: Nan Galbraith [ngalbra...@whoi.edu]
Sent: 05 August 2011 20:58
To: Lowry, Roy K.
Cc: John Graybeal
Hi Jim,
Not the first time this has cropped up on the CF list. The problem is that
when the Standard Names started out they were designed as OPTIONAL terms to
identify model fields that referred to a given geophysical phenomenon. There
has been a sort of mission creep since then with
TEMP_Resolution;
char TEMP_Instrument_manufacturer(depth, 20);
char TEMP_Instrument_model(depth,6);
...
Nan
On 8/26/11 9:05 AM, Lowry, Roy K. wrote:
Hi Jim,
Not the first time this has cropped up on the CF list. The problem is that
when the Standard Names started out they were designed as OPTIONAL terms
Dear All,
I would suggest some fine tuning of this to:
platform_name
platform_id (note this needs to be alphanumeric to support ICES ship codes
widely used in oceanography)
platform_id_authority (mandatory if platform_id present)
platform_description
I wonder if the concept of authority is
Hi All,
Something in the back of my mind from a project in which I have peripheral
engagement (so may be a red herring or worse). Didn't Argo put a lot of effort
into a NetCDF history encoding for their format?
Cheers, Roy.
From:
Hi Jonathan,
My vote would go to something that is both human and machine-readable. There
are standards designed for this such as JSON. Some might consider this comes
down on the side of the machine more than the human, but I find once I get my
in I can read JSON much easier than XML.
If
' then their data
will be regarded as useless for many physical oceanographic applications.
Cheers, Roy.
-Original Message-
From: trevor.mcdoug...@csiro.au [mailto:trevor.mcdoug...@csiro.au]
Sent: 05 October 2011 00:12
To: Lowry, Roy K.; j.m.greg...@reading.ac.uk; paul.dur...@csiro.au
Cc
-
From: Rainer Feistel [mailto:rainer.feis...@io-warnemuende.de]
Sent: 06 October 2011 06:32
To: paul.dur...@csiro.au; j.m.greg...@reading.ac.uk; Lowry, Roy K.;
trevor.mcdoug...@csiro.au
Cc: stephen.griff...@noaa.gov; paul.bar...@csiro.au; King, Brian A.;
r...@eos.ubc.ca; CF-metadata
definition.
Hopefully, case closed!
Cheers, Roy.
From: trevor.mcdoug...@csiro.au [trevor.mcdoug...@csiro.au]
Sent: 08 October 2011 02:49
To: Lowry, Roy K.; rainer.feis...@io-warnemuende.de; paul.dur...@csiro.au;
j.m.greg...@reading.ac.uk
Cc: stephen.griff
, these still need managing and if they become
excessively abundant they also become difficult to navigate.
Cheers, Roy.
From: Vegard Bønes [vegard.bo...@met.no]
Sent: 15 November 2011 13:17
To: Lowry, Roy K.
Cc: cf-metadata@cgd.ucar.edu; Jonathan Gregory
Hi John,
I have a concern with your exclusion of the surface from the term
sea_water_temperature. What Standard Name would you use for the temperature
data stream in a CTD profile that extends from the surface to depth? I'm more
comfortable with the idea of keeping sea_water_temperature
Hi Upendra,
The Forel-Ule is another example where parameter semantics have been off-loaded
in the units of measure, such as 'milligrams per gram of dry sediment'. I have
been working to eliminate this by moving the semantics into the parameter
description to leave a UDUNITS-compatible UoM.
Hi Upendra,
It comes down to the significance of the difference between parameters
according to tha application for which they are used. There ae two temperature
scales - IPTS68 and ITS90. However, pragamatically for the period of time when
IPTS68 was used the measurement uncertaintyfor sea
Hi Philip,
I like that idea. I've always tried to label data such that future users can
judge the applicability of that data to their requirements. pH on an unknown
scale might be useless to a deep-ocean carbonate chemist, but works for some
datasets I have from the Humber where pH ranges
Dear All,
One thought that this debate has brought to mind is what should the practice be
if the file convention is a profile (in the ISO sense) of CF? In other words,
the file conforms to a given version of CF modified by a formally documented
set of extensions (e.g. optional CF attributes
declaration I have stated that
mark'sFruityProfile is CF compliant, is that enough information?
cheers
mark
-Original Message-
From: cf-metadata-boun...@cgd.ucar.edu on behalf of Lowry, Roy K.
Sent: Thu 29/12/2011 10:08
To: Jonathan Gregory; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata
January 2012 18:47
To: Lowry, Roy K.
Cc: CF Metadata List; sdn2-t...@seadatanet.org
Subject: Re: [CF-metadata] Convention attribute
I wasn't sure how to parse these, I'm a little slow today I guess. After
trying a few ways, I decided they mostly use spaces to separate convention
identifiers
.
...
...¶
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: Tuesday, April 03, 2012 2:16 PM
Subject: RE: [CF-metadata] Ocean CTD data following CF
-ordinate
harmonisation to the the application tools.
Yet another 'senior moment'..
Cheers, Roy.
From: cf-metadata-boun...@cgd.ucar.edu [cf-metadata-boun...@cgd.ucar.edu] On
Behalf Of Lowry, Roy K. [r...@bodc.ac.uk]
Sent: 03 April 2012 06:46
To: andrew
Hi Randy,
The practice recommended for SeaDataNet is to specify a fill value for the flag
that is defined in the flag convention as 'missing value'. I always feel more
comfortable with explicit semantics.
Cheers, Roy.
From: CF-metadata
Hi Ellyn,
Encoding wave spectra in a CF-compliant manner is an issue that I plan to
address on behalf of SeaDataNet in the next month or so. The point I'd reached
in thinking this through was to use the timeSeriesProfile feature type with
frequency as the z co-ordinate. I think this OK, but
be
misunderstanding something in John's view of feature types.
Cheers, Roy.
-Original Message-
From: Ellyn Montgomery [mailto:emontgom...@usgs.gov]
Sent: 29 August 2012 15:47
To: Lowry, Roy K.
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] example
: Hattersley, Richard [mailto:richard.hatters...@metoffice.gov.uk]
Sent: 30 August 2012 16:52
To: Lowry, Roy K.; Ellyn Montgomery
Cc: cf-metadata@cgd.ucar.edu
Subject: RE: [CF-metadata] example of
sea_surface_wave_directional_variance_spectral_density
Hi Roy,
There are some fairly explicit statements
Dear All,
It's becoming clear that we need a Standard Name component to cover boolean
values whose trigger point may then be specified elsewhere as Jonathan stated.
In the biological domain, the syntax 'presence_of_x' where x is a taxon name is
often used. Could this be adopted giving the
Suggestion 'presence_of_surface_snow' should have been
'presence_of_surface_snow_cover' to maintain consistency
From: CF-metadata [cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Lowry, Roy K.
[r...@bodc.ac.uk]
Sent: 05 September 2012 19:49
To: Ute
Dear All,
Up until now, addressing of CF Standard Names through the NERC Vocabulary
Server has been through opaque identifiers such as 'P07' and 'CFV8N1'. In
response to requests for addressing through semantically meaningful URLs we
have introduced a system of alternative URLs using the
To: Ben Domenico
Cc: caru...@mbari.org; nat...@imaa.cnr.it; Leadbetter, Adam;
jgrayb...@ucsd.edu; lbermu...@opengeospatial.org; Lowry, Roy K.
Subject: Re: CF Names vocabulary
Hello All (those who I know Ben, Luiz, Stefan, John) and those who I do not
know (Carlos Adam)
I am at the UNIDATA pol
Hello Philip/John,
As John might remember, I attempted this approach a while back (I think I
started in 2004) on another parameter vocabulary (the BODC vocabulary
subsequently adopted by SeaDataNet). I have yet to succeed in implementing it
operationally. This was because of two issues:
1)
Hello Martin,
I understand exactly what you want - or at least I thing I do. I think that
you would like to enter a URL representing the concept 'carbon monoxide' and
get back a document giving you all the Standard Names pertaining to carbon
monoxide. Am I right?
My vision - which I'm
: Jonathan Gregory [j.m.greg...@reading.ac.uk]
Sent: 24 September 2012 17:53
To: Schultz, Martin
Cc: Lowry, Roy K.; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Another potentially useful extension to the
standard_name table
Dear Martin, Roy et al.
I understand exactly what you want - or at least
) then no, but there are opinions that have me 75% convinced that
these are of little consequence in a linked data environment.
Cheers, Roy.
From: simon@csiro.au [simon@csiro.au]
Sent: 24 September 2012 04:33
To: Lowry, Roy K.; jgrayb...@ucsd.edu; cameronsmi...@llnl.gov
Cc: cf
Dear All,
Martin Schultz was proposing an extension to the Standard Name table to provide
a means of easily identifying the Standard Names associated with a given
atmospheric contaminant. What follows provides an alternative way to address
his use case. Go to the URL
be moles per square metre.
Cheers, Roy.
From: Christophe Lerot [christophe.le...@aeronomie.be]
Sent: 04 December 2012 10:20
To: Lowry, Roy K.
Cc: alison.pamm...@stfc.ac.uk; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] new standard name proposal
Tel: +44 1235 778065
NCAS/British Atmospheric Data CentreEmail: alison.pamm...@stfc.ac.uk
STFC Rutherford Appleton Laboratory
R25, 2.22
Harwell Oxford, Didcot, OX11 0QX, U.K.
-Original Message-
From: Lowry, Roy K. [mailto:r...@bodc.ac.uk]
Sent: 04 December 2012 10:23
Dear All,
It has been pointed out to me that the SeaDataNet NetCDF specification uses
'sea_water_pressure' as the Standard Name in cases where pressure is used as
the z co-ordinate in observational data such as CTD profiles. The definition
for this Standard Name is:
the pressure that exists
Dear All,
I totally agree with Heiko's words of caution. In my experience (over 30 years
of oceanographic data management) duplicated information inevitably leads to
inconsistent information.
Cheers, Roy.
Please note that I now work part-time from Tuesday to Thursday. E-mail
response on
Dear All,
Currently, the 'Conventions' attribute is restricted to be a global attribute.
There is currently a requirement to label multiple QC flag variables following
different conventions with their source convention and having the 'Conventions'
attribute as a variable attribute for these
, Roy K. wrote:
Dear All,
Currently, the 'Conventions' attribute is restricted to be a global
attribute. There is currently a requirement to label multiple QC flag
variables following different conventions with their source convention
and having the 'Conventions' attribute as a variable
Dear Jonathan and Martin,
What I was trying to do here was legitimise an already established practice in
at least two communities in the observational oceanographic domain with
thousands of files in existence with the non-standard usage of the Conventions
attribute. I also carried the practice
Hi Nan,
Would the CF web site be an appropriate place for communities to post the
attributes they have added to CF - either with or without namespace prefixes?
Cheers, Roy.
From: CF-metadata [cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Nan Galbraith
Hi Nan,
Slight misunderstanding I fear. The p021 vocabulary is a vocabulary that MAPS
to the CF Standard Names, but it doesn't include the Standard Names themselves.
What I think Nicolas is after is something slightly different, namely a
standardised 6-byte representation for each Standard
Hello Alison,
I had been hanging back waiting for John to respond to Jonathan's comment,
because nephelometric turbidity is a phenomenon that I've seen described - but
not necessarily defined - in a couple of different ways. However, whilst both
turbidity and secchi disk depth (and attenuance
Dear All,
I see Pandora's Box opening before us. I have been down the road of setting up
my equivalent to Standard Names (the BODC Parameter Usage Vocabulary) with
concepts that include specification of the biological entity, which is why I
have a vocabulary with getting on for 30,000
://nodc.ogs.trieste.it/
Il 22/03/2013 16:15, Lowry, Roy K. ha scritto:
Hi Klaas,
What I was trying to say in my e-mail to CF was that I strongly suggest
that CF
decouples the Standard Name from the species name. However, should they
choose not to then the cfu semantics should be removed from
/
Il 22/03/2013 16:15, Lowry, Roy K. ha scritto:
Hi Klaas,
What I was trying to say in my e-mail to CF was that I strongly suggest
that CF
decouples the Standard Name from the species name. However, should they
choose not to then the cfu semantics should be removed from the units of
measure
Dear All,
I am considering setting up a Trac ticket aimed at making the following changes
to the standard
1) Addition of a section on handling biological data in CF
2) Addition of a couple of parameter attributes for taxon name and taxon
identifier (e.g. Aphia ID)
3) Proposing a set of
Thanks Jonathan,
I was indeed responsible for introducing 'green dogs' to discussions in CF, but
since then my experience has expanded further into biological data and, in
particular, into the world of contaminants in biota through EMODNET and our
work in BODC with the Sea Mammal Research
Dear All,
I am currently working on a Trac ticket submission for handling of taxonomic
data in CF and thought I'd run an example past the list to make sure I've got
it right.
Jonathan suggested using a container variable analogous to geographic regions.
My interpretation of this would result
Hello Jonathan,
The reason that I used MAXT rather than TIME is that I am trying to follow the
point data conventions with the possibility of multiple time series (along the
INSTANCE dimension) of different lengths stored as padded rather than ragged
arrays in a single file. Your example is
Hi Jim,
There are a lot of nails being hit on the head at the moment. The Standard
Name attribute was conceived as a standardised label for the geophysical
phenomenon - a sort of grouping term for what was being measured. Note that
the Standard Name isn't a mandatory attribute in CF - the
Hello Randy,
If doing this, please make it clear that by 'Spectral' you mean 'wavelength
spectral'. There are other types of spectra, such as frequency (used for wave
spectra) and size (used optical plankton counters and other particle sizers).
Cheers, Roy.
Please note that I now work
1 - 100 of 382 matches
Mail list logo
