<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi all,<div><span class="Apple-tab-span" style="white-space:pre"> </span>apologies for cross-posting...</div><div><br>I'd like to start a discussion on how the DRS specification for CMIP5 model output (<a href="http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf">http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf</a>)<br>can be applied to observational datasets that will be made part of the same archive. A proposal based on recent workshops with PCMDI is detailed on this wiki page:<br><br><font class="Apple-style-span" color="#144FAE"><u><a href="http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets">http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets</a></u></font></div><div><font class="Apple-style-span" color="#144FAE"><u><br></u></font>As an example, the directory structure for the NASA AIRS dataset would look like this:<br><br><root directory>/cmip5/observations/nasa/aqua/airs/mon/atmos/ta/l3/vYYYYMMDD/<files><br><br>where:<br><br>"observations"=<product>, same as DRS "output1" or "output2"<br>"nasa"=<agency>, same as DRS "institute"<br>"aqua"=<mission>, replaces DRS "model"<br>"airs"=<instrument>, replaces DRS "experiment"<br>"l3"=<processing level>, replaces DRS "ensemble member"<br>vYYYYMMDD=the dated version, same as specified by the DRS<br><br>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.<br><br>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<br>and publishing these observations into the CMIP5 archive.<br><br>thanks in advance,<br><br>Luca<br><div><br></div></div></body></html>