FAAM - Cirrus and Anvils: European Satellite and Airborne Radiation measurements (CAESAR)

General Info

Title:	FAAM - Cirrus and Anvils: European Satellite and Airborne Radiation measurements (CAESAR)
Type:	Data Entity
Sub-Type:	Measurement
Abbreviation:	caesar
Publication State:	published
The publication state of this metadata: 'old' - for redundant records; 'working' - for new/in progress records; 'published' - for records approaching maturity, which may still change, but should be available via the discovery services; and 'Published' for mature records that are unlikely to change and should be available via the discovery services.

URI:	http://badc.nerc.ac.uk/view/badc.nerc.ac.uk__ATOM__dataent_caesar

Summary
A brief description of the data.

The CAESAR project aims to investigate the radiative properties of cirrus cloud over a wide range of wavelengths in combination with airborne in situ measurements of cirrus microphysical properties. Flights using the FAAM BAE-146 will observe frontal and anvil cirrus co-incident with the CloudSat Aqua-train and AATSR satellites over the Chilbolton cloud radars and lidars as well as ocean/sea surrounding the UK. Aircraft measurements will be used to obtain vertical and horizontal distribution of ice crystal size, shape and IWC during summer and winter periods.

Content
The actual data being described by this document. NB, in the case of data granules, this content may just be a reference to an ingested CSML or CDML file.

Introduction

The FAAM (Facility for Airborne Atmospheric Measurements) puts at the scientists' disposal a large atmospheric research aircraft (the BAE-146-301 aircraft) through a scheme of project selection and combined funding. It is run jointly by NERC and by the UK Met Office, and is one of the NERC Centres for Atmospheric Science (NCAS). The BADC is the FAAM designated data centre.

The CAESAR project aims to investigate the radiative properties of cirrus cloud over a wide range of wavelengths in combination with airborne in situ measurements of cirrus microphysical properties. Flights using the FAAM BAE-146 observed frontal and anvil cirrus co-incident with the CloudSat Aqua-train and AATSR satellites over the Chilbolton cloud radars and lidars as well as ocean/sea surrounding the UK. Aircraft measurements were used to obtain vertical and horizontal distribution of ice crystal size, shape and IWC during summer and winter periods. The winter FAAM campaign ran from 14 November 2005 17 December 2005 and the summer FAAM campaign ran from 3-17 May 2006.

Data availability and file format

Data collected onboard the FAAM Bae-146 aircraft is stored in the CAESAR archive at the BADC.

These data include both core and non-core data (for a definition of core data, see the document on FAAM Instruments).

FAAM processed core data are stored in NetCDF. Processed non-core data are stored in NetCDF or NASA Ames. Raw core data are stored in zipped VMS files. Some software to read, manipulate and convert these formats into each other are provided by the BADC (software directory in the FAAM archive) or other agencies.

CAESAR data are stored in either NetCDF or NASA Ames format.

File names follow the BADC file name convention and (for FAAM data) the FAAM file name convention.

Access Restrictions

Access to and use of the data are ruled by the CAESAR Data Protocol.

Access to the FAAM Bae-146 non-core data is now public, after having been restricted to the CAESAR participants during a period of time of 24 months following the last CAESAR flight, in agreement with the CAESAR data Protocol. All users are requested to acknowledge the data providers in any publication based on CAESAR data.
Authorised users of the Processed Bae-146 core data now include everyone. If you would like to access these data , please follow the access to FAAM Processed core data instructions online. Access is granted automatically once you have agreed online with the FAAM Conditions of Use.
Access to raw Bae-146 core data is restricted to the FAAM staff. If you are a FAAM instrument operator and would like to access these data, please follow the access to raw FAAM core data instructions online.

Note that CAESAR data users are still requested to contact the principal investigators prior to any use of the data. FAAM scientists may request acknowledgement (or joint authorship) in any publications based, using or quoting their data.

