Sentinel-3 OLCI L1B
SENTINEL-3 is a European wide-swath, medium-resolution, multi-spectral imaging mission designed to monitor ocean surface topography as well as land and sea surface temperature. The satellite hosts 4 instruments: the Sea and Land Surface Temperature Radiometer (SLSTR), the Ocean and Land Colour Instrument (OLCI), a Sar Radar Altimeter (SRAL) and a Microwave Radiometer (MWR). Sentinel-3A was launched on 16 February 2016 and its twin Sentinel-3B on 25 April 2018.
The OLCI instrument was designed to provide data continuity with the Medium Resolution Imaging Spectrometer (MERIS) instrument flown on Envisat. With its 21 spectral bands ranging from the visible to the near-infrared, the primary objective of the instrument is to measure information related to biology, including the monitoring of ocean colour, algae blooms, and land cover. The additional 6 bands compared to MERIS allow improved Atmospheric Composition measurements. The OLCI swath is not centred at nadir in order to mitigate the effects of sun glint.
Level-1B provides calibrated, ortho-geolocated and spatially re-sampled Top Of Atmosphere (TOA) radiances for the 21 OLCI spectral bands.
|Spatial resolution||~300 m|
|Sensor||Ocean and Land Color Instrument (OLCI), 21 bands: 16 visible bands, 5 Near-Infrared bands|
|Units||Radiance (mW.m-2.sr-1.nm-1). Note that Sentinel Hub returns reflectance.|
|Revisit time||< 2 days with 2 satellites|
|Spatial coverage||Land and coastal areas where the solar zenith angle < 80º|
|Data availability||Since April 2016|
|Measurement||Top of the atmosphere (TOA) radiance|
|Common usage/purpose||Maritime, land, atmospheric and climate change monitoring|
For processing Sentinel-3 OLCI we use the full resolution lat/lon grid from the OLCI L1B products so pixel positioning is exact.
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.
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.
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 S3OLCI data. To see examples of such requests go here, and for an overview of all API parameters see the API Reference.
|creodias.sentinel-hub.com/api/||Global since May 2016|
|code-de.sentinel-hub.com/api/||Germany since May 2016|
S3OLCI) as the value of the
input.data.type parameter in your API requests. This is mandatory and will ensure you get Sentinel-3 OLCI L1B data.
This chapter will explain the
input.data.dataFilter object of the
Sets the order of overlapping tiles from which the output result is mosaicked. The tiling is based on ESA's Product Dissemination Units for easier distribution.
|mostRecent||the pixel will be selected from the most recently acquired tile||If there are multiple products with the same timestamp then NTC will be used over NRT.|
|leastRecent||the pixel will be selected from the oldest acquired tile||If there are multiple products with the same timestamp then NTC will be used over NRT.|
This chapter will explain the
input.data.processing object of the
|upsampling||Defines the interpolation used for processing when the pixel resolution is greater than the source resolution (e.g. 50m/px with a 300m/px source).||NEAREST - nearest neighbour interpolation |
BILINEAR - bilinear interpolation
BICUBIC - bicubic interpolation
|downsampling||Defines the interpolation used for processing when the pixel resolution is lower than the source resolution (e.g. 500m/px with a 300m/px source).||NEAREST - nearest neighbour interpolation |
BILINEAR - bilinear interpolation
BICUBIC - bicubic interpolation
This chapter will explain the bands and data which can be set in the evalscript input object.
Any string listed in the column Name can be an element of the
input.bands array in your evalscript.
|Name||Description||Wavelength centre (nm)||Resolution (m)|
|B01||Aerosol correction, improved water constituent retrieval||400||300|
|B02||Yellow substance and detrital pigments (turbidity)||412.5||300|
|B03||Chlorophyll absorption maximum, biogeochemistry, vegetation||442.5||300|
|B05||Chlorophyll, sediment, turbidity, red tide||510||300|
|B06||Chlorophyll reference (minimum)||560||300|
|B08||2nd Chlorophyll absorption maximum, sediment, yellow substance / vegetation||665||300|
|B09||Improved fluorescence retrieval||673.75||300|
|B10||Chlorophyll fluorescence peak, red edge||681.25||300|
|B11||Chlorophyll fluorescence baseline, red edge transition||708.75||300|
|B12||O2 absorption / clouds, vegetation||753.75||300|
|B13||O2 absorption / aerosol correction||761.25||300|
|B15||O2 absorption used for cloud top pressure, fluorescence over land||767.5||300|
|B16||Atmospheric / aerosol correction||778.75||300|
|B17||Atmospheric / aerosol correction, clouds, pixel co-registration||865||300|
|B18||Water vapour absorption reference. Common reference band with SLSTR. Vegetation monitoring||885||300|
|B19||Water vapour absorption, vegetation monitoring (maximum REFLECTANCE)||900||300|
|B20||Water vapour absorption, atmospheric / aerosol correction||940||300|
|B21||Atmospheric / aerosol correction, snow grain size||1020||300|
|QUALITY_FLAGS||Classification and quality flags||N/A||300|
|SAA||Sun azimuth angle||N/A||19000|
|SZA||Sun zenith angle||N/A||19000|
|VAA||Viewing (observation) azimuth angle||N/A||19000|
|VZA||Viewing (observation) zenith angle||N/A||19000|
|HUMIDITY||Relative humidity (meteo band)||N/A||19000|
|SEA_LEVEL_PRESSURE||Mean sea level pressure (meteo band)||N/A||19000|
|TOTAL_COLUMN_OZONE||Total column ozone (meteo band)||N/A||19000|
|TOTAL_COLUMN_WATER_VAPOUR||Total column water vapour (meteo band)||N/A||19000|
|dataMask||The mask of data/no data pixels (more).||N/A*||N/A**|
*dataMask has no wavelength information, as it carries only boolean information on whether a pixel has data or not. See the chapter on Units for more.
**dataMask has no source resolution as it is calculated for each output pixel.
For more about Sentinel-3 OLCI bands, visit this Copernicus website.
The data values for each band in your custom script are presented in the 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 values in the
Sentinel Hub Units column. Doing so will present data in that unit. The Sentinel Hub
units parameter combines the physical quantity and corresponding units of measurement values. As such, some names more closely resemble physical quantities, others resemble units of measurement.
Source Format specifies how and with what precision the digital numbers (
DN) from which the unit is derived are encoded. Bands requested in
DN units contain exactly the pixel values of the source data. Note that resampling may produce interpolated values.
DN is also used whenever a band is derived computationally (like dataMask); such bands can be identified by having
DN units and
N/A source format.
DN values are typically not offered if they do not simply represent any physical quantity, in particular, when
DN values require source-specific (i.e. non-global) conversion to physical quantities.
Values in non-
DN units are computed from the source (
DN) values with at least float32 precision. Note that the conversion might be nonlinear, therefore the full value range and quantization step size of such a band can be hard to predict. Band values in evalscripts always behave as floating point numbers, regardless of the actual precision.
Typical Range indicates what values are common for a given band and unit, however outliers can be expected.
|Band||Physical Quantity (units)||Sentinel Hub Units||Source Format||Typical Range||Notes|
|Optical bands |
|Reflectance (unitless)||REFLECTANCE||UINT16||0 - 0.4||Higher values in infrared bands. Highly reflective pixels, such as clouds, can have reflectance values above 1.|
|VAA||Angle (degrees)||DEGREES||INT16||-180 - 180|
|VZA||Angle (degrees)||DEGREES||UINT16||0 - 180|
|SAA||Angle (degrees)||DEGREES||INT16||-180 - 180|
|SZA||Angle (degrees)||DEGREES||UINT16||0 - 180|
|HUMIDITY||Humidity (percent)||PERCENT||FLOAT32||0 - 100|
|SEA_LEVEL_PRESSURE||Pressure (hectopascals)||HECTOPASCALS||FLOAT32||980 - 1030||Extreme weather can be outside this range|
|TOTAL_COLUMN_OZONE||Total column ozone (kg/m2)||KG_M2||FLOAT32||0.004 - 0.008|
|TOTAL_COLUMN_WATER_VAPOUR||Total column water vapour (kg/m2)||KG_M2||FLOAT32||0 - 70|
|QUALITY_FLAGS||N/A||DN||UINT32||0 - 4,294,967,294||Bit packed value. Use decodeS3OLCIQualityFlags to unpack.|
|dataMask||N/A||DN||N/A||0 - no data|
1 - data
All mosaicking types are supported.
scenes object stores metadata. An example of metadata available in
scenes object for Sentinel-3 OLCI when mosaicking is
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 provides examples.
To access Sentinel 3 OLCI 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.
|creodias.sentinel-hub.com/api/v1/catalog/collections/sentinel-3-olci||Global since May 2016|
|code-de.sentinel-hub.com/api/v1/catalog/collections/sentinel-3-olci||Germany since May 2016|