Sentinel-5P L2

About Sentinel-5P Data

Sentinel Hub supports Sentinel-5P level 2 (L2) data products as provided by ESA. General information about the satellite and specifically Level 2 data is available here: http://www.tropomi.eu/data-products/level-2-products. Raw bands (Level 1 products) are not available in Sentinel Hub.

Learn more about Sentinel-5P atmosphere monitoring by reading our blog post on measuring Air Pollution from space.

Mission Information

The Sentinel-5P (P for precursor) mission aims at providing information and services on air quality and climate between 2017 and at least 2023. With the TROPOMI sensor on board it makes daily global observations of key atmospheric constituents, including ozone, nitrogen dioxide, sulfur dioxide, carbon monoxide, methane, formaldehyde as well as cloud and aerosol properties. The mission aims at ensuring data continuity between the retirement of the Envisat satellite and NASA's Aura mission and the launch of Sentinel-5 (source: ESA).

Basic Facts

(Source: ESA.)

* "5.5 x 3.5" means a spatial resolution of 5.5 km in the satellite flight direction and 3.5 km in the perpendicular direction at nadir. Data released before 6 August 2019 had a resolution in the flight direction up to 7 km (see ESA news).

Attribution and Use

EU law grants free access to Copernicus Sentinel Data and Service Information for the purpose of the following use in so far as it is lawful: a) reproduction; b) distribution; c) communication to the public; d) adaptation, modification and combination with other data and information; e) any combination of points a to d.

See more details on the use of Copernicus Sentinel data and service information here. Tracing based on Sentinel imagery is allowed for commercial purposes as well.

Acknowledgment or credit: Contains modified Copernicus Sentinel data [Year] processed by Sentinel Hub

Accessing Sentinel-5P Data

To access data you need to send a POST request to our process API. The requested data will be returned as the response to your request. Each POST request can be tailored to get you exactly the data you require. To do this requires setting various parameters which depend on the datasource you are querying. This chapter will help you understand the parameters for S5PL2 data. To see examples of such requests go here, and for an overview of all API parameters see the API Reference.

Endpoint Locations

Data type identifier: sentinel-5p-l2

Use sentinel-5p-l2 (previously S5PL2) as the value of the input.data.type parameter in your API requests. This is mandatory and will ensure you get Sentinel-5P L2 data.

Filtering Options

This chapter will explain the input.data.dataFilter object of the S5PL2 process API.

timeRange

For simple mosaicking, the time range which is requested is clipped to start at most 24 hours before the to date-time. The reason for this is that Sentinel-5P covers the globe in one day therefore longer time ranges are not neccessary. The limitation also improves the responsiveness of Sentinel Hub.

mosaickingOrder

Sets the order of sources from which the output result is mosaicked. If there are multiple sources available for the same time, unless explicitly set otherwise, Sentinel Hub will take the source with the slowest timeliness (i.e. RPRO prefered to OFFL prefered to NRTI).

timeliness

You can force the timeliness of the requested data. If not set and there are multiple sources available for the same time, Sentinel Hub will take the source with the slowest timeliness (RPRO prefered to OFFL prefered to NRTI). To explicitly set, the options are:

• NRTI for near realtime,
• OFFL for offline,
• RPRO for reprocessing.

Processing Options

This chapter will explain the input.data.processing object of the S5PL2 process API.

Available Bands and Data

Information in this chapter is useful when defining input object in evalscript: any string listed in the column Name can be an element of the input.bands array in your evalscript.

Units

The data values for each band in your custom script are presented in the default units as specified here. In case more than one unit is available for a given band, you may optionally set the value of input.units in your evalscript setup function to one of the options. Doing so will present data in that unit. The Source Format specifies how and with what precision the digital numbers from which the unit is derived are encoded. The Typical Range indicates what values are common for a given band and unit, however outliers can be expected.

Mosaicking

SIMPLE and ORBIT mosaicking types are supported.

Scenes Object

scenes object stores metadata. An example of metadata available in scenes object for Sentinel-5p L2 when mosaicking is ORBIT:

Properties of a scenes object can differ depending on the selected mosaicking and in which evalscript function the object is accessed. Working with metadata in evalscript user guide explains all details and provide examples.

Collection Specific Constraints

The raw data is encoded as 32-bit float samples. For scientific usage it is best to set tiff as an output format and sampleType: SampleType.FLOAT32.

Sentinel-5P data can potentially contain many no data pixels which is a consequence of the way it is measured. We therefore suggest using the dataMask band to differentiate between actual zero values and no data.

Catalog API Capabilities

To access Sentinel 5P L2 product metadata you need to send search request to our Catalog API. The requested metadata will be returned as JSON formatted response to your request.

Endpoint Locations

Collection identifier: sentinel-5p-l2

Query extension

• type (available types)
• orbit_id
• timeliness (possible values)

Distinct extension

• date
• type (available types)

Examples

S5PL2 Examples