More information: USGS, Mission, Landsat8 .
|Spatial resolution||30 m, exceptions are the thermal band with a resolution of 120 m and the panchromatic band with a resolution of 15 m.|
|Sensor||Operational Land Imager (OLI) with 9 spectral bands and Thermal Infrared Sensor (TIRS) with 2 spectral 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.|
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 L8L1C data. For an overview of all API parameters see the API Reference.
|services-uswest2.sentinel-hub.com/api||Global coverage since February 2013|
L8L1C as the value of the
input.data.type parameter in your API requests. This is mandatory and will ensure you get Landsat 8 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. Note that tiles will in most cases come from the same orbit/acquisition. The tiling is done by ESA for easier distribution.
|mostRecent||selected by default. The pixel will be selected from the tile, which was acquired most recently||in case there are more tiles available with the same timestamp (some tiles are processed by many ground stations, some are reprocessed, etc.), the one, which was downloaded from SciHub later will be used.|
|leastRecent||similar to mostRecent but in reverse order|
|leastCC||pixel is selected from tile with the least cloud coverage meta-data||note that "per tile" information is used here, each covering about a 12,000 sq. km area, so this information is only an estimate .|
Sets the upper limit for cloud coverage in percent based on the precomputed cloud coverage estimate for each Sentinel-1 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.
This chapter will explain the
input.data.processing object of the
|upsampling||The same as for S2L1C.|
|downsampling||The same as for S2L1C.|
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.bandsarray in your evalscript.
|B01||Ultra Blue (443 nm)||30m||REFLECTANCE|
|B02||Blue (482 nm)||30m||REFLECTANCE|
|B03||Green (561.5 nm)||30m||REFLECTANCE|
|B04||Red (654.5 nm)||30m||REFLECTANCE|
|B05||Near Infrared (NIR) (865 nm)||30m||REFLECTANCE|
|B06||Shortwave Infrared (SWIR) 1 (1608.5 nm)||30m||REFLECTANCE|
|B07||Shortwave Infrared (SWIR) 2 (2200.5 nm)||30m||REFLECTANCE|
|B08||Panchromatic ( 589.5 nm)||15m||REFLECTANCE|
|B09||Cirrus (1373.5 nm)||30m||REFLECTANCE|
|B10||Thermal Infrared (TIRS) 1(10895 nm)||100m * (30m)||Brightness temperature in Kelvin|
|B11||Thermal Infrared (TIRS) 2 (12005 nm)||100m * (30m)||Brightness temperature in Kelvin|
|dataMask||The mask of data/no data pixels (more).||N/A**||0 - no data|
1 - data
|BQA***||Quality Assessment band (QA)||30m||bit-packed combination (key)|
*TIRS bands are acquired at 100 meter resolution, but are resampled to 30 meter in delivered data product (source). **dataMask has no source resolution as it is calculated for each output pixel. ***The values can be obtained using the utility function named decodeLs8Qa.
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.
|services-uswest2.sentinel-hub.com/api/v1/catalog/collections/landsat-8-l1c||Global coverage since February 2013|
eo:cloud_covercloud cover percentage