Landsat 8-9 L1 & L2
Landsat 8–9 collections include both Landsat 8 and the most recently launched Landsat 9 satellites (provided by NASA/USGS), both carrying the Operational Land Imager (OLI/OLI-2) and the Thermal Infrared Sensor (TIRS/TIRS-2) instruments, providing seasonal coverage of the global landmass.
Landsat 8–9 Level 1 includes radiometrically calibrated and orthorectified data with 9 optical and 2 thermal bands. 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.
Basic Facts
| Property | Landsat 8–9 Level 1 | Landsat 8–9 Level 2 |
|---|---|---|
| Data type | Top of Atmosphere (TOA) Reflectance and Brightness Temperature | Surface Reflectance and Surface Temperature |
| Spatial resolution | 15 m for the panchromatic band and 30 m for the rest (the thermal bands is resampled from 100 m) | 30 m (the thermal bands is resampled from 100 m) |
| Sensor | Operational 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 | Operational 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 time | 8 days (16 days for each of the two sensors) | 8 days (16 days for each of the two sensors) |
| Spatial coverage | Whole globe | Whole globe |
| Data availability | Landsat 8 since March 2013, Landsat 9 since November 2021. | Landsat 8 since February 2013, Landsat 9 since January 2022. |
| Common usage/purpose | Vegetation monitoring, land use, land cover maps and monitoring of changes. | Vegetation 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.
For an overview of all API parameters see the API Reference.
Endpoint Locations
| Service | Notes |
|---|---|
| services-uswest2.sentinel-hub.com/api | Global coverage since February 2013 |
Data type identifiers
Use the following values for input.data.type:
| Dataset | Identifier |
|---|---|
| Landsat 8–9 Level 1 | landsat-ot-l1 (previously LOTL1) |
| Landsat 8–9 Level 2 | landsat-ot-l2 (previously LOTL2) |
Filtering Options
This chapter explains the input.data.dataFilter object.
mosaickingOrder
| Value | Description | Notes |
|---|---|---|
| mostRecent | (default) The pixel will be selected from the most recently acquired tile | |
| leastRecent | similar to mostRecent but in reverse order | |
| leastCC | The pixel is selected from the tile with the lowest cloud coverage | This information is estimated per tile (each covering about 31,100 sq. km) so local cloud coverage may differ |
maxCloudCoverage
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.