BEAT-II Record: GOMOS_CRS_AX_o3

Fields

The table below gives an overview of possible fields that can be returned from an ingestion of GOMOS_CRS_AX_o3 data. The 'default' column indicates whether the specified data item is included in the ingestion by default or not. You can change which data items are ingested by making use of the include and exclude filter options (see below).

field nametypedimensionsdefaultdescription
typestring includedreference to the type of data in this record
elements_per_fileint32[file]included
cross_section_o3double[main, spectra]included
cross_section_o3_unitstring includedcm^2
wavelength_per_filedouble[file, spectra]includedThe nominal wavelength assignment
wavelength_per_profile_unitstring includednm
temperaturedouble[main]included

Ingestion filter options

Ingestion filter options are passed as a ',' or ';' separated string to the ingestion function. Each filter option needs to be formulated as option_name=value[ value value] (some options accept more than one value). For example, if a product has filter options 'altitude_min' and 'time_min' you can provide a filter option string "latitude_min=30,time_min=2003-01-01" to get all measurements at or above 30km and on or after January 1st 2003.

option nametypedescription
product_versionintegerIf multiple product format versions for this product type exist, you can use this filter option to select from which ones data should be ingested (i.e. you can provide a space-separated list of allowed product format version numbers). The list of available version numbers for this product type can be found in the CODA Product Format Definitions documentation.
datastringYou should never have to provide this filter option, since this type of record is the default type of data that is ingested for a GOMOS_CRS_AX product. You can, however, still explicitly ask for this type of record by using the filter option data=o3.
includestringProvide a space-separated list of field names to ingest additional data items (i.e. fields that are not ingested by default). You can use the special case include=* to indicate that you want to ingest all available data items.
excludestringProvide a space-separated list of field names that you don't want ingested. Mind that the exclude filter is processed after the include filter.
temperature_mindoubleOnly include elements for which the value is greater than or equal to the provided filter option value
temperature_maxdoubleOnly include elements for which the value is less than or equal to the provided filter option value
temperaturedoubleOnly include elements that match the list of given filter option values
wavelength_mindoubleOnly include data where the wavelength is greater then or equal to the value provided (in nm)
wavelength_maxdoubleOnly include data where the wavelength is less than or equal to the value provided (in nm)

Mapping description

Below a description is provided on how each data item in the ingested record was retrieved from the product.

field namemapping description
cross_section_o3 path/crs_o3_cross_sect_spa_mds[]/cross_sec[], /crs_o3_cross_sect_spb_mds[]/cross_sec[]
descriptionthe cross section data for the ozone for band A and band B is concatenated
cross_section_o3_unit descriptionWill be set to "cm^2"
wavelength_per_file path/crs_o3_cross_sect_spa_gads[0].spec_grid[], /crs_o3_cross_sect_spb_gads[0].spec_grid[]
descriptionthe wavelength data for band A and band B is concatenated
wavelength_per_profile_unit descriptionWill be set to "nm"
temperature path/crs_o3_cross_sect_spa_mds[]/temp, /crs_o3_cross_sect_spb_mds[]/temp
descriptiontemperature will be in Kelvin