<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi all,<br>
<br>
I would suggest to create separate table for station data and remote
sensing data. Also for remote sensing data we will need separate
table depending on frequency (monthly or daily or ....)<span
style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31, 73,
125);"></span>. <br>
<br>
Within a cmor table you can define the following value (in day).
This value is used by cmor to check that your time axis is
increasing the way it should.<br>
approx_interval: 30.000000<br>
<br>
regards.<br>
Sébastien<br>
<br>
On 28/01/2011 16:31, Palanisamy, Giri wrote:
<blockquote
cite="mid:CBEF2347B084924995CFE4561590F88E703556474D@EXCHMBA.ornl.gov"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Grande";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"\0027Lucida Grande\0027";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Hi Luca…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Good question. So for, we have only added the
variables from
Observational station data. We can either make this table
common for both
station data and remote sensing data, or create separate
tables.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Also, the obsSites is still an early draft, and
probably needs
more use cases before it can be used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Giri<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a class="moz-txt-link-freetext" href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>] <b>On
Behalf Of </b>Cinquini, Luca (3880)<br>
<b>Sent:</b> Friday, January 28, 2011 7:41 AM<br>
<b>To:</b> Renata McCoy<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>; Sébastien Denvil;
climate-obs; Lynnes,
Christopher S. (GSFC-6102)<br>
<b>Subject:</b> Re: [Go-essp-tech] Extending the DRS
syntax to observations<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Renata and Giri,<o:p></o:p></p>
<div>
<p class="MsoNormal"><span class="apple-tab-span">
</span>thanks for the
spreadsheet, we should encourage all people who will be
providing obs to CMIP5
to take a look and add their contribution.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I do have a question: the obs table is
now called
"obsSites". Is this meant to also include remote sensing
datasets, or
just station data ? Should we have a collection of CMOR obs
tables ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">thanks, Luca<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Jan 27, 2011, at 3:51 PM, Renata
McCoy wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Hi All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The spreadsheet for developing the
observational CMOR table
controlled variables list is on google docs :<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <a moz-do-not-send="true"
href="https://spreadsheets.google.com/ccc?key=0ArrcdEATH6R8dDJEYUstbnpaSmpZTVh6OVZpOEl5SUE&hl=en&authkey=CNbh2t0P#gid=20">https://spreadsheets.google.com/ccc?key=0ArrcdEATH6R8dDJEYUstbnpaSmpZTVh6OVZpOEl5SUE&hl=en&authkey=CNbh2t0P#gid=20</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Everyone with the url can modify
it, so maybe we need to use
colors to indicate what is being changed. We need to
define the temporal and
spacial (pressure, or height) axes somewhere.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The observational table itself is
in a tab named 'obsSites'
(you may need to scroll to see it or use navigational
arrow in the tabs menu to
see more tabs). It's mostly a copy of cfSites but with
modification for the
obs. specifications. This is just a beginning, we will
be adding more
variables, as needed, please do add the variables that
your data requires.
Notice that all the 2D variables from Amon are part of
this table, with the
modification in time cell method (which now allows
instantaneous (time:point)
and time average (time:mean) measurements with any
time average
interval). <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks to Giri for setting it up!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Greetings,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Renata<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:
"";" lucida="" grande="" ,="" serif=""> </span><span
style="font-family: "Lucida
Grande","serif";"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">On Jan 27, 2011, at 1:06 PM,
Sébastien Denvil wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">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: black;">- 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>
<br>
<o:p></o:p></p>
<pre> -- source (a string description of a specific source of the measurement)<o:p></o:p></pre>
<pre> <span style="color: black;">Calipso L1/NASA products (NASA Langley ASDC - CALIPSO Data Sets).</span><o:p></o:p></pre>
<pre> -- source_datastream (file datastream identifier with the version)<o:p></o:p></pre>
<pre> Code version used to compute derive product (svn/cvs/git/... version or code identifier)<o:p></o:p></pre>
<pre> -- source_url (a reference url for the source data)<o:p></o:p></pre>
<pre> <a moz-do-not-send="true" href="http://climserv.ipsl.polytechnique.fr/fr/cfmip-observations-3.html">http://climserv.ipsl.polytechnique.fr/fr/cfmip-observations-3.html</a><o:p></o:p></pre>
<pre> -- source_doi (a citable reference describing in deep detail methodology used behind the scene)<o:p></o:p></pre>
<pre> <span style="color: black;">H. Chepfer, S.Bony</span>,<span style="color: black;"> D. M. Winker, G. Cesana, JL. Dufresne, P. Minnis, C.J. Stubenrauch, S. Zeng, 2009 : "The GCM Oriented<o:p></o:p></span></pre>
<pre><span style="color: black;"> CALIPSO Cloud Product (CALIPSO-GOCCP)", J. Geophys. Res., 105,</span> D00H16, doi:10.1029/2009JD012251<span style="color: black;">, </span><o:p></o:p></pre>
<pre> <a moz-do-not-send="true" href="http://www.agu.org/journals/jd/jd1005/2009JD012251/" target="_blank" title="http://www.agu.org/journals/jd/jd1005/2009JD012251/">http://www.agu.org/journals/jd/jd1005/2009JD012251/</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<p class="MsoNormal">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: <o:p></o:p></p>
<pre>Hi Renata,<o:p></o:p></pre>
<pre> 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... <o:p></o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 27, 2011, at 12:45 PM, Renata McCoy wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Hi Chris, Luca,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>It could also be a requested attribute of a variable. I propose adding the following attributes (CMOR table specified attribute) for each variable:<o:p></o:p></pre>
<pre> -- source (a string description of a specific source of the measurement)<o:p></o:p></pre>
<pre> -- source_datastream (file datastream identifier with the version) <o:p></o:p></pre>
<pre> -- source_url (a reference url for the source data)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Greetings,<o:p></o:p></pre>
<pre>Renata<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 27, 2011, at 11:26 AM, Cinquini, Luca (3880) wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Hi Chris,<o:p></o:p></pre>
<pre> 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:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>o The tech note that is associated with each dataset<o:p></o:p></pre>
<pre>o Perhaps, a global attribute that is encoded in the netcdf files themselves (which can be harvested and displayed on the web interface)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What's your opinion ?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 27, 2011, at 12:08 PM, Lynnes, Christopher S. (GSFC-6102) wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Luca,<o:p></o:p></pre>
<pre>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...<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt;
margin-bottom: 5pt;">
<pre>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.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>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<o:p></o:p></pre>
<pre>and publishing these observations into the CMIP5 archive.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>thanks in advance,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
<pre>--<o:p></o:p></pre>
<pre>Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185<o:p></o:p></pre>
</blockquote>
</blockquote>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Sébastien Denvil<o:p></o:p></pre>
<pre>IPSL, Pôle de modélisation du climat<o:p></o:p></pre>
<pre>UPMC, Case 101, 4 place Jussieu,<o:p></o:p></pre>
<pre>75252 Paris Cedex 5<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Tour 45-55 2ème étage Bureau 209<o:p></o:p></pre>
<pre>Tel: 33 1 44 27 21 10<o:p></o:p></pre>
<pre>Fax: 33 1 44 27 39 02<o:p></o:p></pre>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</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>