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

[Sébastien Denvil]

  Hi all,

yes I think as well those attributes can describe the nature of the link 
between raw measurement and used product.
Taking an example I know:

- CALIPSO-GOCCP is derived from Calipso L1/NASA products (NASA Langley 
ASDC - CALIPSO Data Sets).
- A piece of code is applied on L1 product to produce an information 
directly comparable with gcm outputs (and COSP package).
- This piece of code and the underlying reasoning have clear identifier 
and references (doi).

   -- source   (a string description of a specific source of the measurement)
	Calipso L1/NASA products (NASA Langley ASDC - CALIPSO Data Sets).
   -- source_datastream  (file datastream identifier with the version)
	Code version used to compute derive product (svn/cvs/git/... version or code identifier)
   -- source_url  (a reference url for the source data)
	http://climserv.ipsl.polytechnique.fr/fr/cfmip-observations-3.html
   -- source_doi  (a citable reference describing in deep detail methodology used behind the scene)
	H. Chepfer, S.Bony,  D. M. Winker, G. Cesana, JL. Dufresne, P. Minnis, C.J. Stubenrauch, S. Zeng, 2009 : "The GCM Oriented
	CALIPSO Cloud Product (CALIPSO-GOCCP)", J. Geophys. Res., 105,  D00H16, doi:10.1029/2009JD012251,  
	http://www.agu.org/journals/jd/jd1005/2009JD012251/

Thinking about that it could be good to add as well a citable reference 
in the global attribute. I'm sure all observational dataset will have 
one. Just a suggestion.

Regards.
Sébastien

On 27/01/2011 20:52, Cinquini, Luca (3880) wrote:
> Hi Renata,
> 	these attributes seem like a good idea to me. It is beyond what the models have, but the nature of these observational data is that they come from some other data...
> thanks, Luca
>
> On Jan 27, 2011, at 12:45 PM, Renata McCoy wrote:
>
>> 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
>>>
>>
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech


-- 
Sébastien Denvil
IPSL, Pôle de modélisation du climat
UPMC, Case 101, 4 place Jussieu,
75252 Paris Cedex 5

Tour 45-55 2ème étage Bureau 209
Tel: 33 1 44 27 21 10
Fax: 33 1 44 27 39 02

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110127/71f7014e/attachment-0001.html