All measurements collected during the MAPM field campaign are made publicly available in well documented netCDF format. To allow a diverse non-scientific user community to also access the data, we are also aiming to provide Excel files of the data. However, not all data are currently available in an excel format.
The campaign team is working on a peer-reviewed publication which will describe in detail the data sets collected through the measurement campaign and all subsequent processing of those data. Some information on the individual data sets is also provided in the sub-pages of this page.
Available data sets
Data are available from two different particulate matter sensors: (i) ES-642 sensors which are high-quality particulate matter sensors also used as part of Christchurch’s operational monitoring system and (ii) from small, inexpensive Outdoor Dust Information Nodes (ODINs). Furthermore, meteorological observations were collected using three automatic weather stations deployed specifically for the measurement campaign and by launching 12 balloon-borne radiosondes that provided vertical profiles of temperature, pressure and humidity through the atmosphere.
Particulate matter measurements
Downloading MAPM campaign data
If you wish to use any MAPM data please email email@example.com and let us know which data set you would like to download and what your intended use of the data is. You will then receive a link and a password that can be used to login to our ftp server. You will also receive updates if an improved version of the data you are using becomes available.
The campaign data are made freely available for non-commercial use under the Creative Commons Attribution Non Commercial Share Alike 4.0 International license.
File naming convention for campaign data
The file names for all MAPM field campaign data follow the same naming convention , i.e. <Instrument_type>_<Instrument_ID>_Christchurch2019_<‘Colocation1/2’ or ‘Deployment’>_<locX>_<raw or version number>.nc. In this way the filename provides the following information about the data contained in the file:
Instrument_type: Type of the instrument, for example ES-642 or ODIN for the particulate matter instruments.
Instrument_ID: Number or name of specific instrument/observing site.
Colocation_1/2 or Deployment: This identifier is only required for the PM2.5 measurements (i.e. not for automatic weather stations or radiosondes) and should allow a quick overview of which part of the campaign the data are from, i.e.
- Colocation_1 – pre-campaign inter-calibration at the Woolston site.
- Deployment – time frame in which the sensors where distributed around Christchurch.
- Colocation_2 – post-campaign inter-calibration at the Woolston site.
locX: should only be added to files when the instrument was moved during the campaign (this should only apply to a few instruments).
raw or version number: Raw means any data set which has had no correction applied (however, quality flags are given), while data with a version number have had corrections applied to the raw data. Not every instrument has a data set with a version number, but raw data are provided for all instruments.