<!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">
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0, 0);
font-weight: normal; margin: 10px 0px; padding: 0px;">Hi Luca,</p>
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0, 0);
font-weight: normal; margin: 10px 0px; padding: 0px;">Just below
is a version of your email of this morning which has minor
editorial changes (<font color="#ff0000"><b>in red</b></font>) to
reflect a broader outlook on the term "observations", and an
initial proposal for gridded <i>in situ</i> observations. I
think if we adopt language like this we will be glad of it in the
long term:<br>
</p>
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0, 0);
font-weight: normal; margin: 10px 0px; padding: 0px;"> - Steve<br>
</p>
<blockquote>
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0, 0);
font-weight: normal; margin: 10px 0px; padding: 0px;"><b>Open
Questions</b></p>
<ul style="font-size: 10pt; line-height: 13pt; list-style-type:
disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Agree on basic DRS-like structure for
observations and meaning of each field
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Use activity="cmip5" or
activity="cmip54obs", "obs4models" ?</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">DRS hierarchy for models (partial):
"institute" > "model" > "experiment" > "ensemble"</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Current proposed hierarchy for <font
color="#ff0000"><b>gridded</b></font> <font
color="#ff0000"><b>remote sensed</b></font> observations
(partial): "institute" (="agency") > "mission" >
"instrument" > ("processing level" + "other
specifiers")</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Alternative proposal for <b><font
color="#ff0000">gridded remote sensed</font></b>
observations (partial): "institute" (="agency") >
"instrument" > "processing level" > ?</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;"><font color="#ff0000">Need a proposal for <b>gridded
in situ observations</b>, say: "institute"
(="agency") > "program" > "resolution">
"variant" ?</font></li>
<ul>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;"><font color="#ff0000">e.g. NOAA/NCAR
/ ICOADS / 1degree / equatorial / </font></li>
</ul>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;"><font color="#ff0000">Should we even
attempt to describe in situ (point and trajectory)
observations through DRS? (can we succeed at this?)</font><br>
</li>
</ul>
</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Decide on whether to have one single CMOR table
for observations (currently "obsSites"), or more than one
depending on types of observational data:
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">remote sensed (grids and swaths)</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">in-situ stations (time series and profiles)</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">trajectory-based observations</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">in-situ gridded products</li>
</ul>
</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Decide on whether to encode global attributes
for data source in netcdf files ("source",
"source_datastream", "source_url", "source_reference")</li>
</ul>
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0, 0);
font-weight: normal; margin: 10px 0px; padding: 0px;"><b>Action
Items</b></p>
<ul style="font-size: 10pt; line-height: 13pt; list-style-type:
disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Populate CV for observations (decide on
upper/lower case)</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Produce some reference datasets</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Develop snippet of "esg.ini" (ESG publisher)
configuration for processing observations</li>
</ul>
</blockquote>
<br>
<br>
On 1/31/2011 6:58 AM, Cinquini, Luca (3880) wrote:
<blockquote
cite="mid:04B66A74-B5A5-492C-AAD7-14893841A62C@jpl.nasa.gov"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Hi all,
<div><span class="Apple-tab-span" style="white-space: pre;"> </span>thanks
to everybody for the lively discussion... I just wanted to
summarize what I think is the status so far - I posted this also
on the wiki. Please keep the discussion going...</div>
<div>thanks, Luca</div>
<div><br>
</div>
<div><span class="Apple-style-span" style="font-family:
Helvetica,Arial,sans-serif; font-size: 13px; line-height:
17px;">
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0,
0); font-weight: normal; margin: 10px 0px; padding: 0px;"><b>Open
Questions</b></p>
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Agree on basic DRS-like structure for
observations and meaning of each field
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">Use activity="cmip5" or
activity="cmip54obs", "obs4models" ?</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">DRS hierarchy for models
(partial): "institute" > "model" > "experiment"
> "ensemble"</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">Current proposed hierarchy for
observations (partial): "institute" (="agency") >
"mission" > "instrument" > ("processing level" +
"other specifiers")</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">Alternative proposal for
observations (partial): "institute" (="agency") >
"instrument" > "processing level" > ?</li>
</ul>
</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Decide on wether to have one single CMOR
table for observations (currently "obsSites"), or more
than one depending on types of observational data:
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">remote sensed (grids and swaths)</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">in-situ stations (time series and
profiles)</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">trajectory-based observations</li>
<li style="font-size: 10pt; line-height: 13pt; margin:
0px; padding: 0px;">in-situ gridded products</li>
</ul>
</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Decide on wether to encode global
attributes for data source in netcdf files ("source",
"source_datastream", "source_url", "source_reference")</li>
</ul>
<p style="font-size: 10pt; line-height: 13pt; color: rgb(0, 0,
0); font-weight: normal; margin: 10px 0px; padding: 0px;"><b>Action
Items</b></p>
<ul style="font-size: 10pt; line-height: 13pt;
list-style-type: disc;">
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Populate CV for observations (decide on
upper/lower case)</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Produce some reference datasets</li>
<li style="font-size: 10pt; line-height: 13pt; margin: 0px;
padding: 0px;">Develop snippet of "esg.ini" (ESG
publisher) configuration for processing observations<br>
</li>
</ul>
</span>
<div><br>
</div>
<div>
<div>On Jan 31, 2011, at 2:42 AM, Bryan Lawrence wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div><br>
Hi Folks<br>
<br>
Sorry I've come late to this discussion.<br>
<br>
I've got just two simple points to make (for now).<br>
<br>
Firstly, I think this activity (organising observational
data to support <br>
CMIP5) is not the same as cmip5 itself. Sooner or later
things break in <br>
the DRS heirarchy doing this, and so I think it would be
helpful to all <br>
consumers if this was dealt with at the top level of the
DRS. <br>
Additionally, remember obs are timeless, models are not.
This data will <br>
be useful beyond cmip5 (e.g. cordex). So I recommend *not*
shoehorning <br>
all the obs data under cmip5 in the DRS.<br>
<br>
The DRS allows you to define new activiites, and I'd do
so, something <br>
like obs4models or (if you must) cmip5obs ....<br>
<br>
Otherwise I'm fine with the approach. <br>
<br>
Secondly, wrt to Steve's list below: there is of course
swath data as <br>
well ... but otherwise I rather agree that 3 and 1 can be
handled the <br>
same.<br>
<br>
Cheers<br>
Bryan<br>
<br>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>