BEAT-II Record: OMI_L2_OMAERUV

Fields

The table below gives an overview of possible fields that can be returned from an ingestion of OMI_L2_OMAERUV 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 name	type	dimensions	default	description
type	string		included	reference to the type of data in this record
time	double	[main]	included	The time of the measurement (in seconds since 2000-01-01 00:00:00)
latitude	double	[main]	included	The center latitude for a ground pixel
longitude	double	[main]	included	The center longitude for a ground pixel
corner_latitude	double	[main, 4]	included	The corner latitude values for a ground pixel
corner_longitude	double	[main, 4]	included	The corner longitude values for a ground pixel
aerosol_optical_depth	double	[main]	included	Aerosol Optical Depth
aerosol_optical_depth_description	string		included	indication of wavelength for which the aerosol optical depth is given
aerosol_absorbing_optical_depth	double	[main]	excluded	Aerosol Absorbing Optical Depth
aerosol_absorbing_optical_depth_description	string		excluded	indication of wavelength for which the aerosol absorbing optical depth is given
uv_aerosol_index	double	[main]	included	UV Aerosol Index
vis_aerosol_index	double	[main]	excluded	VIS Aerosol Index

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 name	type	description
include	string	Provide 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.
exclude	string	Provide 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_min	time*	Only include elements for which the value is greater than or equal to the provided filter option value
time_max	time*	Only include elements for which the value is less than or equal to the provided filter option value
time	time*	Only include elements that match the list of given filter option values
latitude_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
latitude_max	double	Only include elements for which the value is less than or equal to the provided filter option value
latitude	double	Only include elements that match the list of given filter option values
longitude_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
longitude_max	double	Only include elements for which the value is less than or equal to the provided filter option value
longitude	double	Only include elements that match the list of given filter option values
aerosol_optical_depth_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
aerosol_optical_depth_max	double	Only include elements for which the value is less than or equal to the provided filter option value
aerosol_optical_depth	double	Only include elements that match the list of given filter option values
aerosol_absorbing_optical_depth_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
aerosol_absorbing_optical_depth_max	double	Only include elements for which the value is less than or equal to the provided filter option value
aerosol_absorbing_optical_depth	double	Only include elements that match the list of given filter option values
uv_aerosol_index_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
uv_aerosol_index_max	double	Only include elements for which the value is less than or equal to the provided filter option value
uv_aerosol_index	double	Only include elements that match the list of given filter option values
vis_aerosol_index_min	double	Only include elements for which the value is greater than or equal to the provided filter option value
vis_aerosol_index_max	double	Only include elements for which the value is less than or equal to the provided filter option value
vis_aerosol_index	double	Only include elements that match the list of given filter option values
aerosol_optical_depth_variant	string	To select the wavelength use either '354nm', '388nm' (default), or '500nm' 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 name	mapping description
time	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Geolocation_Fields/Time[]
	description	The time converted from TAI93 to seconds since 2000-01-01T00:00:00
latitude	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Geolocation_Fields/Latitude[]
longitude	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Geolocation_Fields/Longitude[]
corner_latitude	description	The 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	description	The 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))
aerosol_optical_depth	condition	aerosol_optical_depth_variant=354nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolOpticalDepth[,,0]
	condition	aerosol_optical_depth_variant=388nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolOpticalDepth[,,1]
	condition	aerosol_optical_depth_variant=500nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolOpticalDepth[,,2]
aerosol_optical_depth_description	description	Value depends on aerosol_optical_depth_variant filter option
aerosol_absorbing_optical_depth	condition	aerosol_absorbing_optical_depth_variant=354nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolAbsOpticalDepth[,,0]
	condition	aerosol_absorbing_optical_depth_variant=388nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolAbsOpticalDepth[,,1]
	condition	aerosol_absorbing_optical_depth_variant=500nm
	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/FinalAerosolAbsOpticalDepth[,,2]
aerosol_absorbing_optical_depth_description	description	Value depends on aerosol_optical_depth_variant filter option
uv_aerosol_index	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/UVAerosolIndex[]
vis_aerosol_index	path	/HDFEOS/SWATHS/Aerosol_NearUV_Swath/Data_Fields/VISAerosolIndex[]