Sentinel-2 L1C

About Sentinel-2 L1C Data

Mission information

SENTINEL-2 is a European wide-swath, high-resolution, multi-spectral imaging mission. Its high-resolution optical images have many applications, including land monitoring, emergency response and security services assistance. The satellite's multispectral imager provides a versatile set of 13 spectral bands spanning from the visible and near infrared to the shortwave infrared.

More information:

• https://sentinel.esa.int/web/sentinel/missions/sentinel-2
• Collection user guide

Basic facts

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

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-2 L1C 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 S2L1C data. To see examples of such requests go here, and for an overview of all API parameters see the API Reference.

Endpoint Locations

Differences in Capabilities

eocloud.sentinel-hub.com supports only OGC requests (and not API requests). The version of OGC services at eocloud.sentinel-hub.com is older and there might be minor differences in rendering. For the latest version use services.sentinel-hub.com endpoint.

Data type identifier: sentinel-2-l1c

Use sentinel-2-l1c (previously S2L1C) as the value of the input.data.type parameter in your API requests. This is mandatory and will ensure you get Sentinel-2 L1C data.

Filtering Options

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

mosaickingOrder

Sets the order of overlapping tiles from which the output result is mosaicked. Note that tiles will in most cases come from the same orbit/acquisition. The tiling is done by ESA for easier distribution.

maxCloudCoverage

Sets the upper limit for cloud coverage in percent based on the precomputed cloud coverage estimate for each Sentinel-2 tile as present in the tile metadata. Satellite data will therefore not be retrieved for tiles with a higher cloud coverage estimate. For example, by setting the value to 20, only tiles with at most 20% cloud coverage will be used. Note that this parameter is set per tile and might not be directly applicable to the chosen area of interest.

previewMode

Sentinel Hub API is optimised for full resolution data access as this is what most users need. There are, however, cases where low spatial resolution makes sense as well. To make this feasible, Sentinel Hub generates lower resolution files (which we call previews) with up to a few hours of delay after initial data availability. To enable access to these previews and thus reduce the resolution limit, set this property to TILE_PREVIEW, PREVIEW or EXTENDED_PREVIEW. If set, the API will still display full resolution data when requesting higher resolutions. So, aside from potentially using more requests, in general there is no downside to enabling this option.

NOTE: CLM and CLP bands have meaningful values only when requesting resolution 200 meters per pixel or higher (more zoomed in) or previewMode TILE_PREVIEW and resolution 640 meters per pixel or higher.

NOTE: maxCloudCoverage filter is not applied for PREVIEW and EXTENDED_PREVIEW when requesting mosaicking SIMPLE.

Processing Options

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

Available Bands and Data

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.

[1]: The data of this band is always resampled using nearest neighbor interpolation, regardless of the requested interpolation type.

[2]: dataMask has no source resolution as it is calculated for each output pixel.

Units

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.

The 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 (see also Harmonize Values). 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.

The Typical Range indicates what values are common for a given band and unit, however outliers can be expected.

For Sentinel-2 optical data, the relation between DN and REFLECTANCE (default unit) is: DN = 10000 * REFLECTANCE. See also Harmonize Values.

*Higher values are expected in infrared bands. Reflectance values can easily be above 1.

Harmonize Values

ESA updated the Sentinel-2 processing baseline to version 04.00 in January, 2022, which introduced breaking changes to the interpretation of digital numbers (DN). The optional harmonizeValues parameter gives you extra control over the values which enter your evalscript.

harmonizeValues can be true (default) or false, and it's behavior depends on the units chosen:

• REFLECTANCE:
  • harmonizeValues = true: negative reflectance values are clamped to zero. In other words, pixels with negative reflectance return zero reflectance instead.
  • harmonizeValues = false: negative reflectance values can be returned.
• DN:
  • harmonizeValues = true: DN values are harmonized so they are comparable with data from previous baselines. Therefore it still holds that DN = 10000 * REFLECTANCE. In addition, negative values are clamped to zero.
  • harmonizeValues = false: DN values are exactly as provided in the source files themselves. The "true" DN value, you could say. Don't forget that values have different definitions with different processing baselines, careful with mosaicking!

Mosaicking

All mosaicking types are supported.

Scenes Object

scenes object stores metadata. An example of metadata available in scenes object for Sentinel-2 L1C 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.

Catalog API Capabilities

To access Sentinel 2 L1C 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. This chapter will help with understanding Sentinel 2 L1C specific parameters for search request.

Endpoint Locations

Collection identifier: sentinel-2-l1c

Query extension

• eo:cloud_cover cloud cover percentage

Distinct extension

• date

Examples

S2L1C examples