<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2>Hi
Bob,</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2>We are evaluating
how best to extract NetCDF metadata on our esg data node to reformulate into
METAFOR CIM documents. It seems obvious there are 3 possible sources of
this:</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2> 1. THREDDS
catalogues generated by esg publisher</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2> 2. The
Postgres database produced by esg publisher</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2> 3. The NetCDF
files themselves</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2>Looking at the
THREDDS xml generated on our data node it appears only selected metadata from
the NetCDF is exposed in the catalogue. I can see variable names,
standard_names and units with no global metadata. Is that what you
expect? I attach a catalogue for a small portion of
CMIP3.</FONT></SPAN></DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=809403211-04112009><FONT face=Arial size=2>I'm guessing that
with a correct configuration in esg.ini more metadata get's put in the
THREDDS xml but does this come from the NetCDF? Is there a way to
configure the publisher to put all NetCDF attributes in the THREDDS
xml?</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=809403211-04112009>Turning to the
Postgres database it appears to contain all attributes from the NetCDF. On
my system it also contains lots of Python object references that I assume is a
bug. For instance:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>esgcet=> select name, value from file_var_attr
limit 20;<BR> name
|
value
<BR>---------------+------------------------------------------------------------------<BR> axis
| Y<BR> bounds |
lat_bnds<BR> getitem | <built-in
method getitem of CdunifVariable object at
0x19f8150><BR> getslice | <built-in
method getslice of CdunifVariable object at
0x19f8150><BR> long_name |
latitude<BR> setitem | <built-in
method setitem of CdunifVariable object at
0x19f8150><BR> setslice | <built-in
method setslice of CdunifVariable object at 0x19f8150><BR> standard_name
| latitude<BR> units |
degrees_north<BR> getitem |
<built-in method getitem of CdunifVariable object at
0x19f8030><BR> getslice | <built-in
method getslice of CdunifVariable object at
0x19f8030><BR> setitem |
<built-in method setitem of CdunifVariable object at
0x19f8030><BR> setslice | <built-in
method setslice of CdunifVariable object at
0x19f8030><BR> axis
| X<BR> bounds |
lon_bnds<BR> getitem | <built-in
method getitem of CdunifVariable object at
0x19f8108><BR> getslice | <built-in
method getslice of CdunifVariable object at
0x19f8108><BR> long_name |
longitude<BR> setitem | <built-in
method setitem of CdunifVariable object at
0x19f8108><BR> setslice | <built-in
method setslice of CdunifVariable object at 0x19f8108><BR>(20
rows)<BR></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2>---</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Stephen Pascoe +44 (0)1235
445980</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>British Atmospheric Data
Centre</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Rutherford Appleton
Laboratory</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></BODY></HTML>