Landsat 8-9 L2

About Landsat 8-9 OLI-TIRS Collection 2 Level 2 Data

Mission Information

Landsat 8-9 Level 2 collection includes both Landsat 8 and the most recently launched Landsat 9 satellites (provided by NASA/USGS), both carrying the Operational Land Imager (OLI) and the Thermal Infrared Sensor (TIRS), providing seasonal coverage of the global landmass. Landsat 8-9 Level 2 provides global surface reflectance and surface temperature science products. Level 2 science products are generated from Collection 2 Level-1 inputs that meet the <76 degrees Solar Zenith Angle constraint and include the required auxiliary data inputs to generate a scientifically viable product. Learn more about the collection here.

Basic Facts

Spatial resolution30 m (the thermal bands is re-sampled from 100 m)
SensorOperational Land Imager (OLI for Landsat 8 and OLI-2 for Landsat 9) with 9 spectral bands and Thermal Infrared Sensor (TIRS for Landsat 8 and TIRS-2 for Landsat 9) with 2 thermal bands
Revisit time8 days (16 days for each of the two sensors)
Spatial coverageWhole globe
Data availabilityLandsat 8 since February 2013, Landsat 9 since January 2022.
Common usage/purposeVegetation monitoring, land use, land cover maps and monitoring of changes.

Accessing 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 collection you are querying. This chapter will help you understand the parameters for Landsat 8-9 Level 2 data. For an overview of all API parameters see the API Reference.

Endpoint Locations

ServiceNotes coverage since February 2013

Data type identifier: landsat-ot-l2

Use landsat-ot-l2 [1] (previously LOTL2) as the value of the parameter in your API requests. This is mandatory and will ensure you get Landsat 8-9 Level 2 data.

The collection is currently in the preview stage and might thus change.

[1]: landsat-ot-l2 stands for Landsat OLI-TIRS Level 2.

Filtering Options

This chapter will explain the object of the process API.


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 USGS for easier distribution.

mostRecentselected by default. The pixel will be selected from the tile, which was acquired most recentl
leastRecentsimilar to mostRecent but in reverse order
leastCCpixel is selected from tile with the least cloud coverage metadatanote that "per tile" information is used here, each covering about a 31,100 sq. km area, so this information is only an estimate.


Selects product tiers.

TIER_1selects Tier 1 products
ALL_TIERSselected by default. selects Tier 1 and Tier 2 products


Sets the upper limit for cloud coverage in percent based on the precomputed cloud coverage estimate for each 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.

Processing Options

This chapter will explain the object of the process API.

upsamplingThe same as for S2L1C.
downsamplingThe same as for S2L1C.

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.

B01Ultra Blue (443 nm)30m
B02Blue (482 nm)30m
B03Green (561.5 nm)30m
B04Red (654.5 nm)30m
B05Near Infrared (NIR) (865 nm)30m
B06Shortwave Infrared (SWIR) 1 (1608.5 nm)30m
B07Shortwave Infrared (SWIR) 2 (2200.5 nm)30m
B10Thermal Infrared (TIRS) 1(10895 nm)30m [1]
BQAQuality Assessment band (QA)30m
QA_RADSATRadiometric Saturation and Terrain Occlusion QA Band30m
ST_QASurface Temperature Uncertainty30m
ST_TRADLevel-1 thermal band converted to thermal surface radiance30m
ST_URADUpwelled Radiance30m
ST_DRADDownwelled Radiance30m
ST_ATRANAtmospheric Transmittance30m
ST_EMISEmissivity of Band 10 estimated from ASTER GED30m
ST_EMSDEmissivity standard deviation30m
ST_CDISTPixel distance to cloud30m
dataMaskThe mask of data/no data pixels (more).N/A [2]

[1]: TIRS bands are acquired at 100 meter resolution, but are resampled to 30 meter in delivered data product (source).
[2]: dataMask has no source resolution as it is calculated for each output pixel.


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. 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.

BandPhysical Quantity (units)Sentinel Hub UnitsSource FormatTypical RangeNotes
Optical bands
B01 - B07
Surface reflectance (unitless)REFLECTANCEUINT160 - 0.4Higher values in infrared bands. Reflectance values can easily be above 1.
Thermal infrared band
Surface temperature (kelvin)SURFACE_TEMPERATUREUINT16250 - 320Surface temperature of roughly -20 to +50 C. Can reach outside this range in extreme environments.
BQAPixel quality assessment (unitless)DNUINT16bit-packed combination (info here)Use the function named decodeL8C2Qa (see).
QA_RADSATRadiometric saturation quality assessment (unitless)DNUINT16bit-packed combination (info here)
SR_QA_AEROSOLSurface reflectance quality assessment (unitless)DNUINT8bit-packed combination (info here)
ST_QASurface temperature uncertainty (Kelvin)KELVININT16
ST_TRADRadiance (W / m2 / sr / μm)RADIANCEINT16
ST_URADRadiance (W / m2 / sr / μm)RADIANCEINT16
ST_DRADRadiance (W / m2 / sr / μm)RADIANCEINT16
ST_ATRANAtmospheric transmittance (unitless)FRACTIONINT160 - 1
ST_EMISEmissivity (unitless)FRACTIONINT160 - 1
ST_EMSDEmissivity standard deviation (unitless)FRACTIONINT160 - 1
ST_CDISTPixel distance (kilometers)KILOMETERSINT16
dataMaskN/ADNN/A0 - no data
1 - data

Scenes Object

scenes object stores metadata, for an example see scenes object for Landsat-8-9 L1.

Catalog API Capabilities

To access Landsat 8-9 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.

Collection identifier: landsat-ot-l2

Filter extension

  • eo:cloud_cover cloud cover percentage
  • landsat:scene_id scene identifier
  • landsat:collection_category collection tier. T1 for tier 1 (scenes with the highest radiometric and positional quality) and T2 for tier 2 (scenes not meeting tier 1 criteria)

Distinct extension

  • date