Data Specification
Our cloudless data is a 10-band multi-spectral Sentinel-2 MSI product. All satellite data, including, original "cloud-free" images, are processed and modified to improve on consistency (i.e. limiting atmospheric effects). The cloudless data has been corrected with Sen2Cor for bottom-of-atmosphere disturbance beforehand. All of our Sentinel-2 data is harmonized to the pre-January 25 baseline. This harmonization allows for more efficient time-series analysis across multiple years.
The API data is served in either uin8
or int16
, and the designated value for no data
is -32768
. The reflectance scaling factor for spectral bands is 10000
, while for indices the values should be divided by 32767
. All indices precomputed on our servers range from -1
to 1
. If larger ranges are needed, we recommend that users download the necessary bands and then perform the index calculation.
Band Information
The imagery is available as multi-spectral GeoTIFFs (.tif
) with the following spectral bands:
Band Name | Band Name | Resolution (m) | Wavelength (nm) | Band Order |
---|---|---|---|---|
Blue | B2 | 10 | 492 ± 33 | 1 |
Green | B3 | 10 | 559 ± 18 | 2 |
Red | B4 | 10 | 664 ± 15 | 3 |
Red-Edge 1 | B5 | 10 | 704 ± 8 | 4 |
Red-Edge 2 | B6 | 10 | 740 ± 7 | 5 |
Red-Edge 3 | B7 | 10 | 782 ± 10 | 6 |
Near Infrared | B8 | 10 | 732 ± 53 | 7 |
Narrow Near Infrared | B8a | 10 | 864 ± 11 | 8 |
Shortwave Infrared 1 | B11 | 10 | 1613 ± 47 | 9 |
Shortwave Infrared 2 | B12 | 10 | 2200 ± 92 | 10 |
Metadata
Additional metadata tags have been integrated into GeoTIFF files retrieved through the Processing API:
- IMAGE_DATE: Represents the date of the image, formatted as
yyyymmdd
. - MODEL_VERSION: Indicates the version of the model used for prediction.
- IMAGE_VERSION: Notifies users of any modifications to the image. If a tile is regenerated for any reason, this number increments by one.
- CONSTELLATIONS: Lists the satellite constellations used by the model when generating the image (e.g.,
Sentinel1
orSentinel1,Sentinel2,Landsat89
).
When a request overlaps multiple tiles, the IMAGE_VERSION
tag will list values for each intersecting tile, separated by commas. The order of these values corresponds to the internal positioning of the tiles within our data storage, not by numerical sorting. For instance, if a request intersects four tiles where three use image version 13
and one uses image version 15
, the IMAGE_VERSION
tag might display as 13,15,13,13
. This arrangement ensures that any change in the data—from 13,15,13,13
to 13,15,13,15
—indicates that the last tile in our internal sorting has been updated to version 15
.