[Go-essp-tech] Extending the DRS syntax to observations

[Renata McCoy]

Hi Chris, Luca,

It could also be a requested attribute of a variable. I propose adding the following attributes (CMOR table specified attribute) for each variable:
   -- source   (a string description of a specific source of the measurement)
   -- source_datastream  (file datastream identifier with the version) 
   -- source_url  (a reference url for the source data)

Greetings,
Renata


On Jan 27, 2011, at 11:26 AM, Cinquini, Luca (3880) wrote:

> Hi Chris,
> 	good question. My feeling is that this information is too complex to be encoded as part of the file names or directory structure, and should probably go into two places:
> 
> o The tech note that is associated with each dataset
> o Perhaps, a global attribute that is encoded in the netcdf files themselves (which can be harvested and displayed on the web interface)
> 
> What's your opinion ?
> 
> thanks, Luca
> 
> On Jan 27, 2011, at 12:08 PM, Lynnes, Christopher S. (GSFC-6102) wrote:
> 
>> Luca,
>>  Where do you make visible the information that those files were generated by the AIRS processing software version 5.2.2, or alternatively that it is Collection 5 AIRS and not Collection 3 AIRS?  These distinctions are rather critical w.r.t. the content of the data...
>> 
>> 
>>> 
>>> The values for the various fields <agency>, <mission>, <instrument> and <processing level> would need to be selected from a controlled vocabulary similar to the one established for models.
>>> 
>>> Any comment or insight on the matter is appreciated.... The idea is to try to finalize the specification relatively quickly, let's say a couple of weeks, so that we can start preparing
>>> and publishing these observations into the CMIP5 archive.
>>> 
>>> thanks in advance,
>>> 
>>> Luca
>>> 
>> 
>> --
>> Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185
> 
>