For more details on FAAM data restrictions, please see the FAAM Data Access Rules.

Chilbolton data have their own access conditions and must be applied for separately.

AATSR can be accessed through the NEODC.

Services and Links to further information

Services to CAESAR Campaign participants

A secure online workspace has been set up to facilitate the exchange of preliminary data amongst the CAESAR project team. This workspace is only accessible by invitation. If you require access, please contact the BADC help desk. This workspace, is separate from, and does not replace, the main data archive. All final, validated data will be archived in the CAESAR archive at the BADC.
CAESAR Data Providers Guide to submit data to the BADC Archive.
BADC NASA-Ames file checker
BADC NetCDF file checker

Documentation

Tables showing archive contents arranged by flight number/date and by campaign with links to the archive.
FAAM Flight Schedule - Calendar of past FAAM flights based on the data archived - Updated daily.
Tables showing which core parameters were measured for each flight.
List of FAAM campaigns, with links to the relevant BADC FAAM dataset details and specific data access conditions.
List of downloadable software packages to write, read and handle NetCDF files.

Links to further information

The Facility for Airborne Atmospheric Measurements (FAAM) Web site
AATSR data at the NEODC
Chilbolton Facility for Atmospheric and Radio Research (CFARR)

Citation

Date of citation

Who to contact

The NEON Principal Investigator is A. Keil (Met Office).
The FAAM Ops Manager is Maureen Smith.
Any query regarding the data should be sent to the BADC help desk.

Lineage
Summary of the origins of the dataset, e.g.: "Dataset produced from NASA MODIS instrument on Terra and collected at the University of York's groundstation 1999-2003 and a copy provided to NEODC in June 2007".

FAAM Data provided as is by FAAM CAESAR campaign participants as the campaign was underway.

Quality Statement
Description of the relative quality of the dataset.

Research data

Author
The principal author of the actual underlying data. Only one author can be specified per atom; if there are multiple authors, these should be specified as 'contributors'. NB, an atom MUST have an author specified.

Name	email
FAAM, Met Office

Contributors
Any other authors of the actual underlying data. NB, the principal author should be specified in the 'Author' input field. Also, note, three contributors can be added at once; after these are added a further three may be specified - and so on.

Name	email
A.J. Baran, Met Office

Online References
Online references with a specific relationship to the data being described here. NB, if links are supplied they must be valid and include the transport protocol - e.g. 'http://blah.co.uk'. Also, note, three online references can be added at once; after these are added a further three may be specified - and so on.

Relation	Title
Download	CAESAR Data Directory
Documentation	BADC Doc: List of FAAM Campaigns
Documentation	FAAM NERC website
Documentation	CAESAR Conditions of Use
Apply for access	Apply for access to CAESAR FAAM Core data
Logo	FAAM Logo

Parent Data Entity
Define the parent of this record. There should probably only be one parent, but this is not enforced.

No data specified at present

Sub Data Entities
Lists all entities which have the current entity as their parent.

None

Associated Deployments

Data Coverage
Summary of the temporal and spatial data coverage for the data.

Spatial coverage
Max Y: 55
Min X: -10	Max X 5
Min Y 45

Temporal coverage
Start Date:	2005-11-14
End Date:	2007-09-20

Spatial resolution

No spatial resoultion information available.

Vertical extent

No vertical extent information available.

Responsible Parties
Parties responsible for the metadata - e.g. data curator. Responsible parties can have a role specified to make their function clearer. Multiple responsible parties can be specified.

Role	Name	URI
Data Curator	badc.nerc.ac.uk	http://badc.nerc.ac.uk

Other Info
Other miscellaneous information. Note, update frequency relates to the update frequency of the underlying data, not the metadata.

Dataset language

English

Update frequency

notPlanned

Links and Services
	Downloadable XML version of this record

Not all information in this record may be rendered in this view. Please see the XML version for complete content

WARNING: You currently have javascript disabled. For these pages to work correctly, please enable javascript.