[Esip-documentation] Documentation Cluster Telecon TODAY

[Nan Galbraith]

Hi all -

Sorry that I missed this telecon, sounds like it was interesting.

My understanding is that cdm_data_type is not part of CF, but is used
by THREDDS, and was introduced as part of ACDD V1.0.

Here's what we wrote about this issue in the OceanSITES docs:

     cdm_data_type: The Unidata CDM (common data model) data
     type, used by THREDDS. e.g. point, profile, section, station,
     station_profile, trajectory, grid, radial, swath, image;
     use 'station' for OceanSITES mooring data.  (ACDD)

     featureType : Optional, and only for files using the Discrete
     Sampling Geometry, available in CF-1.5 and later. See CF
     documents. (CF)


The acronyms in parenthesis (ACDD/CF) indicate which external 
specification the term
came from; we're trying to avoid re-defining anything.  I spent longer 
than I'd wanted
to trying to track down where the term cdm_data_type actually came from; 
it's
not found in the THREDDS docs, as far as I was able to determine. Also,
I think we've discussed this more than once before on the ACDD team -
funny how it keeps giving!

Nan

On 4/17/14 3:18 PM, John Graybeal wrote:
> In our telecon a side discussion broke out on the chat session, which 
> I failed to copy but would like to continue. The final question of the 
> session, from Mike McCann, went something like:
>
>> In CF 1.5 there was a cdm_data_type with a specific controlled 
>> vocabulary; in CF 1.6 it was replaced by feature_type with a 
>> different controlled vocabulary. Since ACDD doesn't specify what CF 
>> convention applies, does this represent a potential conflict?
>
> With regard to 1.6, I don't believe it represents a conflict because 
> there is no cdm_data_type in CF 1.6, and the ACDD cdm_data_type is 
> explicitly different from CF's feature_type.
>
> With regard to 1.5, looking at the specification at 
> http://cf-convention.github.io/1.5.html, I'm not seeing cdm_data_type. 
>  So I may have misquoted Mike, but so far I'm not seeing a conflict in 
> this item.
>
> The overall concern is whether not specifying a corresponding CF 
> version is a problem for ACDD.  I hadn't thought of that, but I don't 
> know of a conflict -- let me know if anyone comes up with an issue.
>
> Mike, all, please feel free to continue the discussion here or off-line.
>
> John
>
>
> On Apr 17, 2014, at 10:48, Ted Habermann <thabermann at hdfgroup.org 
> <mailto:thabermann at hdfgroup.org>> wrote:
>
>> Great...
>>
>>
>> <SignatureSm2.png>
>>
>> On Apr 17, 2014, at 12:45 PM, John Graybeal 
>> <jbgraybeal at mindspring.com <mailto:jbgraybeal at mindspring.com>> wrote:
>>
>>> propose topic "Update re ACDD status"
>>>
>>> john
>>>
>>>
>>> On Apr 17, 2014, at 10:07, Kelly Monteleone <krbm at unm.edu 
>>> <mailto:krbm at unm.edu>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Sorry about the late notice.  Our monthly telecon is TODAY, at 2 pm 
>>>> EST.  The agenda is still below and can be found 
>>>> athttp://wiki.esipfed.org/index.php/Category:Documentation_Cluster .
>>>>
>>>>


-- 
*******************************************************
* Nan Galbraith        Information Systems Specialist *
* Upper Ocean Processes Group            Mail Stop 29 *
* Woods Hole Oceanographic Institution                *
* Woods Hole, MA 02543                 (508) 289-2444 *
*******************************************************


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-documentation/attachments/20140417/e070e1b3/attachment.html>