<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi all,<br>
<br>
yes I think as well those attributes can describe the nature of the
link between raw measurement and used product.<br>
Taking an example I know:<br>
<br>
<span style="color: rgb(0, 0, 0);">- CALIPSO-GOCCP is derived from
Calipso L1/NASA products (NASA Langley ASDC - CALIPSO Data Sets).</span><br>
- A piece of code is applied on L1 product to produce an information
directly comparable with gcm outputs (and COSP package).<br>
- This piece of code and the underlying reasoning have clear
identifier and references (doi).<br>
<pre wrap=""> -- source (a string description of a specific source of the measurement)
<span style="color: rgb(0, 0, 0);">Calipso L1/NASA products (NASA Langley ASDC - CALIPSO Data Sets).</span>
-- 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)
<a class="moz-txt-link-freetext" href="http://climserv.ipsl.polytechnique.fr/fr/cfmip-observations-3.html">http://climserv.ipsl.polytechnique.fr/fr/cfmip-observations-3.html</a>
-- source_doi (a citable reference describing in deep detail methodology used behind the scene)
<span style="color: rgb(0, 0, 0);">H. Chepfer, S.Bony</span>,<span style="color: rgb(0, 0, 0);"> 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,</span> D00H16, doi:10.1029/2009JD012251<span style="color: rgb(0, 0, 0);">,</span><span style="color: rgb(0, 0, 0);"> </span>
<a href="http://www.agu.org/journals/jd/jd1005/2009JD012251/" class="jce_doclink" title="http://www.agu.org/journals/jd/jd1005/2009JD012251/" target="_blank">http://www.agu.org/journals/jd/jd1005/2009JD012251/</a>
</pre>
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.<br>
<br>
Regards.<br>
Sébastien<br>
<br>
On 27/01/2011 20:52, Cinquini, Luca (3880) wrote:
<blockquote
cite="mid:21AC7C84-FA02-4C42-882F-9E27937FD448@jpl.nasa.gov"
type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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...
</pre>
<blockquote type="cite">
<pre wrap="">
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
</pre>
</blockquote>
<pre wrap="">
--
Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
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
</pre>
</body>
</html>