The NOAA/ESRL/GML/HATS group has assembled in one place
trace gas measurements from its entire three decade history of involvement in cooperative airborne measurement campaigns.
These data have always, for the most part, been available from several archive sites accessible to the public where
they are kept in a despersed form under multiple campaign umbrellas and their associated research flights. Links to
these archive sites are available at the campaign acronyms listed below. Links to overview descriptions of the
science objectives targeted during each campaign are available from the
HATS Airborne Projects page.
Typically, cooperating researchers are responsible for the data from one or more instrument systems that they build
and maintain themselves, and the data that each system produces arrives at the campaign archive in standalone form
divided among individual research flights. Each instrument team also customarily offers only a sychronized time vector
for matching with the data streams from other instruments. As such, measurement placement and sychronization on a flight
by flight basis is a cumbersome process.
Fortunately, we have done much of this work already and packaged HATS system trace gas measurements
from all reported flights of all of the airborne campaigns we have had the privilege to be involved
in since 1991 into a single HATS airborne data file.
The measurements available in the this file are currently limited to those from the
UCATS, and NWAS-PFP
systems, with navigational and atmospheric state parameters supplied by platform operators. The data are stored
in a simple text format with comma-separated values. Because no HATS system measures all of the parameters
reported in this file at the same time, much of the actual storage space required for the file is reserved for
missing values. Future releases will seek to curtail this problem and speed up access with the implementation
of a better organized and more robust storage format that will also include measurement uncertainty estimates
where appropriate and available. These have been left out for now owing to the practical limitations of the csv
The following is a list of the parameters supplied in order of ascending column number:
Mission/Platform (no units, char, campaign name and platform type)
MissionIndex (sequence number, integer)
DeploymentIndex (sequence number, integer, for multi-part missions)
FlightDate (UTC, yyyymmdd, date of takeoff)
FlightType (no units)
daysec (UTC, int, seconds since midnight of takeoff date)