Forgot to select Reply All.......
Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in the office. All vocabulary queries should be sent to enquiries at bodc.ac.uk. Please also use this e-mail if your requirement is urgent.
________________________________
From: Lowry, Roy K.
Sent: 31 August 2016 09:25
To: ngalbraith at whoi.edu
Subject: Re: [CF-metadata] radiosonde ascent rate?
Dear Nan,
I have never seen descent rate included as a CTD data parameter. Occasionally, I have seen it included as a single figure - often covering a whole cruise - in accompanying plain-language metadata.
Cheers, Roy.
Please note that I partially retired on 01/11/2015. I am now only working 7.5 hours a week and can only guarantee e-mail response on Wednesdays, my day in the office. All vocabulary queries should be sent to enquiries at bodc.ac.uk. Please also use this e-mail if your requirement is urgent.
________________________________
From: CF-metadata <cf-metadata-bounces at cgd.ucar.edu> on behalf of Nan Galbraith <ngalbraith at whoi.edu>
Sent: 30 August 2016 22:18
To: cf-metadata at cgd.ucar.edu
Subject: Re: [CF-metadata] radiosonde ascent rate?
Hmm, interesting! I remember looking closely at the platform standard
names, but not thinking
about platforms moving straight up or down.
Could you use platform_speed_wrt_ground along with platform_course or
_orientation?
||Instead of adding 'upward' to the std name, could you supply it as an
attribute for speed?
I thought there might be a standard attribute in ACDD for this info, but
there really isn't.
How do people supply descent rate for the millions of CTDs that are in CF?
Cheers - Nan
On 8/29/16 4:30 PM, Jim Biard wrote:
>
> Leslie,
>
> That sounds like a good name, assuming that you really need one. CF
> does not require a standard name for every variable. The primary
> intention of standard names is to make it easier to see that you are
> comparing apples to apples with data (or at least quinces to apples,
> as opposed to hat-racks to apples).
>
> If you think the benefits of having a standard name are great enough
> to go through the minimal bother, then make a "formal" request in an
> email to the list.
>
> Grace and peace,
>
> Jim
>
>
> On 8/29/16 3:10 PM, Leslie Hartten (NOAA Affiliate) wrote:
>> Dear List,
>>
>> I am putting together a radiosonde dataset and trying hard to stick
>> with CF Standard Names. I have combed through the table
>> (http://cfconventions.org/Data/cf-standard-names/current/build/cf-standard-name-table.html)
CF Standard Name Table - CF Conventions<
http://cfconventions.org/Data/cf-standard-names/current/build/cf-standard-name-table.html>
cfconventions.org
Version 35, 20 July 2016 Refer to the Guidelines for Construction of CF Standard Names for information on how the names are constructed and interpreted, and how ...
>> and this list's archives, but found nothing that would obviously work
>> as a name for the ascent rate of a radiosonde. At present, I have
>> taken the name " platform_speed_wrt_ground" and prefaced it with
>> "upward_", since there is horizontal motion w/r/to the ground that is
>> not considered in this variable.
>>
>> Does anyone have an already legal suggestion for radiosonde ascent
>> rate? Should I request a new variable,
>> "upward_platform_speed_wrt_ground"?
>>
>> Many thanks for any assistance. I never even knew about CF
>> standard names until I started QC'ing data from our field program and
>> trying to create good data files!
>>
>> Cheers,
>> Leslie
--
*******************************************************
* Nan Galbraith Information Systems Specialist *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 (508) 289-2444 *
*******************************************************
_______________________________________________
CF-metadata mailing list
CF-metadata at cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
________________________________
This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20160831/b095b23f/attachment.html>
Received on Wed Aug 31 2016 - 02:26:13 BST
