[Esip-documentation] ACDD: global attribute: source vs. variable attribute: coverage_content_type

Aaron Sweeney aaron.sweeney at noaa.gov
Mon Jan 5 14:44:14 EST 2015


Thanks for the clarification, Jim, especially for the tip about 
capturing this disambiguation between obs and model variables in the 
summary attribute.

Cordially,
Aaron

On 01/05/2015 12:30 PM, Jim Biard via Esip-documentation wrote:
> Aaron,
>
> The source attribute is a free text field, so you can describe both 
> parts with no problem. The attribute is intended for human reading, 
> not machine processing. Just keep it succinct. You can and should 
> provide a detailed explanation in the summary attribute.
>
> Grace and peace,
>
> Jim
>
> On 1/5/15 2:13 PM, Aaron Sweeney via Esip-documentation wrote:
>> Hi,
>>
>>       I am planning to create a single netCDF file which contains 
>> both insitu observations and modelled values and am trying to 
>> understand how best to use ACDD to distinguish the two.
>>
>>       It appears that I can provide each variable with a 
>> highly-recommended attribute "coverage_content_type" to distinguish 
>> between variables containing insitu observations 
>> ("physicalMeasurement") or modelled values ("modelResult"). This 
>> sounds reasonable.  However, their also exists a recommended global 
>> attribute "source", whose description (see below) seems to imply that 
>> the entire file contains either insitu observations or modelled 
>> values, but not both.
>>
>>> The method of production of the original data. If it was 
>>> model-generated, source should name the model and its version. If it 
>>> is observational, source should characterize it. This attribute is 
>>> defined in the CF Conventions. Examples: 'temperature from CTD 
>>> #1234'; 'world model v.0.1'. 
>>
>>       Am I interpreting the description of the global attribute 
>> "source" correctly?
>>
>>       If not, would a comma-separated list be allowed in the global 
>> attribute "source" to enable inclusion of both insitu observations 
>> and modelled values in the same file?
>>
>>       Thanks for your kind consideration.
>>
>> Cordially,
>> Aaron
>>
>
> -- 
> CICS-NC <http://www.cicsnc.org/> Visit us on
> Facebook <http://www.facebook.com/cicsnc> 	*Jim Biard*
> *Research Scholar*
> Cooperative Institute for Climate and Satellites NC <http://cicsnc.org/>
> North Carolina State University <http://ncsu.edu/>
> NOAA's National Climatic Data Center <http://ncdc.noaa.gov/>
> 151 Patton Ave, Asheville, NC 28801
> e: jbiard at cicsnc.org
> o: +1 828 271 4900
>
>
>
>
>
>
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-documentation

-- 
Aaron D. Sweeney
Water Level Data Manager

Cooperative Institute for Research in Environmental Sciences (CIRES)
University of Colorado at Boulder
and
NOAA National Geophysical Data Center
Marine Geology and Geophysics Division
325 Broadway, E/GC3
Boulder, CO 80305-3328

Phone: 303-497-4797, Fax: 303-497-6513

DISCLAIMER: The contents of this message are mine personally and do not necessarily reflect any position of NOAA.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-documentation/attachments/20150105/f72aa416/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11847 bytes
Desc: not available
URL: <http://lists.deltaforce.net/pipermail/esip-documentation/attachments/20150105/f72aa416/attachment-0001.png>


More information about the Esip-documentation mailing list