Landsat 8 L1
About Landsat 8 OLI-TIRS Collection 2 Level 1 Data
Mission Information
Landsat 8 is the most recently launched Landsat satellite (provided by NASA/USGS) and carries the Operational Land Imager (OLI) and the Thermal Infrared Sensor (TIRS) instruments, with 9 optical and 2 thermal bands. These two sensors provide seasonal coverage of the global landmass. Learn more about here.
Basic Facts
| Property | Info |
|---|---|
| Spatial resolution | 15 m for the panchromatic band and 30 m for the rest (the thermal bands is re-sampled from 100 m) |
| Sensor | Operational Land Imager (OLI) with 9 spectral bands and Thermal Infrared Sensor (TIRS) with 2 thermal bands |
| Revisit time | 16 days |
| Spatial coverage | Whole globe |
| Data availability | Since February 2013 |
| Common usage/purpose | 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. This chapter will help you understand the parameters for Landsat 8 Level 1 data. 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 identifier: landsat-ot-l1
Use landsat-ot-l1[1] (previously LOTL1) as the value of the input.data.type parameter in your API requests. This is mandatory and will ensure you get Landsat 8 Level 1 data.
The collection is currently in the preview stage and might thus change.
[1]:landsat-ot-l1 stands for Landsat OLI-TIRS Level 1.
Filtering Options
This chapter will explain the input.data.dataFilter object of the 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 USGS for easier distribution.
| Value | Description | Notes |
|---|---|---|
| mostRecent | selected by default. The pixel will be selected from the tile, which was acquired most recentl | |
| leastRecent | similar to mostRecent but in reverse order | |
| leastCC | pixel is selected from tile with the least cloud coverage metadata | note that "per tile" information is used here, each covering about a 31,100 sq. km area, so this information is only an estimate. |
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.
tiers
Selects product tiers.
| Value | Description |
|---|---|
| TIER_1 | selects Tier 1 products |
| TIER_1_AND_RT | selects Tier 1 and Real-Time products |
| ALL_TIERS | selected by default. selects Real-Time, Tier 1 and Tier 2 products |
Processing Options
This chapter will explain the input.data.processing object of the process API.
| Action | Description |
|---|---|
| upsampling | The same as for S2L1C. |
| downsampling | The 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.
| Name | Description | Resolution |
|---|---|---|
| B01 | Ultra Blue (443 nm) | 30m |
| B02 | Blue (482 nm) | 30m |
| B03 | Green (561.5 nm) | 30m |
| B04 | Red (654.5 nm) | 30m |
| B05 | Near Infrared (NIR) (865 nm) | 30m |
| B06 | Shortwave Infrared (SWIR) 1 (1608.5 nm) | 30m |
| B07 | Shortwave Infrared (SWIR) 2 (2200.5 nm) | 30m |
| B08 | Panchromatic ( 589.5 nm) | 15m |
| B09 | Cirrus (1373.5 nm) | 30m |
| B10 | Thermal Infrared (TIRS) 1(10895 nm) | 30m [1] |
| B11 | Thermal Infrared (TIRS) 2 (12005 nm) | 30m [1] |
| BQA | Quality Assessment band (QA) | 30m |
| QA_RADSAT | Radiometric Saturation and Terrain Occlusion QA Band | 30m |
| VAA | View (sensor) Azimuth Angle | 30m |
| VZA | View (sensor) Zenith Angle | 30m |
| SAA | Sun Azimuth Angle | 30m |
| SZA | Sun Zenith Angle | 30m |
| dataMask | The 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.
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. 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.
| Band | Physical Quantity (units) | Sentinel Hub Units | Source Format | Typical Range | Notes |
|---|---|---|---|---|---|
| Optical bands B01 - B09 | Reflectance (unitless) | REFLECTANCE [1] | UINT16 | 0 - 0.4 | Higher values in infrared bands. Reflectance values can easily be above 1. |
| Thermal infrared bands B10 - B11 | Brightness temperature (Kelvin) | BRIGHTNESS_TEMPERATURE [2] | UINT16 | 250 - 320 | Brightness temperature of roughly -20 to +50 C. Can reach outside this range in extreme environments. |
| BQA | Pixel quality assessment (unitless) | DN | UINT16 | bit-packed combination (info here) | The values can be obtained using the utility function the function named decodeL8C2Qa (see). |
| QA_RADSAT | Radiometric saturation quality assessment (unitless) | DN | UINT16 | bit-packed combination (info here | |
| VAA | Angle (degrees) | DEGREES | INT16 | ||
| VZA | Angle (degrees) | DEGREES | INT16 | ||
| SAA | Angle (degrees) | DEGREES | INT16 | ||
| SZA | Angle (degrees) | DEGREES | INT16 | ||
| dataMask | N/A | DN | N/A | 0 - no data 1 - data |
[1]: Top of the Atmosphere Reflectance, which is obtained using the scene center sun angle.
[2]: Top of the Atmosphere Brightness Temperature.
Scenes Object
scenes object stores metadata. An example of metadata available in scenes object for Sentinel-5p L2 when mosaicking is ORBIT:
| Property name | Value |
|---|---|
| dateFrom | '2018-12-25T00:00:00Z' |
| dateTo | '2018-12-25T23:59:59Z' |
| tiles[i].date | '2018-12-25T09:45:29.121783Z' |
| tiles[i].shId | 3097841 |
| tiles[i].cloudCoverage | 98.35 |
| tiles[i].tileOriginalId | 'LC08_L1TP_190027_20181225_20200829_02_T1' |
| tiles[i].dataPath | 'https://usgs-landsat.s3.amazonaws.com/collection02/level-1/standard/oli-tirs/2018/190/027/LC08_L1TP_190027_20181225_20200829_02_T1/LC08_L1TP_190027_20181225_20200829_02_T1' |
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 Landsat 8 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
| Service | Notes |
|---|---|
| services-uswest2.sentinel-hub.com/api/v1/catalog/collections/landsat-ot-l1 | Global coverage since February 2013 |
Collection identifier: landsat-ot-l1
Query extension
eo:cloud_covercloud cover percentage
Distinct extension
date