Landsat 1-5 MSS L1
The Landsat Multispectral Scanner System (MSS) sensors were carried onboard Landsats 1 to 5. It provides 4 spectral bands. Learn more about here.
|Spatial resolution||68 m x 83 m (commonly resampled to 57 m, or 60 m)|
|Sensor||Multispectral Scanner System (MSS) with 4 spectral bands|
|Revisit time||18 days for Landsats 1-3 and 16 days for Landsat 4-5|
|Spatial coverage||Whole globe|
|Data availability||Landsat 1 from July 1972 to January 1978 |
Landsat 2 from January 1975 to February 1982
Landsat 3 from March 1978 to March 1983
Landsat 4 from July 1982 to December 1993
Landsat 5 from 1984 to October 1992, and from June 2012 to January 2013
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 1-5 MSS Level 1 data. For an overview of all API parameters see the API Reference.
|services-uswest2.sentinel-hub.com/api||Global coverage from July 1972 to October 1992 and from June 2012 to January 2013|
landsat-mss-l1  (previously
LMSSL1) as the value of the
input.data.type parameter in your API requests. This is mandatory and will ensure you get Landsat 1-5 MSS Level 1 data.
The collection is currently in the preview stage and might thus change.
landsat-mss-l1 stands for Landsat Multispectral Scanner System Level 1.
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 52,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.|
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 ||Green (500-600 nm)||60m|
|B02 ||Red (600-700 nm)||60m|
|B03 ||Ultra Red (700-800 nm)||60m|
|B04 ||Near Infrared (NIR) (800-1100 nm)||60m|
|BQA||Quality Assessment band (QA)||60m|
|QA_RADSAT||Radiometric Saturation and Terrain Occlusion QA Band||60m|
|dataMask||The mask of data/no data pixels (more).||N/A |
: On Landsat 1-3, the bands 1-3 were from the RBV instrument (Return Beam Vidicon), and the bands from the MSS instrument were the bands 4-7. For the sake of consistency and given that there's no RBV data, we decided to name MSS bands of these Landsats also B01-B04, respectively.
: 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 - B04
|Reflectance (unitless)||REFLECTANCE ||UINT8||0 - 0.4||Higher values in infrared bands. Reflectance values can easily be above 1.|
|BQA||Pixel quality assessment (unitless)||DN||UINT16||bit-packed combination |
|QA_RADSAT||Radiometric saturation quality assessment (unitless)||DN||UINT16||bit-packed combination |
|dataMask||N/A||DN||N/A||0 - no data|
1 - data
: Top of the Atmosphere Reflectance, which is obtained using the scene center sun angle.
: Info here.
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-mss-l1||Data availability and coverage is the same as in the basic facts|
eo:cloud_covercloud cover percentage