Collections and ids
A collection is one product from one mission family, such as Sentinel-2 Level-2A. Each has a canonical id from schema v1 and a list of aliases that work wherever the id does.
The Data section has a page per collection with its bands, scale and offset, quality layers, data availability and example requests.
Available now
Section titled “Available now”| Canonical id | What it holds | Main aliases | Upstream |
|---|---|---|---|
sentinel-2-l2a |
Sentinel-2 MSI surface reflectance (Sen2Cor), Collection 1, from Sentinel-2A, 2B and 2C | sentinel-2-c1-l2a, S2L2A |
Earth Search sentinel-2-c1-l2a |
landsat-ot-l2 |
Landsat 8 and 9 OLI/TIRS Collection 2 Level-2 surface reflectance and surface temperature | landsat-c2-l2 |
Earth Search landsat-c2-l2, Landsat 8 and 9 only |
Every alias schema v1 lists for these two collections works, matched without regard to case, including SENTINEL2_L2A (CDSE openEO) and LOTL2 (Sentinel Hub). Earth Search ids are mapped both ways: you can send either, and responses use the canonical id. landsat-ot-l2 returns Landsat 8 and 9 scenes only.
Aliases in paths and bodies
Section titled “Aliases in paths and bodies”An alias works in a path, a query string or a request body:
curl -s https://api.satellitedata.net/v1/collections/S2L2AWhen you fetch a collection by alias, the answer is the canonical document with a Content-Location header pointing at the canonical URL.
Item ids
Section titled “Item ids”Item ids stay native, so you can match them against other catalogs:
- Sentinel-2: ESA-derived ids as Earth Search writes them, for example
S2C_T15TVK_20260712T171233_L2A. - Landsat: USGS product ids, for example
LC08_L2SP_027029_20260718_02_T1.
Collection documents
Section titled “Collection documents”GET /v1/collections/{collectionId} returns a STAC collection with members from schema v1 under the sdn: prefix, such as sdn:aliases and sdn:attribution. See one collection.
Attribution
Section titled “Attribution”Show the credit line near any map or image you make from the data:
| Collection | Credit line |
|---|---|
sentinel-2-l2a |
Contains modified Copernicus Sentinel data {years} |
landsat-ot-l2 |
Landsat data courtesy of the U.S. Geological Survey |
{years} is the acquisition years of the scenes you used, such as 2026. Collection documents carry the template in sdn:attribution.
Coming later
Section titled “Coming later”Schema v1 defines 13 collections. Besides the two above:
| Canonical id | What it holds |
|---|---|
landsat-etm-l2 |
Landsat 7 ETM+ Level-2 |
landsat-tm-l2 |
Landsat 4 and 5 TM Level-2 |
hls |
NASA Harmonized Landsat Sentinel-2 v2.0 |
optical-sr |
A virtual collection that searches Sentinel-2 L2A, Landsat Level-2 and HLS at once and removes duplicate overpasses |
dem |
Copernicus DEM |
sentinel-1-rtc |
Sentinel-1 radiometric terrain corrected backscatter |
sentinel-2-l1c |
Sentinel-2 top-of-atmosphere |
landsat-ot-l1, landsat-etm-l1, landsat-tm-l1, landsat-mss-l1 |
Landsat Level-1 archives |
Aliases that contain a slash, such as COPERNICUS/S2_SR_HARMONIZED (Google Earth Engine), work in bodies and query strings but not in path segments. The full list is in GET /v1/schema.
GET /v1/collections lists only the collections that are live, so a client can discover new ones as they arrive.