BEAT-II Record: OMI_L2_OMUVB

Fields

The table below gives an overview of possible fields that can be returned from an ingestion of OMI_L2_OMUVB 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
timedouble[main]includedThe time of the measurement (in seconds since 2000-01-01 00:00:00)
latitudedouble[main]includedThe center latitude for a ground pixel
longitudedouble[main]includedThe center longitude for a ground pixel
corner_latitudedouble[main, 4]includedThe corner latitude values for a ground pixel
corner_longitudedouble[main, 4]includedThe corner longitude values for a ground pixel
uv_irradiance_surfacedouble[main]includedSurface UV irradiance
uv_irradiance_surface_descriptionstring includedindication of wavelength for which the surface UV irradiance is given and whether the clear_sky data was provided
solar_zenith_angle_wgs84double[main]excludedSolar zenith angle at WGS84 ellipsoid for center co-ordinate of the ground pixel

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
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.
time_mintime*Only include elements for which the value is greater than or equal to the provided filter option value
time_maxtime*Only include elements for which the value is less than or equal to the provided filter option value
timetime*Only include elements that match the list of given filter option values
latitude_mindoubleOnly include elements for which the value is greater than or equal to the provided filter option value
latitude_maxdoubleOnly include elements for which the value is less than or equal to the provided filter option value
latitudedoubleOnly include elements that match the list of given filter option values
longitude_mindoubleOnly include elements for which the value is greater than or equal to the provided filter option value
longitude_maxdoubleOnly include elements for which the value is less than or equal to the provided filter option value
longitudedoubleOnly include elements that match the list of given filter option values
uv_irradiance_surface_mindoubleOnly include elements for which the value is greater than or equal to the provided filter option value
uv_irradiance_surface_maxdoubleOnly include elements for which the value is less than or equal to the provided filter option value
uv_irradiance_surfacedoubleOnly include elements that match the list of given filter option values
solar_zenith_angle_wgs84_mindoubleOnly include elements for which the value is greater than or equal to the provided filter option value
solar_zenith_angle_wgs84_maxdoubleOnly include elements for which the value is less than or equal to the provided filter option value
solar_zenith_angle_wgs84doubleOnly include elements that match the list of given filter option values
uv_irradiance_surface_variantstringA single option value or combination (space separated) of two options values can be provided: When 'clear_sky' is selected the clear sky surface UV irradiance is ingested. To select the wavelength at wich the irradiance was retrieved use either '305nm', '308nm', '324nm', or '380nm' as option value

* Time values can be passed as either 'yyyy-mm-dd', 'yyyy-mm-ddThh:mm:ss', 'yyyy-mm-ddThh:mm:ss.uuuuuu' or a floating point value indicating the amount of seconds since 2000-01-01 00:00:00.

Mapping description

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

field namemapping description
time path/HDFEOS/SWATHS/UVB/Geolocation_Fields/Time[]
descriptionThe time converted from TAI93 to seconds since 2000-01-01T00:00:00
latitude path/HDFEOS/SWATHS/UVB/Geolocation_Fields/Latitude[]
longitude path/HDFEOS/SWATHS/UVB/Geolocation_Fields/Longitude[]
corner_latitude descriptionThe shape and size of each ground pixel is not included in the product. BEAT therefore provides its own approximation. The calculation is based on interpolation of the available center coordinates for each of the ground pixels. Each corner coordinate is determined by its four surrounding center coordinates. The corner coordinate is exactly at the intersection of the cross that can be made with these four points (each line of the cross is the minimal distance along the earth surface from one center coordinate to the other). In situations where a corner coordinate is not surrounded by four center coordinates (i.e. at the boundaries) virtual center coordinates are created by means of extrapolation. The virtual center coordinate is placed such that the distance to its nearest real center coordinate equals the distance between that nearest real center coordinate and the next center coordinate going further inwards. In mathematical notation: when c(i,m+1) is the virtual center coordinate and c(i,m) and c(i,m-1) are real center coordinates, then |c(i,m+1) - c(i,m)| = |c(i,m) - c(i,m-1)| and all three coordinates should lie on the same great circle. The four virtual coordinates that lie in the utmost corners of the boundaries are calculated by extrapolating in a diagonal direction (e.g. c(n+1,m+1) is calculated from c(n,m) and c(n-1,m-1))
corner_longitude descriptionThe shape and size of each ground pixel is not included in the product. BEAT therefore provides its own approximation. The calculation is based on interpolation of the available center coordinates for each of the ground pixels. Each corner coordinate is determined by its four surrounding center coordinates. The corner coordinate is exactly at the intersection of the cross that can be made with these four points (each line of the cross is the minimal distance along the earth surface from one center coordinate to the other). In situations where a corner coordinate is not surrounded by four center coordinates (i.e. at the boundaries) virtual center coordinates are created by means of extrapolation. The virtual center coordinate is placed such that the distance to its nearest real center coordinate equals the distance between that nearest real center coordinate and the next center coordinate going further inwards. In mathematical notation: when c(i,m+1) is the virtual center coordinate and c(i,m) and c(i,m-1) are real center coordinates, then |c(i,m+1) - c(i,m)| = |c(i,m) - c(i,m-1)| and all three coordinates should lie on the same great circle. The four virtual coordinates that lie in the utmost corners of the boundaries are calculated by extrapolating in a diagonal direction (e.g. c(n+1,m+1) is calculated from c(n,m) and c(n-1,m-1))
uv_irradiance_surface conditionuv_irradiance_surface_variant=305nm
path/HDFEOS/SWATHS/UVB/Data_Fields/Irradiance305[]
 
conditionuv_irradiance_surface_variant=310nm
path/HDFEOS/SWATHS/UVB/Data_Fields/Irradiance310[]
 
conditionuv_irradiance_surface_variant=324nm
path/HDFEOS/SWATHS/UVB/Data_Fields/Irradiance324[]
 
conditionuv_irradiance_surface_variant=380nm
path/HDFEOS/SWATHS/UVB/Data_Fields/Irradiance380[]
 
conditionuv_irradiance_surface_variant=clearsky 305nm
path/HDFEOS/SWATHS/UVB/Data_Fields/CSIrradiance305[]
 
conditionuv_irradiance_surface_variant=clearsky 310nm
path/HDFEOS/SWATHS/UVB/Data_Fields/CSIrradiance310[]
 
conditionuv_irradiance_surface_variant=clearsky 324nm
path/HDFEOS/SWATHS/UVB/Data_Fields/CSIrradiance324[]
 
conditionuv_irradiance_surface_variant=clearsky 380nm
path/HDFEOS/SWATHS/UVB/Data_Fields/CSIrradiance380[]
uv_irradiance_surface_description descriptionValue depends on uv_irradiance_surface_variant filter option
solar_zenith_angle_wgs84 path/HDFEOS/SWATHS/UVB/Geolocation_Fields/SolarZenithAngle[]