Result List
Get a list of Result objects. Results have a 1:1 mapping with Observations.
### Available end points:
- `/results/` - Will list all Results in the database
- `/results.json` - Will return all Results in json format
- `/results/<object_id>/` - Returns Results object with that id
### Available Methods:
- `GET`
- `HEAD`
### Available filters:
- `dataPath`
- `storageStatus`
- `storageLocation`
- `oldDataPath`
- `fileFormat`
- `observation`
### How to use filters:
`/results/?dataPath=/badc/weybourne/data/co2/`
`/results.json?dataPath=/badc/weybourne/data/co2/`
`/results/?fileFormat__icontains=netCDF`
GET /api/v2/results/?format=api&offset=1000
{ "count": 11555, "next": "https://api.catalogue.ceda.ac.uk/api/v2/results/?format=api&limit=100&offset=1100", "previous": "https://api.catalogue.ceda.ac.uk/api/v2/results/?format=api&limit=100&offset=900", "results": [ { "ob_id": 5635, "dataPath": "/badc/amma/data/ceh-aws", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "African Monsoon Multidisciplinary Analysis (AMMA) Project: Centre for Ecology & Hydrology (CEH) Automatic Weather Station", "uuid": "17bc31f2d028ae177afa18693dac5db1", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5634/?format=api" }, "volume": 21815526, "numberOfFiles": 12, "fileFormat": "Data are NetCDF formatted." }, { "ob_id": 5639, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5643, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5646, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5650, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5654, "dataPath": "/badc/amma/data/ceh-flux", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "African Monsoon Multidisciplinary Analysis (AMMA) Project: Centre for Ecology & Hydrology (CEH) Flux station", "uuid": "957a1f6de2d36ed257c6f62285dff048", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5653/?format=api" }, "volume": 19357789, "numberOfFiles": 11, "fileFormat": "Data are NetCDF formatted" }, { "ob_id": 5659, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5662, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5665, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5669, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5673, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5677, "dataPath": "/badc/amma/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\n\nThe AMMA archive maintained at the BADC contains data collected by the\nUK participants to AMMA (AMMA-UK). \n<!-- as well as satellite data to support\ntheir research.\n-->\nFor information on and access to data collected by other country members,\nand for satellite data archived in the UK, see the\n\"<a href=\"#links\">Links to further information</a>\" section below.\nAMMA-UK data archived at BADC include the following.\n</p><ul>\n<li>Routine observational data sourced in near real time form the Met Office (Amdars, Metars, Synop).\n</li><li>Near real time runs of the Met Office African limited area model (Africa-LAM).\n</li><li>Data from ground based flux stations (heat flux and, for some stations,\n CO<sub>2</sub> and H<sub>2</sub>O vapour fluxes).\n Files also include concomitant meteorological\n measurements (wind, temperature, pressure, humidity, rainfall) and soil\n physics parameters (soil temperature and moisture).\n\n</li><li>Data from sodars <!--and tethered balloons --> (UFAM instruments).\n</li><li>Data collected on board the FAAM Bae-146 aircraft in July-August 2006 (*).\n<!-- \n<li>Land-SAF data. &#150; Land surface geophysical products derived from\n Meteosat Second Generation (MSG) by the Satellite Application Facility\n (SAF).-->\n</li><li>Model fields.\n</li><li>Data from the <a href=\"http://badc.nerc.ac.uk/data/solas/projects/dodo.html\">DODO</a> and \n<a href=\"http://badc.nerc.ac.uk/data/dabex\"> DABEX</a> campaigns are available to AMMA participants.\n</li></ul>\n<p />\n\n<p class=\"right-shift\"><font size=\"-1\">(*)\nThe FAAM data include both core and non-core data (for a definition of\ncore data, see the document on\n<a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>).\n\n</font></p><p><font size=\"-1\">AMMA data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format.\nFile names follow the \n<a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the\n<a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n\n\n</font></p>\n</div>\n\n\n" }, { "ob_id": 5681, "dataPath": "/badc/CDs/ppsm/AVHRR1", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Polar Pathfinder Sampler (PPSM): AVHRR Polar Pathfinder 1.25 km data (1978-1996)", "uuid": "b2f21e4972c90504ed837367b06acc91", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5680/?format=api" }, "volume": 116715167, "numberOfFiles": 81, "fileFormat": "Image files are GIF formatted. Movie files are mpeg formatted.\r\n" }, { "ob_id": 5687, "dataPath": "/badc/CDs/ppsm/SSMI", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Polar Pathfinder Sampler (PPSM): SMMR and SSM/I Pathfinder brightness temperature data (1978-1987)", "uuid": "80a0863baa49f11c9c7ca7a570208346", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5686/?format=api" }, "volume": 20003184, "numberOfFiles": 66, "fileFormat": "Data are binary and HDR formatted. Images are GIF formatted." }, { "ob_id": 5691, "dataPath": "/badc/CDs/ppsm/PCUBE", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Polar Pathfinder Sampler (PPSM): Polar Pathfinder Products (P-Cube) data cube multi-sensor data at 100km resolution", "uuid": "541e6d4d071873e04703c7416e65e56e", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5690/?format=api" }, "volume": 215051714, "numberOfFiles": 750, "fileFormat": "Data are HDF formatted. Images are GIF formatted" }, { "ob_id": 5695, "dataPath": "/badc/CDs/ppsm/TOVS", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Polar Pathfinder Sampler (PPSM): TOVS Polar Pathfinder gridded daily and monthly Arctic atmospheric soundings (1979-1998)", "uuid": "5be973861dfc6055f64129577cf1f636", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5694/?format=api" }, "volume": 8030937, "numberOfFiles": 16, "fileFormat": "Data are HDF formatted. Movies are MPG formatted." }, { "ob_id": 5701, "dataPath": "/badc/ronoco/data/bae-146", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nData supplied by the RONOCO project team to the BADC are available via the \n<a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ronoco\">RONOCO archive</a>,\nfrom where they can be viewed and downloaded by authorised users (see below). This includes links to the FAAM data (core and non-core data - for a definition of core data, see the document on <a href=\"http://www.faam.ac.uk/public/instrumentation.html\">FAAM Instruments</a>) and model data (including Met Office Air Quality Unified Model data) to support the project.\n</p><p>\nFAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http;//badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>. Raw core data are stored in zipped VMS files. Some software to read, manipulate and convert these formats into each other are\nprovided by the BADC (software directory in the FAAM archive) or other agencies.\n</p>\n\n<p>RONOCO data are stored in either <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a> format. \n</p><p>File names follow the <a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a>\nand (for FAAM data) the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM file name convention</a>.\n</p>\n</div>\n\n" }, { "ob_id": 5705, "dataPath": "/badc/ronoco/data/aqum", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "RONOCO: AQUM (Air Quality in the Unified Model) images", "uuid": "f08bc2e99cac9794c6272635acccb13d", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5704/?format=api" }, "volume": 503643326, "numberOfFiles": 8270, "fileFormat": "Images are PNG formatted" }, { "ob_id": 5708, "dataPath": "/badc/ronoco/data/model-output-images", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "RONOCO: Chemistry model output images", "uuid": "28f2a7c61e3dbb61a3212d31e728ddb7", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5707/?format=api" }, "volume": 4265708263, "numberOfFiles": 15134, "fileFormat": "Images are PNG formatted" }, { "ob_id": 5711, "dataPath": "/badc/ukmo-nimrod/data/single-site/hameldon-hill/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Hameldon Hill C-band rain radar single polar products", "uuid": "e9912ec29933fe304297cdf018f16c88", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5710/?format=api" }, "volume": 572979282896, "numberOfFiles": 3229, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5714, "dataPath": "/badc/ukmo-nimrod/data/single-site/chenies/1km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Chenies C-band rain radar 1 km rainfall rate data", "uuid": "2be6f8a1d28171ca0ef95a4418bd1a46", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5713/?format=api" }, "volume": 1387357132, "numberOfFiles": 2308, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5717, "dataPath": "/badc/ukmo-nimrod", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>The NIMROD data is routinely and continuously updated at the BADC to present date.\n</p>\n<p>A calendar detailing data availability for the period 2003-2010 is also available from <a href=\"http://badc.nerc.ac.uk/data/nimrod/calendar.html\"> here</a></p> \n\n<p>The current situation is\nthat we are not able to fulfil requests for data that are missing from this archive. The data may be available at a cost by <a href=\"http://badc.nerc.ac.uk/reg/ukmo_contact.html\">contacting the Met Office directly</a> with required dates. It is worth contacting the BADC first to check if the reason for the gap is already identified as being due to the data not existing at all.</p>\n\n<h3>Data format </h3>\n\nNIMROD product data are in a non-standard binary format described in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/doc/Nimrod_File_Format_v1.7.pdf\">NIMROD format document</a>. <b>However,</b> the documentation does not indicate there are three 4 byte elements in each record. These are located before each block of data within the record, the first and second should be equal to 512 to confirm the size of the next data block; the third should be equal to twice the size of the data grid (e.g. if the data are in a grid 200 by 500 boxes, then this third entry should be 200,000) <p />\n\n<p> The BADC does not support reading software but programs written by the community to do this task in IDL, Matlab, FORTRAN and Python are available in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/software\">dataset software directory</a>. Those interested in importing to ArcGIS should see the <a href=\"http://alonaarmstrong.wordpress.com/radar/\">Lancaster ArcGIS page</a>.</p> \n\n<p> The data files contain integer precipitation rates in unit of (mm/hr)*32. Each value is between 0 and 32767. In practice it is rare to see a value in excess of 4096 i.e. 128 mm/hr.</p>\n\n<p> At 10:00 on 14 June 2005, the 1 km composite data files became larger with 2175 rows by 1725 columns compared to the previous 775 rows by 640 columns. From 14:55 on 30 August 2006, the 1 km composite data files are gzipped files. From 13 Nov 2007, the 1 km composite is derived directly from processed polar (600m x 1 degree) rain rate estimates and there is more detail in the rain structure. </p>\n\n<p> The raw polar data format is different and described in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/doc/Polar_File_Format.doc\"> polar data header format document</a>. The actual elevations of individual scans are recorded in the polar data files. The file names for the polar data follow the <a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a> but those for the normal data products do not. </p>\n</div>\n" }, { "ob_id": 5720, "dataPath": "/badc/ukmo-nimrod/data/single-site/wardon-hill/raw-dual-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Wardon Hill C-band rain radar dual polar products", "uuid": "910f888f47966082800a228a25ee76aa", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5719/?format=api" }, "volume": 6273912628296, "numberOfFiles": 7386, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5723, "dataPath": "/badc/ukmo-nimrod/data/single-site/predannack/1km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Predannack C-band rain radar 1 km rainfall rate data", "uuid": "2039ee8a46a62123a2d2fa033e9201d9", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5722/?format=api" }, "volume": 1481677775, "numberOfFiles": 2188, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5726, "dataPath": "/badc/ukmo-nimrod/data/single-site/jersey/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Jersey C-band rain radar single polar products", "uuid": "2fa373b69f5015339df43709e5c8b656", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5725/?format=api" }, "volume": 339263714249, "numberOfFiles": 1556, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details.\r\n" }, { "ob_id": 5729, "dataPath": "/badc/ukmo-nimrod/data/single-site/clee-hill/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Clee Hill C-band rain radar single polar products", "uuid": "0b937e45fd18e72e5b98e2f2a64ac905", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5728/?format=api" }, "volume": 769927814092, "numberOfFiles": 3497, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5732, "dataPath": "/badc/ukmo-nimrod", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>The NIMROD data is routinely and continuously updated at the BADC to present date.\n</p>\n<p>A calendar detailing data availability for the period 2003-2010 is also available from <a href=\"http://badc.nerc.ac.uk/data/nimrod/calendar.html\"> here</a></p> \n\n<p>The current situation is\nthat we are not able to fulfil requests for data that are missing from this archive. The data may be available at a cost by <a href=\"http://badc.nerc.ac.uk/reg/ukmo_contact.html\">contacting the Met Office directly</a> with required dates. It is worth contacting the BADC first to check if the reason for the gap is already identified as being due to the data not existing at all.</p>\n\n<h3>Data format </h3>\n\nNIMROD product data are in a non-standard binary format described in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/doc/Nimrod_File_Format_v1.7.pdf\">NIMROD format document</a>. <b>However,</b> the documentation does not indicate there are three 4 byte elements in each record. These are located before each block of data within the record, the first and second should be equal to 512 to confirm the size of the next data block; the third should be equal to twice the size of the data grid (e.g. if the data are in a grid 200 by 500 boxes, then this third entry should be 200,000) <p />\n\n<p> The BADC does not support reading software but programs written by the community to do this task in IDL, Matlab, FORTRAN and Python are available in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/software\">dataset software directory</a>. Those interested in importing to ArcGIS should see the <a href=\"http://alonaarmstrong.wordpress.com/radar/\">Lancaster ArcGIS page</a>.</p> \n\n<p> The data files contain integer precipitation rates in unit of (mm/hr)*32. Each value is between 0 and 32767. In practice it is rare to see a value in excess of 4096 i.e. 128 mm/hr.</p>\n\n<p> At 10:00 on 14 June 2005, the 1 km composite data files became larger with 2175 rows by 1725 columns compared to the previous 775 rows by 640 columns. From 14:55 on 30 August 2006, the 1 km composite data files are gzipped files. From 13 Nov 2007, the 1 km composite is derived directly from processed polar (600m x 1 degree) rain rate estimates and there is more detail in the rain structure. </p>\n\n<p> The raw polar data format is different and described in the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-nimrod/doc/Polar_File_Format.doc\"> polar data header format document</a>. The actual elevations of individual scans are recorded in the polar data files. The file names for the polar data follow the <a href=\"http://badc.nerc.ac.uk/help/file_naming.html\">BADC file name convention</a> but those for the normal data products do not. </p>\n</div>\n" }, { "ob_id": 5735, "dataPath": "/badc/ukmo-nimrod/data/composite/europe-5km", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "5 km Resolution Europe Composite Resolution Rainfall Data from the Met Office Nimrod System", "uuid": "d5ae8b92d8c884690592ce619f2eca07", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5734/?format=api" }, "volume": 35831071734, "numberOfFiles": 16861, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details. CEDA does not support reading software but programs written by the community to do this task in IDL, Matlab, FORTRAN and Python are available in the data software directory (see documentation links). \r\n\r\nHowever, the documentation does not indicate there are three 4 byte elements in each record. These are located before each block of data within the record, the first and second should be equal to 512 to confirm the size of the next data block; the third should be equal to twice the size of the data grid (e.g. if the data are in a grid 200 by 500 boxes, then this third entry should be 200,000).\r\n\r\n\r\n" }, { "ob_id": 5740, "dataPath": "/badc/ukmo-nimrod/data/single-site/deanhill/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Deanhill C-band rain radar single polar products", "uuid": "18f9d05e90171ecf31e5fc8db2903852", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5739/?format=api" }, "volume": 1176847453131, "numberOfFiles": 4559, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5743, "dataPath": "/badc/ukmo-nimrod/data/single-site/dudwick/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Hill of Dudwick C-band rain radar single polar products", "uuid": "bef432525debb41de6ff1c52e76cd03b", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5742/?format=api" }, "volume": 120151215000, "numberOfFiles": 878, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5747, "dataPath": "/badc/ukmo-nimrod/data/composite/uk-1km", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "1 km Resolution UK Composite Rainfall Data from the Met Office Nimrod System", "uuid": "27dd6ffba67f667a18c62de5c3456350", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5746/?format=api" }, "volume": 317880167313, "numberOfFiles": 7865, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details. However, the documentation does not indicate there are three 4 byte elements in each record. These are located before each block of data within the record, the first and second should be equal to 512 to confirm the size of the next data block; the third should be equal to twice the size of the data grid (e.g. if the data are in a grid 200 by 500 boxes, then this third entry should be 200,000)\r\n" }, { "ob_id": 5751, "dataPath": "/badc/ukmo-nimrod/data/single-site/wardon-hill/2km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Wardon Hill C-band rain radar 2 km rainfall rate data", "uuid": "fec3e0939484ebe85d64c02790d1fc40", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5750/?format=api" }, "volume": 335002577, "numberOfFiles": 580, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5754, "dataPath": "/badc/ukmo-nimrod/data/composite/uk-5km", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "5 km Resolution UK Composite Rainfall Data from the Met Office Nimrod System", "uuid": "f91b2c5399c5bf689e29bb15ab45da8a", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5753/?format=api" }, "volume": 45506919313, "numberOfFiles": 16847, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details. However, the documentation does not indicate there are three 4 byte elements in each record. These are located before each block of data within the record, the first and second should be equal to 512 to confirm the size of the next data block; the third should be equal to twice the size of the data grid (e.g. if the data are in a grid 200 by 500 boxes, then this third entry should be 200,000).\r\nThe data files contain integer precipitation rates in unit of (mm/hr)*32. Each value is between 0 and 32767. In practice it is rare to see a value in excess of 4096 i.e. 128 mm/hr." }, { "ob_id": 5757, "dataPath": "/badc/ukmo-nimrod/data/single-site/castor-bay/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Castor Bay C-band rain radar single polar products", "uuid": "1e4bfc8430b83fda8b66176a91a8a365", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5756/?format=api" }, "volume": 148685200333, "numberOfFiles": 1361, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details.\r\n" }, { "ob_id": 5761, "dataPath": "/badc/ukmo-nimrod/data/single-site/jersey/2km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Jersey C-band rain radar 2 km rainfall rate data", "uuid": "875eef122e8018e5d5b5a63a8b39dd23", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5760/?format=api" }, "volume": 3035433931, "numberOfFiles": 4398, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5764, "dataPath": "/badc/ukmo-nimrod/data/single-site/predannack/raw-dual-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Predannack C-band rain radar dual polar products", "uuid": "6c230fbe20db96c7ffe780910873a636", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5763/?format=api" }, "volume": 3206673757131, "numberOfFiles": 3785, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5767, "dataPath": "/badc/ukmo-nimrod/data/single-site/clee-hill/1km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Clee Hill C-band rain radar 1 km rainfall rate data", "uuid": "03533a4d4e4717f065a581545e9e928c", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5766/?format=api" }, "volume": 1706251214, "numberOfFiles": 2242, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5770, "dataPath": "/badc/ukmo-nimrod/data/single-site/chenies/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Chenies C-band rain radar single polar products", "uuid": "52ee93955ae57016edac453138cf5182", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5769/?format=api" }, "volume": 490538947531, "numberOfFiles": 2557, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details" }, { "ob_id": 5773, "dataPath": "/badc/ukmo-nimrod/data/single-site/crug-y-gorrllwyn/raw-polar/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Crug-y-Gorllwyn C-band rain radar single polar products", "uuid": "fd5f4aa5c87ab8735cc86c32a409f6e3", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5772/?format=api" }, "volume": 30716355480, "numberOfFiles": 149, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5777, "dataPath": "/badc/ukmo-nimrod/data/single-site/cobbacombe/1km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Cobbacombe Cross C-band rain radar 1 km rainfall rate data", "uuid": "e3b47eeee7a26ac85dbe922b2a753e40", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5776/?format=api" }, "volume": 1500785621, "numberOfFiles": 2246, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5780, "dataPath": "/badc/ukmo-nimrod/data/single-site/hameldon-hill/1km/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Hameldon Hill C-band rain radar 1 km rainfall rate data", "uuid": "c51faade69520b1838b90bad689ec83c", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5779/?format=api" }, "volume": 1686016978, "numberOfFiles": 2286, "fileFormat": "NIMROD product data are in the non-standard NIMROD binary format. Refer to linked documentation for further details." }, { "ob_id": 5784, "dataPath": "/badc/faam/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nThe <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_Flight_Schedule.html\">FAAM flights schedule</a> gives an overview\nof the past campaigns and test flights and the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_data_catalogue.html\">\narchive population table</a> shows which data files are present for each flight.\n</p>\nTo find out about core and non-core data, refer to the brief description of the different <a href=\"http://badc.nerc.ac.uk/data/faam/data-types.html\">types of FAAM data</a>.\n<p>FAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>, <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>\nor <a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT</a> formats.</p>\n<p>Raw core data are stored in zipped files.</p>\n<p>Some software to read, manipulate and convert these formats into each other are provided by the BADC (see <a href=\"#Doc\">\"Documentation and Tools\"</a> section\nbelow) or other agencies (see <a href=\"#Lin\">\"Links\"</a> section below).\n</p>\n<p>\nFile names follow the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM File Name Convention</a>.\n</p>\n\n<p>In Summer 2007 a linux-based processing system was introduced for the core processed data. In this new system <a href=\"http://badc.nerc.ac.uk/data/faam/newparameternames.html\">new descriptive names</a> were used for the core and core-cloud-physics variables replacing the old PARAxxxx style names.</p>\n</div>\n\n\n" }, { "ob_id": 5788, "dataPath": "/badc/faam/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nThe <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_Flight_Schedule.html\">FAAM flights schedule</a> gives an overview\nof the past campaigns and test flights and the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_data_catalogue.html\">\narchive population table</a> shows which data files are present for each flight.\n</p>\nTo find out about core and non-core data, refer to the brief description of the different <a href=\"http://badc.nerc.ac.uk/data/faam/data-types.html\">types of FAAM data</a>.\n<p>FAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>, <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>\nor <a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT</a> formats.</p>\n<p>Raw core data are stored in zipped files.</p>\n<p>Some software to read, manipulate and convert these formats into each other are provided by the BADC (see <a href=\"#Doc\">\"Documentation and Tools\"</a> section\nbelow) or other agencies (see <a href=\"#Lin\">\"Links\"</a> section below).\n</p>\n<p>\nFile names follow the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM File Name Convention</a>.\n</p>\n\n<p>In Summer 2007 a linux-based processing system was introduced for the core processed data. In this new system <a href=\"http://badc.nerc.ac.uk/data/faam/newparameternames.html\">new descriptive names</a> were used for the core and core-cloud-physics variables replacing the old PARAxxxx style names.</p>\n</div>\n\n\n" }, { "ob_id": 5791, "dataPath": "/badc/faam/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nThe <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_Flight_Schedule.html\">FAAM flights schedule</a> gives an overview\nof the past campaigns and test flights and the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_data_catalogue.html\">\narchive population table</a> shows which data files are present for each flight.\n</p>\nTo find out about core and non-core data, refer to the brief description of the different <a href=\"http://badc.nerc.ac.uk/data/faam/data-types.html\">types of FAAM data</a>.\n<p>FAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>, <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>\nor <a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT</a> formats.</p>\n<p>Raw core data are stored in zipped files.</p>\n<p>Some software to read, manipulate and convert these formats into each other are provided by the BADC (see <a href=\"#Doc\">\"Documentation and Tools\"</a> section\nbelow) or other agencies (see <a href=\"#Lin\">\"Links\"</a> section below).\n</p>\n<p>\nFile names follow the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM File Name Convention</a>.\n</p>\n\n<p>In Summer 2007 a linux-based processing system was introduced for the core processed data. In this new system <a href=\"http://badc.nerc.ac.uk/data/faam/newparameternames.html\">new descriptive names</a> were used for the core and core-cloud-physics variables replacing the old PARAxxxx style names.</p>\n</div>\n\n\n" }, { "ob_id": 5794, "dataPath": "/badc/faam/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nThe <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_Flight_Schedule.html\">FAAM flights schedule</a> gives an overview\nof the past campaigns and test flights and the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_data_catalogue.html\">\narchive population table</a> shows which data files are present for each flight.\n</p>\nTo find out about core and non-core data, refer to the brief description of the different <a href=\"http://badc.nerc.ac.uk/data/faam/data-types.html\">types of FAAM data</a>.\n<p>FAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>, <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>\nor <a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT</a> formats.</p>\n<p>Raw core data are stored in zipped files.</p>\n<p>Some software to read, manipulate and convert these formats into each other are provided by the BADC (see <a href=\"#Doc\">\"Documentation and Tools\"</a> section\nbelow) or other agencies (see <a href=\"#Lin\">\"Links\"</a> section below).\n</p>\n<p>\nFile names follow the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM File Name Convention</a>.\n</p>\n\n<p>In Summer 2007 a linux-based processing system was introduced for the core processed data. In this new system <a href=\"http://badc.nerc.ac.uk/data/faam/newparameternames.html\">new descriptive names</a> were used for the core and core-cloud-physics variables replacing the old PARAxxxx style names.</p>\n</div>\n\n\n" }, { "ob_id": 5798, "dataPath": "/badc/faam/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>\nThe <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_Flight_Schedule.html\">FAAM flights schedule</a> gives an overview\nof the past campaigns and test flights and the <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/faam/doc/FAAM_data_catalogue.html\">\narchive population table</a> shows which data files are present for each flight.\n</p>\nTo find out about core and non-core data, refer to the brief description of the different <a href=\"http://badc.nerc.ac.uk/data/faam/data-types.html\">types of FAAM data</a>.\n<p>FAAM processed core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\nProcessed non-core data are stored in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>, <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames</a>\nor <a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT</a> formats.</p>\n<p>Raw core data are stored in zipped files.</p>\n<p>Some software to read, manipulate and convert these formats into each other are provided by the BADC (see <a href=\"#Doc\">\"Documentation and Tools\"</a> section\nbelow) or other agencies (see <a href=\"#Lin\">\"Links\"</a> section below).\n</p>\n<p>\nFile names follow the <a href=\"http://badc.nerc.ac.uk/data/faam/file-names.html\">FAAM File Name Convention</a>.\n</p>\n\n<p>In Summer 2007 a linux-based processing system was introduced for the core processed data. In this new system <a href=\"http://badc.nerc.ac.uk/data/faam/newparameternames.html\">new descriptive names</a> were used for the core and core-cloud-physics variables replacing the old PARAxxxx style names.</p>\n</div>\n\n\n" }, { "ob_id": 5803, "dataPath": "/badc/CDs/aaoe87/aaoe87/data/sonde/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Ozonesondes data from Antarctic stations during the Airborne Antarctic Ozone Experiment (AAOE-87) Project", "uuid": "0d796add4a5c4e309a9a9be8ce0c283d", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5802/?format=api" }, "volume": 1984770, "numberOfFiles": 245, "fileFormat": "Data are MS-DOS ASCII formatted." }, { "ob_id": 5808, "dataPath": "/badc/CDs/aaoe87/aaoe87/data/er2/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Airborne data from mounted in-situ instruments on board the NASA ER-2 aircraft during the Airborne Antarctic Ozone Experiment (AAOE-87) Project", "uuid": "979060734dbe57c5027963dc931a1393", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5807/?format=api" }, "volume": 64642950, "numberOfFiles": 290, "fileFormat": "Data are MS-DOS ASCII formatted." }, { "ob_id": 5811, "dataPath": "/badc/CDs/aaoe87/aaoe87/data/dc8/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Airborne data from mounted in-situ instruments onboard the NASA DC-8 aircraft during the Airborne Antarctic Ozone Experiment (AAOE-87) Project", "uuid": "06924fa8e2fe565447677d2cc023e8e0", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5810/?format=api" }, "volume": 51521943, "numberOfFiles": 177, "fileFormat": "Data are MS-DOS ASCII formatted." }, { "ob_id": 5815, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5818, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5821, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5824, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5827, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5830, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5833, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5836, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5839, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5842, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5845, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5848, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5851, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5854, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5857, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5860, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5863, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5866, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5869, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5872, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5875, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5878, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5881, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5884, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5887, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5890, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5893, "dataPath": "/badc/itop/data/forecasts_and_analyses/ecmwf", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "UTLS-Ozone ITOP: ECMWF boundary layer, convective precipitation and cloud level forecast model output", "uuid": "b87fc6b2f94df6b4c621e2c4a52e1135", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5892/?format=api" }, "volume": 216059299, "numberOfFiles": 5379, "fileFormat": "Images are PNG formatted" }, { "ob_id": 5895, "dataPath": "/badc/itop/data/forecasts_and_analyses/tomcat", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "UTLS-Ozone ITOP: TOMCAT atmospheric CO, NOX and O3 trajectory model output", "uuid": "3f9d45db58e81d71535a2484439d50b2", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5894/?format=api" }, "volume": 552726375, "numberOfFiles": 1345, "fileFormat": "Data are ASCII formatted. Plots are PNG formatted" }, { "ob_id": 5898, "dataPath": "/badc/itop", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and file format</div>\n<p>\n\nThe ITOP-UK data set includes\n</p><ul>\n<li>Trajectories and other forecast products calculated by John Methven\n (University of Reading),\n based on ECMWF forecast wind fields, to support ICARTT flight planning.\n\n</li><li>Near-real-time chemical analyses produced by the University of Cambridge\n using the pTOMCAT chemical transport model.\n\n</li><li>Data collected onboard the <a href=\"http://www.faam.ac.uk/\">FAAM</a>\n\n Bae-146 aircraft during the ITOP campaign (12 July - 3 August 2004).\n These data include both core and non-core data.\n A list of currently available\n <a href=\"http://badc.nerc.ac.uk/data/itop/flight_data.html\">flight data</a>\n is provided.\n</li></ul>\n<p />\n\n\n\n<p>\nAccess to the processed BAe-146 core data is public and ruled by the\n<a href=\"http://badc.nerc.ac.uk/data/faam/faam-data-protocol.pdf\">FAAM Data Protocol</a>.\n\n\nAccess to the raw BAe-146 core data is restricted to FAAM staff.\n</p>\n<p>\nOther ITOP-UK data, i.e. the forecast products and the Bae-146 non-core data,\nare now public (with signature of the Met Office agreement required for the\nforecasts), after having been restricted to the UTLS-Ozone and ICARTT participants\nduring a period of time of 2 years after the last flight, in agreement with the\n<a href=\"http://badc.nerc.ac.uk/data/utls-ozone/utls-protocol.html\">UTLS-Ozone Data Protocol</a>.\n</p>\n\nITOP data are stored in either\n<a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a> or ICARTT ASCII format\n(<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a>\n\nupdated as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>, pp. 8-17).\n<br />\nData file names follow the ICARTT file name convention as described in the\n<a href=\"http://badc.nerc.ac.uk/data/itop/DataManagement_plan.pdf\">ICARTT Data Management Implementation Plan</a>\n(pp. 7-8) but the launch number <i><b>L#</b></i> is replaced by the FAAM flight number.\n\n\n</div>\n" }, { "ob_id": 5902, "dataPath": "/badc/CDs/sam2/SAM2DATA", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Stratospheric Aerosol Measurement II (SAM II): Polar Arctic and Antarctic Aerosol Extinction Profiles", "uuid": "20959cc60f1dda630df224d73e7b5d8c", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5901/?format=api" }, "volume": 496200627, "numberOfFiles": 362, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 5914, "dataPath": "/badc/higem/data/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "High Resolution Global Environmental Model runs", "uuid": "31ec814776e84ff9c4cfbe7a035cf5de", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/5913/?format=api" }, "volume": 108044479687514, "numberOfFiles": 290226, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data, file format and software</div>\n<p>\n</p><p>Access to the HiGEM data sets is available via the <a href=\"http://badc.nerc.ac.uk/browse/badc/higem\">HiGEM\ndata browser directory</a>. Alternatively you can ftp the data from ftp.ceda.ac.uk.</p>\n\n\n<p>Software is available to manipulate and view the HadCM3 data.\n<a href=\"http://badc.nerc.ac.uk/help/software/xconv\">swapbytes</a> can be used to byte swap\npp files from the COAPEC dataset if necessary. \n<a href=\"http://badc.nerc.ac.uk/help/software/xconv\">xconv</a> provides an easy to use point\nand click interface to the data. \n<a href=\"http://www.met.reading.ac.uk/~jeff/xconv/appx1.html\">convsh</a>\nprovides a subset of the functionality of xconv, but in a scriptable\nform, so it can be used to automate some common data processing tasks.\nJeff Cole at CGAM Reading, who developed both xconv and convsh, \nprovides some example uses of\n<a href=\"http://www.met.reading.ac.uk/~jeff/xconv/appx2.html\">convsh</a></p>\n\n<p>\nA <a href=\"http://badc.nerc.ac.uk/data/higem/summary.html\">summary of HiGEM data</a> held at the BADC with links to webpages showing\nand the evolution of certain key parameters is available to HiGEM participants.\nDetails of previous HiGEM simulations can be found \n<a href=\"http://www.higem.nerc.ac.uk/science/status.php\">here</a>.\nThe HiGEM simulations archived at the BADC are at N144 Atmosphere resolution (1.25 lat x 0.83 lon) \nand 1/3 degree ocean resolution. The HiGEM simulations have 38 vertical levels in the atmosphere \nand 40 vertical levels in the ocean.\n</p>\n\n<p>A suite of example datasets are also available to HiGEM partners, these include:\n</p><ul>\n<li><a href=\"http://badc.nerc.ac.uk/data/higem/hadcm3l30.html\">HadCM3(L30)</a> - a 100 year integration of a version of the \nHadCM3 AOGCM, but with 30, instead of 19, atmospheric levels\n</li><li><a href=\"http://badc.nerc.ac.uk/data/higem/hadcm3ctl.html\">HadCM3 control integration</a> - 100 year and 1000 year \ndatasets from the Hadley Centre supplied to the NERC COAPEC thematic programme.\n</li><li><a href=\"http://badc.nerc.ac.uk/data/higem/hadceml.html\">HadCEML integration</a> - 100 year datasets of the HadCEML model\nfrom the Hadley Centre .\n</li></ul>\n<p />\nThe current status of the HiGEM dataset at the BADC can be found <a href=\"http://badc.nerc.ac.uk/data/higem/status.html\">here</a>\n<p>The HIGEM data file format is as follows:\n</p><ul>\n <li> HiGEM simulations are held as 32 bit UM pp files.\n </li><li> HadCM3(L30) data are held as 64 bit UM fields files\n </li><li> HadCM3 control data are held as 32 bit pp files\n </li><li> HadCM3 control data from the Beowulf cluster are held as NetCDF files\n </li><li> HadCEML data held as both NetCDF and pp files.\n</li></ul>\n\n\n</div>\n" }, { "ob_id": 6029, "dataPath": "/badc/ndsc/data/ncep", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Network for the Detection of Atmospheric Composition Change (NDACC): Numerical Model Output from stations", "uuid": "460eca4f010bbebf25c8027bf1c8b4ef", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6028/?format=api" }, "volume": 731828289, "numberOfFiles": 21437, "fileFormat": "Data are NMC formatted" }, { "ob_id": 6051, "dataPath": "/badc/ndsc/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data and File format</div>\n<p>\n\nA list of\n<a href=\"http://www.ndsc.ncep.noaa.gov/data/data_tbl/\" target=\"_top\">current\narchived data</a> in the NDACC database is available.\nData that are less than two years old are still restricted to NDACC\ninvestigators.\nPublic data can be directly downloaded from the BADC archive <i>via</i> the Web\nor by <i>anonymous ftp</i>. You can browse the NDACC\n<a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ndsc/data/\">archive</a> held\nat BADC.\nMirroring of the NDACC archive is performed daily by BADC.\n</p>\n<p>\nThe BADC holds NDACC data in NASA Ames format &#151;\nan ASCII based file format which incorporates a number of self\ndescribing data formats.\nEach file not only includes information on the format (necessary to read the\ndata), but also general information needed to understand and interpret the data\n(how the data have been generated, their units, etc).\nA contact name is given in each file.\nThis file format, which has been used\nby a number of measurement campaigns, is documented at BADC in the\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA Ames Format</a> page, based on the document\nwritten by\n<a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/G-and-H-June-1998.html\">S.E. Gaines and R.S.\nHipskind</a>.\n</p>\n<p>\nA <a href=\"http://badc.nerc.ac.uk/data/ndsc/acquiring.html\">guide</a> is available to help you\nretrieving the data. <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ndsc/software/\">Software</a>\n\nis also provided to read the data.\n</p><p /></div>\n" }, { "ob_id": 6054, "dataPath": "/badc/ndsc/data/stations", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Network for the Detection of Atmospheric Composition Change (NDACC): Stations data", "uuid": "bbe18bccf5ea108582f722ef0b243a41", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6053/?format=api" }, "volume": 124217069904, "numberOfFiles": 318690, "fileFormat": "Data are NASA Ames formatted" }, { "ob_id": 6058, "dataPath": "/badc/utls/data/cirrus", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\nThe UTLS CIRRUS data is available in the BADC <a href=\"http://badc.nerc.ac.uk/browse/badc/utls/data/cirrus\">UTLS-CIRRUS archive</a>. It contains processed core data collected from April to August 2005 on board the <a href=\"http://badc.nerc.ac.uk/data/faam/\">FAAM BAe-146 aircraft</a>. The data are in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\n</p><p>Non-core data is also available for the same period. Those data are in <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA-Ames</a>.\n</p><p /></div>\n" }, { "ob_id": 6061, "dataPath": "/badc/utls/data/cirrus", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\nThe UTLS CIRRUS data is available in the BADC <a href=\"http://badc.nerc.ac.uk/browse/badc/utls/data/cirrus\">UTLS-CIRRUS archive</a>. It contains processed core data collected from April to August 2005 on board the <a href=\"http://badc.nerc.ac.uk/data/faam/\">FAAM BAe-146 aircraft</a>. The data are in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\n</p><p>Non-core data is also available for the same period. Those data are in <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA-Ames</a>.\n</p><p /></div>\n" }, { "ob_id": 6064, "dataPath": "/badc/utls/data/cirrus", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\nThe UTLS CIRRUS data is available in the BADC <a href=\"http://badc.nerc.ac.uk/browse/badc/utls/data/cirrus\">UTLS-CIRRUS archive</a>. It contains processed core data collected from April to August 2005 on board the <a href=\"http://badc.nerc.ac.uk/data/faam/\">FAAM BAe-146 aircraft</a>. The data are in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\n</p><p>Non-core data is also available for the same period. Those data are in <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA-Ames</a>.\n</p><p /></div>\n" }, { "ob_id": 6067, "dataPath": "/badc/utls/data/cirrus", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Availability of data</div>\n<p>\nThe UTLS CIRRUS data is available in the BADC <a href=\"http://badc.nerc.ac.uk/browse/badc/utls/data/cirrus\">UTLS-CIRRUS archive</a>. It contains processed core data collected from April to August 2005 on board the <a href=\"http://badc.nerc.ac.uk/data/faam/\">FAAM BAe-146 aircraft</a>. The data are in <a href=\"http://badc.nerc.ac.uk/help/formats/netcdf/\">NetCDF</a>.\n</p><p>Non-core data is also available for the same period. Those data are in <a href=\"http://badc.nerc.ac.uk/help/formats/NASA-Ames/\">NASA-Ames</a>.\n</p><p /></div>\n" }, { "ob_id": 6071, "dataPath": "/badc/ukmo-gosta/data/gisst/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Global sea-Ice and Sea Surface Temperature (GISST2.3b) anomalies (1871-2003)", "uuid": "baea7ca09988fead898232b4bda9eea5", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6070/?format=api" }, "volume": 720527592, "numberOfFiles": 153, "fileFormat": "ASCII" }, { "ob_id": 6074, "dataPath": "/badc/ukmo-gosta/data/gice/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Global sea-Ice Content (GICE2.3b) anomalies (1871-2003)", "uuid": "dadcfc64a08d59d81cfb2fc9be7ed7ad", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6073/?format=api" }, "volume": 108141034, "numberOfFiles": 139, "fileFormat": "ASCII\r\n" }, { "ob_id": 6077, "dataPath": "/badc/ukmo-gosta/data/mohmatn4/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Monthly Gridded Met Office Historical Marine Air Temperature (MOHMATN4) anomalies (1856-2006)", "uuid": "365e5e62328975643e320d418bc34e95", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6076/?format=api" }, "volume": 32323612, "numberOfFiles": 157, "fileFormat": "Data are ASCII formatted\r\n\r\n" }, { "ob_id": 6080, "dataPath": "/badc/ukmo-gosta/data/mohsst6/", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Monthly Gridded Met Office Historical Sea-Surface Temperature (MOHSST6) anomalies (1856-2006)", "uuid": "2291d3582cab3293b615ae0ee1ece5bd", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6079/?format=api" }, "volume": 31956300, "numberOfFiles": 158, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 6091, "dataPath": "/badc/mamm/data/faam-flights/b809-2013-sep-23/non-core", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": null, "volume": 0, "numberOfFiles": 0, "fileFormat": null }, { "ob_id": 6094, "dataPath": "/badc/ukmo-wind-prof/data/camborne", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 915MHz vertical wind profiler measurements at Camborne, UK (1998 - 2012)", "uuid": "1492abad564e4127bab3175504566819", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6093/?format=api" }, "volume": 1798483066, "numberOfFiles": 3409, "fileFormat": "Data are ASCII formatted\r\n\r\n" }, { "ob_id": 6098, "dataPath": "/badc/ukmo-wind-prof/data/dunkeswell", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 1290 MHz vertical wind profiler measurements at Dunkeswell, UK (1999 - 2012)", "uuid": "253b168c06406f962f4920857987c525", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6097/?format=api" }, "volume": 1418106988, "numberOfFiles": 4188, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 6101, "dataPath": "/badc/ukmo-wind-prof/data/wattisham", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 1290 MHz vertical wind profiler measurements at Wattisham, UK (2001 - 2010)", "uuid": "a211f706bda9cd1d4ab141cd29cec8d5", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6100/?format=api" }, "volume": 1463438414, "numberOfFiles": 3610, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 6104, "dataPath": "/badc/ukmo-wind-prof/data/south-uist64", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: 64 MHz ST vertical wind profiler measurements at South Uist, UK (2004 - 2012)", "uuid": "3ca88ef5aca50e29b257ffaff3a047ab", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6103/?format=api" }, "volume": 963615462, "numberOfFiles": 1977, "fileFormat": "<div property=\"cedacat:formats\">\n<div class=\"formats\">Data availability and file format</div>\n<p>These instruments make observations in two interlaced modes; the low mode covers the approximate altitude range 0.1 - 2.0 km at 0.1 km intervals, and the high mode covers the approximate altitude range 0.2 - 8.0 km at 0.2 km intervals. The useful altitude coverage varies with atmospheric conditions and only extends significantly above 2 km when precipitation is present. Although the cycle time for observations is of the order of a few minutes, the data used by the Met Office represent \"consensus averages\" over 30 minutes.</p>\n\n\n<p>The <a href=\"http://badc.nerc.ac.uk/cgi-bin/data_browser/data_browser/badc/ukmo-wind-prof/\">data held at the BADC</a>, are stored in a simple ASCII format (plain text and \"human\" readable). A <a href=\"http://badc.nerc.ac.uk/data/ukmo-wind-prof/file_format.html\">detailed description</a> of the file structure \nis available.</p></div>\n\n\n" }, { "ob_id": 6109, "dataPath": "/badc/ukmo-wind-prof/data/isleofman", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 915MHz vertical wind profiler measurements at Isle of Man, UK (2005 - 2012)", "uuid": "a20a19eaea281b50d333f3225e8115a4", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6108/?format=api" }, "volume": 892452953, "numberOfFiles": 1503, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 6112, "dataPath": "/badc/ukmo-wind-prof/data/capel-dewi", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 915 MHz vertical wind profiler measurements at Capel Dewi, UK (1999 - 2002)", "uuid": "e63cba90f831f00e9f32319422dc834d", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6111/?format=api" }, "volume": 185947753, "numberOfFiles": 862, "fileFormat": "Data are ASCII formatted\r\n" }, { "ob_id": 6115, "dataPath": "/badc/ukmo-wind-prof/data/south-uist915", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "Met Office: Vaisala Radian LAP3000 915 MHz vertical wind profiler measurements at South Uist, UK (2003 - 2004)", "uuid": "9987917bd2c7ec13cd91df4b82a10fb0", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6114/?format=api" }, "volume": 126130906, "numberOfFiles": 549, "fileFormat": "Data are ASCII formatted" }, { "ob_id": 6119, "dataPath": "/badc/mst/data/mst-products-v0", "oldDataPath": [], "storageLocation": "internal", "storageStatus": "online", "observation": { "title": "NERC Mesosphere-Stratosphere-Troposphere (MST) Radar version 0 data products", "uuid": "ef91b8184e0b44f66d89ed985c81ceb2", "ob_id": "https://api.catalogue.ceda.ac.uk/api/v2/observations/6118/?format=api" }, "volume": 36800889681, "numberOfFiles": 46162, "fileFormat": null } ] }