Landsat 4-5 TM L2
About Landsat 4-5 TM Collection 2 Level 2 Data
The Landsat Thematic Mapper (TM) sensor was carried onboard Landsats 4 and 5. It provides 6 spectral bands and 1 thermal infrared band. Learn more about here.
|Spatial resolution||30 m (the thermal band is re-sampled from 120 m)|
|Sensor||Thematic Mapper (TM) with 6 spectral bands and 1 thermal infrared band|
|Revisit time||16 days|
|Spatial coverage||Whole globe|
|Data availability||Landsat 4 from July 1982 to December 1993 |
Landsat 5 from March 1984 to May 2012
|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 collection you are querying. This chapter will help you understand the parameters for Landsat 4-5 TM Level 2 data. For an overview of all API parameters see the API Reference.
|services-uswest2.sentinel-hub.com/api||Global coverage from July 1982 to May 2012|
Data type identifier: landsat-tm-l2
landsat-tm-l2  (previously
LTML2) as the value of the
input.data.type parameter in your API requests. This is mandatory and will ensure you get Landsat 4-5 TM Level 2 data.
The collection is currently in the preview stage and might thus change.
landsat-tm-l2 stands for Landsat Thematic Mapper Level 2.
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 USGS for easier distribution.
|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,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 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.
Selects product tiers.
|TIER_1||selects Tier 1 products|
|ALL_TIERS||selected by default. selects Tier 1 and Tier 2 products|
This chapter will explain the
input.data.processing object of the
|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.
|B01||Blue (450-520 nm)||30m|
|B02||Green (520-600 nm)||30m|
|B03||Red (630-690 nm)||30m|
|B04||Near Infrared (NIR) (760-900 nm)||30m|
|B05||Shortwave Infrared (SWIR) 1 (1550-1750 nm)||30m|
|B06||Thermal Infrared (10400-12500 nm)||30m |
|B07||Shortwave Infrared (SWIR) 2 (2080-2350 nm)||30m|
|BQA||Quality Assessment band (QA)||30m|
|QA_RADSAT||Radiometric Saturation and Terrain Occlusion QA Band||30m|
|ST_QA||Surface Temperature Uncertainty||30m|
|ST_TRAD||Level-1 thermal band converted to thermal surface radiance||30m|
|ST_EMIS||Emissivity estimated from ASTER GED||30m|
|ST_EMSD||Emissivity standard deviation||30m|
|ST_CDIST||Pixel distance to cloud||30m|
|SR_ATMOS_OPACITY||Internal SR Atmospheric Opacity||30m|
|SR_CLOUD_QA||Cloud Quality Assessment||30m|
|dataMask||The mask of data/no data pixels (more).||N/A |
: Thermal band is acquired at 120 meter resolution and then resampled to 30 meter in delivered data product (source).
: 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.
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.
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 - B05, B07
|Surface reflectance (unitless)||REFLECTANCE||UINT16||0 - 0.4||Higher values in infrared bands. Reflectance values can easily be above 1.|
|Thermal band |
|Surface temperature (kelvin)||SURFACE_TEMPERATURE||UINT16||250 - 320||Surface 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)||Use the function named decodeL8C2Qa (see).|
|QA_RADSAT||Radiometric saturation quality assessment (unitless)||DN||UINT16||bit-packed combination (info here)|
|ST_QA||Surface temperature uncertainty (Kelvin)||KELVIN||INT16|
|ST_TRAD||Radiance (W / m2 / sr / μm)||RADIANCE||INT16|
|ST_URAD||Radiance (W / m2 / sr / μm)||RADIANCE||INT16|
|ST_DRAD||Radiance (W / m2 / sr / μm)||RADIANCE||INT16|
|ST_ATRAN||Atmospheric transmittance (unitless)||FRACTION||INT16||0 - 1|
|ST_EMIS||Emissivity (unitless)||FRACTION||INT16||0 - 1|
|ST_EMSD||Emissivity standard deviation (unitless)||FRACTION||INT16||0 - 1|
|ST_CDIST||Pixel distance (kilometers)||KILOMETERS||INT16|
|SR_ATMOS_OPACITY||Opacity (unitless)||FRACTION||INT16||0 - 1|
|SR_CLOUD_QA||Cloud mask quality (unitless)||DN||UINT8||bit-packed combination (info here)|
|dataMask||N/A||DN||N/A||0 - no data|
1 - data
Catalog API Capabilities
To access Landsat 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-tm-l2||Data availability and coverage is the same as in the basic facts|
Collection identifier: landsat-tm-l2
eo:cloud_covercloud cover percentage
T1for tier 1 (scenes with the highest radiometric and positional quality) and
T2for tier 2 (scenes not meeting tier 1 criteria)