<!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">
Dear Karl,<br>
<br>
the file we published on ESG where originally created using "23
August 2010" or "30 November 2010" tables. <br>
<br>
But we rewrote them using "31 January 2011" tables where necessary.<br>
<br>
For example *all* our land variables has been rewritten using 31
January 2011 tables. So *all* our land files have standard name in
it.<br>
<br>
I don't know how gateways feed their standard names database. But it
could be that they use CMOR2 tables and not the metadata coming from
the files. This could be another explanation.<br>
<br>
------------------------<br>
creation_date = "2011-01-08T01:50:31Z" ;<br>
history = "2011-01-08T01:50:31Z CMOR rewrote data to comply with CF
standards and CMIP5 requirements." ;<br>
table_id = "Table 6hrLev (30 November 2010)
6c116423753a0c320c0cf3e31acd51b9" ;<br>
------------------------<br>
creation_date = "2011-02-23T17:56:33Z" ;<br>
history = "2011-02-23T17:56:33Z CMOR rewrote data to comply with CF
standards and CMIP5 requirements." ;<br>
table_id = "Table Lmon (31 January 2011)
a84ae296f75bb85ff61668fac8fcf090" ;<br>
------------------------<br>
<br>
Regards.<br>
Sébastien<br>
<br>
On 27/05/2011 23:37, Karl Taylor wrote:
<blockquote cite="mid:4DE01986.6000109@llnl.gov" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<font face="Times New Roman">Dear Stephen,<br>
<br>
Here's some information that might provide a partial
explanation:<br>
<br>
1. all 10 variables you list do indeed have the same same
standard name (area_fraction). The standard_name alone is *not
meant to* uniquely identify a variable (you need other metadata
attributes to do this). <br>
<br>
2. All but 1 (prveg) of the 22 standard names listed were not
agreed until early November 2010. So the CMOR tables did not
include a standard name for these variables prior to that time.
[Note inclusion of the standard_name attribute is not required
for CF compliance.] If IPSL wrote this output before November
2010 (or subsequent to that time used out-dated CMOR tables),
then the standard_name attribute will not appear in their
files. <br>
<br>
Because of the above (and for many other reasons), a user should
be able to discover variables not only by searching on the
standard_name, but also the long_name or the variable name
itself (i.e., netCDF variable name). Does someone know whether
anyone is working on improving the search capability?<br>
<br>
We should at least make user's aware that only variables with
standard_names will appear in the current search.<br>
<br>
Best regards,<br>
Karl<br>
</font><br>
On 5/27/11 4:15 AM, <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>
wrote:
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B52119C41D@EXCHMBX01.fed.cclrc.ac.uk"
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:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-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;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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">I've noticed the mapping between
standard_name and variable name isn't 1-to-1 for some IPSL
data in the BADC Gateway. This may be a Gateway
configuration error or it might be a standard_name issue.
Details below:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The dataset
"cmip5.output1.IPSL.IPSL-CM5A-LR.historical.mon.land.Lmon.r4i1p1"
has 49 variables but only 18 show up on the faceted search.
If I investigate the Gateway database I see that :<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">* 10 variables are given the standard
name "area_fraction": <o:p> </o:p></p>
<p class="MsoNormal"> cropFrac c4PftFrac residualFrac
grassFrac landCoverFrac treeFracPrimEver treeFracPrimDec
treeFrac baresoilFrac c3PftFrac <o:p></o:p></p>
<p class="MsoNormal"> * 22 variables don't have a
standard_name: <o:p></o:p></p>
<p class="MsoNormal"> fLuc, fLitterSoil, nppWood, nep,
cSoilMedium, nppLeaf, fHarvest, rGrowth, nppRoot,
cLitterBelow, nbp, cSoilSlow, cRoot, cSoilFast, cLeaf,
prveg, cWood, rMaint, cLitterAbove, fFire, cMisc, cProduct<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is this how it should be?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Stephen.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas;">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas;">Stephen Pascoe +44 (0)1235 445980<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas;">Centre of Environmental Data
Archival<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas;">STFC Rutherford Appleton
Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<p>-- <br>
Scanned by iCritical. </p>
<br>
</blockquote>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>