CDSE STAC development roadmap
Within the Copernicus Data Space Ecosystem there are two STAC catalogues available:
1. Production catalogue available here: https://radiantearth.github.io/stac-browser/#/external/catalogue.dataspace.copernicus.eu/stac
2. Development catalogue available here: https://radiantearth.github.io/stac-browser/#/external/pgstac.demo.cloudferro.com
| odata_attributes | data type | to be removed | target STAC extension | STAC Counterpart | collection level | item level | asset level | Notes | OData ICD definition | STAC definition | Example STAC | Example Odata |
| areaOfInterest | StringAttribute | X | region | name | mandatory | optional | na | can be set as a keyword at collection level | CLMS specific | A human-readable name of the relevant region. | global | |
| beginningDateTime | DateTimeOffsetAttribute | STAC core attribute | start_datetime | na | mandatory | na | beginning of the interval that the data is valid. RFC beginning of interval start or end of second? | CLMS specific | The first or start date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6. | 2025-06-21T00:00:00.000000Z | 2025-06-21T00:00:00.000000Z | |
| cellID | IntegerAttribute | ? | grid | code | na | optional | na | New grid variants may need to be added to the extension. | CLMS specific | CLMS specific | 1300000000033 | |
| Checksum | StringAttribute | file | checksum | na | na | mandatory | Represents the known checksums for the product’s physical data, providing a unique value for supporting download integrity check. At least MD5 checksum is mandatory. | Provides a way to specify file checksums (e.g. BLAKE2, MD5, SHA1, SHA2, SHA3). The hashes are self-identifying hashes as described in the Multihash specification and must be encoded as hexadecimal (base 16) string with lowercase letters. | ||||
| collectionName | StringAttribute | X | na | na | na | na | na | can be set as a keyword at collection level | CLMS specific | CLMS specific | TO BE REMOVED | CLMS |
| component | StringAttribute | X | na | na | na | na | na | can be set as a keyword at collection level | CLMS specific | CLMS specific | bio-geophysical | |
| consolidationPeriod | IntegerAttribute | X | na | na | na | na | na | can be set as a keyword at collection level | CLMS specific | CLMS specific | 6 | |
| ContentDate:End | DateTimeOffsetAttribute | STAC core attribute | end_time | na | mandatory | na | nominal end | The last or end date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6. | 2025-06-30T23:59:59.999999Z | 2025-06-30T23:59:59.999999Z | ||
| ContentDate:Start | DateTimeOffsetAttribute | STAC core attribute | start_datetime | na | mandatory | na | nominal start | The first or start date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6. | 2025-06-21T00:00:00.000000Z | 2025-06-21T00:00:00.000000Z | ||
| ContentLength | IntegerAttribute | file | size | na | na | mandatory | Actual size in bytes (B) of the downloadable product package | The file size, specified in bytes. | 2751622412 | 2751622412 | ||
| ContentType | StringAttribute | STAC core attribute | type | na | na | mandatory | The Mime type of the product | Media type of the asset. See the common media types in the best practice doc for commonly used asset types. | image/tiff; application=geotiff; profile=cloud-optimized | application/netcdf | ||
| datasetAlias | StringAttribute | X | can be set as a keyword at collection level | CLMS specific | CLMS specific | wl-lakes_global_vector_daily | ||||||
| datasetIdentifier | StringAttribute | STAC core attribute | collection | mandatory | na | na | CLMS specific | The | wl-lakes_global_vector_daily_v2 | wl-lakes_global_vector_daily_v2 | ||
| datasetShortName | StringAttribute | X | can be set as a keyword at collection level | CLMS specific | CLMS specific | lwl | ||||||
| datasetVersion | IntegerAttribute | version | version | mandatory | na | na | it should be included in the collection name | CLMS specific | Version of the context this fields is used in (e.g. Asset or Collection). | 2 | ||
| endingDateTime | DateTimeOffsetAttribute | STAC core attribute | end_time | na | mandatory | na | CLMS specific | The last or end date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6. | 2025-06-30T23:59:59.999999Z | 2025-06-30T23:59:59.999999Z | ||
| EvictionDate | DateTimeOffsetAttribute | timestamps | expires | na | mandatory | na | Date when the data file will be removed from the Interface Delivery Point. | Date and time the corresponding data (see below) expires (is not valid any longer), in UTC. | 9999-12-31T23:59:59.999999Z | 9999-12-31T23:59:59.999999Z | ||
| fileFormat | StringAttribute | X | it should be included in the collection name | CLMS specific | CLMS specific | geojson | ||||||
| gridLabel | StringAttribute | STAC core attribute | gsd | mandatory | na | na | Required for all rasters minimum nominal grid spacing for a collection | CLMS specific | The nominal Ground Sample Distance for the data, as measured in meters on the ground. There are many definitions of GSD. The value of this field should be related to the spatial resolution at the sensor, rather than the pixel size of images after orthorectification, pansharpening, or scaling. The GSD of a sensor can vary depending on geometry (off-nadir / grazing angle) and wavelength, so it is at the discretion of the implementer to decide which value most accurately represents the GSD. For example, Landsat8 optical and short-wave IR bands are all 30 meters, but the panchromatic band is 15 meters. The gsd should be 30 meters in this case because that is the nominal spatial resolution at the sensor. | 300 | 300m | |
| Id | StringAttribute | X | UUID | It is a universally unique identifier (UUID). The Id is a local identifier for the product instance within the Data Access, assigned during the product ingestion. | NA | c46db475-d910-431f-8f36-d12bf3a93e7f | ||||||
| instrumentShortName | StringAttribute | STAC core attribute | instruments | mandatory | mandatory | na | Can be array of strings. | name of the Instrument | An array of all the sensors used in the creation of the data. For example, data from the Landsat-8 platform is collected with the OLI sensor as well as the TIRS sensor, but the data is distributed together so would be specified as ['oli', 'tirs'] | VEGETATION | VEGETATION | |
| metricGridSpacing | IntegerAttribute | STAC core attribute | gsd | mandatory | mandatory | na | CLMS specific | The nominal Ground Sample Distance for the data, as measured in meters on the ground. There are many definitions of GSD. The value of this field should be related to the spatial resolution at the sensor, rather than the pixel size of images after orthorectification, pansharpening, or scaling. The GSD of a sensor can vary depending on geometry (off-nadir / grazing angle) and wavelength, so it is at the discretion of the implementer to decide which value most accurately represents the GSD. For example, Landsat8 optical and short-wave IR bands are all 30 meters, but the panchromatic band is 15 meters. The gsd should be 30 meters in this case because that is the nominal spatial resolution at the sensor. | 1000 | 1000 | ||
| missionShortName | StringAttribute | X | na | na | na | na | na | CLMS specific | CLMS specific | NOT TO BE USED | SPOT4,SPOT5,PROBAV | |
| ModificationDate | DateTimeOffsetAttribute | STAC core attribute | updated | na | mandatory | na | modification of metadata in OData/STAC cataloguea and not the modification of data/assets itself | Date when the product metadata was last modified. | Date and time the corresponding STAC entity or Asset (see below) was updated last, in UTC. | 2025-07-02T10:08:46.236018Z | 2025-07-02T10:08:46.236018Z | |
| Name | StringAttribute | STAC core attribute | id | na | mandatory | na | product name unique within a Collection, | Data file name | It is important that an Item identifier is unique within a Collection, and that the Collection identifier in turn is unique globally. Then the two can be combined to give a globally unique identifier. Items are strongly recommended to have Collections, and not having one makes it more difficult to be used in the wider STAC ecosystem. If an Item does not have a Collection, then the Item identifier should be unique within its root Catalog or root Collection. | c_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_nc | c_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_nc | |
| nominalDate | DateTimeOffsetAttribute | STAC core attribute | datetime | na | mandatory | na | CLMS specific | This is likely the acquisition (in the case of single camera type captures) or the 'nominal' or representative time in the case of assets that are combined together. Though time can be a complex thing to capture, for this purpose keep in mind the STAC spec is primarily searching for data, so use whatever single date and time is most useful for a user to search for. STAC content extensions may further specify the meaning of the main datetime field, and many will also add more datetime fields. All times in STAC metadata should be in Coordinated Universal Time (UTC). If there's clearly no meaningful single 'nominal' time, it is allowed to use null instead. In this case it is required to specify a temporal interval with the fields start_datetime and end_datetime from common metadata. | 2025-06-21T00:00:00.000000Z | 2025-06-21T00:00:00.000000Z | ||
| Online | StringAttribute | X | na | na | na | na | na | Indication of current online presence. | na | TRUE | ||
| OriginDate | DateTimeOffsetAttribute | STAC core attribute | created | na | mandatory | na | When generated by the CLMS producer | Date and time of the product at the source (e.g. Publication date time on the PRIP). Time is in UTC | Creation date and time of the corresponding STAC entity or Asset (see below), in UTC. | 2025-07-02T09:30:01.282075Z | 2025-07-02T09:30:01.282075Z | |
| platformAcronym | StringAttribute | STAC core attribute | constellation | mandatory | mandatory | na | CLMS specific | The name of a logical collection of one or more platforms that have similar payloads and have their orbits arranged in a way to increase the temporal resolution of acquisitions of data with similar geometric and radiometric characteristics. This field allows users to search for related data sets without the need to specify which specific platform the data came from, for example, from either of the Sentinel-2 satellites. Examples include landsat-8 (Landsat-8, a constellation consisting of a single platform), sentinel-2 (Sentinel-2), rapideye (operated by Planet Labs), and modis (NASA EOS satellites Aqua and Terra). In the case of modis, this is technically referring to a pair of sensors on two different satellites, whose data is combined into a series of related products. | Sentinel-2 or multimission | Sentinel-2 | ||
| platformShortName | StringAttribute | STAC core attribute | platform | mandatory | mandatory | na | name of the Platform | The unique name of the specific platform the instrument is attached to. For satellites this would be the name of the satellite, whereas for drones this would be a unique name for the drone. Examples include landsat-8 (Landsat-8), sentinel-2a and sentinel-2b (Sentinel-2), terra and aqua (part of NASA EOS, carrying the MODIS instruments), mycorp-uav-034 (hypothetical drone name), and worldview02 (Maxar/DigitalGlobe WorldView-2). | Sentinel-2A or multimission | Senitnel-2A | ||
| processingCenter | StringAttribute | processing | facility | na | mandatory | na | name of the Procesing Centre | The name of the facility that produced the data. For example, Copernicus S1 Core Ground Segment - DPA for product of Sentinel-1 satellites. | VITO | |||
| productVersion | StringAttribute | processing | version | na | mandatory | na | CLMS specific | The version of the primary processing software or processing chain that produced the data. For example, this could be the processing baseline for the Sentinel missions. | v3.0.1 | |||
| PublicationDate | DateTimeOffsetAttribute | timestamps | published | na | mandatory | na | Publication date and time of the product (time at which the product becomes accessible for retrieval to the client within the DA). | Date and time the corresponding data (see below) was published the first time, in UTC. | 2025-07-02T10:08:46.236018Z | |||
| S3Path | StringAttribute | STAC core attribute | href | na | na | mandatory | S3 path in the CDSE repository | S3 path in the CDSE repository | /eodata/CLMS/bio-geophysical/vegetation_indices/ndvi_global_300m_10daily_v2/2025/06/21/c_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_nc | |||
| swiSubParameter | StringAttribute | ? | CLMS specific | CLMS specific | CI | |||||||
| temporalRepeatRate | StringAttribute | X | can be set as a keyword at collection level | CLMS specific | CLMS specific | 10daily | ||||||
| vppSeason | StringAttribute | ? | CLMS specific | CLMS specific | S2 | |||||||
| vppSubParameter | StringAttribute | ? | CLMS specific | CLMS specific | TPROD | |||||||
| wlBasinName | StringAttribute | ? | CLMS specific | CLMS specific | Mackenzie River | |||||||
| wlLakeName | StringAttribute | ? | CLMS specific | CLMS specific | athabasca | |||||||
| wlRiverName | StringAttribute | ? | CLMS specific | CLMS specific | Ya-lu-cang-bu-jiang |
| Sentinel-5P Odata attributes | data type | to be removed | target STAC extension (in bold new attributes to be added) | STAC Counterpart | asset level | Description | Example STAC | Example Odata |
| beginningDateTime | DateTimeOffsetAttribute | attribute | start_datetime datetime | 2018-11-03T23:58:55.121559Z | 2024-05-17T00:23:29.000Z | |||
| endingDateTime | DateTimeOffsetAttribute | core STAC attribute | end_datetime | 2018-11-03T23:58:55.121559Z | 2024-05-17T00:27:08.000Z | |||
| instrumentShortName | StringAttribute | core STAC attribute | instruments | tropomi | TROPOMI | |||
| orbitNumber | IntegerAttribute | sat | sat:absolute_orbit | 34158 | 34158 | |||
| parentIdentifier | StringAttribute | X | urn:ogc:def:EOP:ESA:SENTINEL.S5P_TROP_L2__NO2___ | |||||
| platformShortName | StringAttribute | core STAC attribute | constellation | sentinel-5p | SENTINEL-5P | |||
| processingCenter | StringAttribute | processing | processing:facility | ? | pdgs-op | PDGS-OP | ||
| processingDate | DateTimeOffsetAttribute | processing | processing:datetime | 2018-11-03T23:58:55.121559Z | 2024-05-17T01:26:59.613000+00:00 | |||
| processingLevel | StringAttribute | processing | processing:level | L2 | L2 | |||
| processingMode | StringAttribute | product | product:timeliness product:timeliness_category |
NRT | NRTI | |||
| processorName | StringAttribute | X | TROPNLL2DP | |||||
| processorVersion | StringAttribute | X | For Sentinel-5P I believe the processing:version should be taken from the netCDF global attribute processor_version | 20600 | ||||
| productType | StringAttribute | product:type | product:type | L2__NO2___ | L2__NO2___ |
| Sentinel-1 Odata attributes | data type | to be removed | target STAC extension (in bold new attributes to be added) | STAC Counterpart | asset level | Description | Example STAC | Example Odata |
| beginningDateTime | DateTimeOffsetAttribute | core STAC attribute | start_datetime datetime | 2018-11-03T23:58:55.121559Z | 2024-05-14T00:06:28.688Z | |||
| completionTimeFromAscendingNode | DoubleAttribute | sat:anx_end_offset | 238903.7 | |||||
| cycleNumber | IntegerAttribute | sat:orbit_cycle | sat:orbit_cycle | 322 | ||||
| datatakeID | IntegerAttribute | EOPF | 429004 | |||||
| endingDateTime | DateTimeOffsetAttribute | core STAC attribute | end_datetime | 2018-11-03T23:59:55.112875Z | 2024-05-14T00:06:53.687Z | |||
| instrumentConfigurationID | IntegerAttribute | EOPF | 7 | |||||
| instrumentShortName | StringAttribute | core STAC attribute | instruments | sar | SAR | |||
| operationalMode | StringAttribute | sar:instrument_mode | sar:instrument_mode | IW | IW | |||
| orbitDirection | StringAttribute | sat | sat:orbit_state | descending | ASCENDING | |||
| orbitNumber | IntegerAttribute | sat | sat:absolute_orbit | 42767 | 53860 | |||
| origin | StringAttribute | processing | processing:facility | production service-serco | ESA | |||
| platformSerialIdentifier | StringAttribute | core STAC attribute | platform | sentinel-1a | A | |||
| platformShortName | StringAttribute | core STAC attribute | constellation | sentinel-1 | SENTINEL-1 | |||
| polarisationChannels | StringAttribute | sar:polarizations | sar:polarizations | '[VV,VH]' | VV&VH | |||
| processingCenter | StringAttribute | processing | processing:facility | production service-serco | Production Service-SERCO | |||
| processingDate | DateTimeOffsetAttribute | processing | processing:datetime | 2024-05-14T08:04:12.593998+00:00 | ||||
| processingLevel | StringAttribute | processing | processing:level | L1 | LEVEL1 | |||
| processorName | StringAttribute | X | to be dropped | Sentinel-1 IPF | ||||
| processorVersion | StringAttribute | X | 3.71 | |||||
| processing:version (PR) | processing:version (PR) | to be added in the future? what to do with s-1 baseline? | ||||||
| productClass | StringAttribute | X | S | |||||
| productComposition | StringAttribute | X | Slice/Slice-Partial | |||||
| productType | StringAttribute | product:type | IW_GRDH_1S | IW_GRDH_1S | ||||
product:type | sar:product_type | to be moved to product:type (PR) | GRD | |||||
| relativeOrbitNumber | IntegerAttribute | sat:relative_orbit | sat:relative_orbit | 63 | ||||
| segmentStartTime | DateTimeOffsetAttribute | X | 2024-05-14T00:05:09.988000+00:00 | |||||
| sliceNumber | IntegerAttribute | X | 4 | |||||
| sliceProductFlag | BooleanAttribute | X | false | |||||
| startTimeFromAscendingNode | DoubleAttribute | sat:anx_start_offset | milliseconds from anx crossing | 213904.7 | ||||
| swathIdentifier | StringAttribute | X | IW | |||||
| timeliness | StringAttribute | product | product:timeliness product:timeliness_category |
Fast-24H | Fast-24h | |||
| totalSlices | IntegerAttribute | X | 20 | |||||
| sar:frequency_band | sar:frequency_band | collection level? | C |
| burst attributes | example | to be added to STAC |
| linesPerBurst | 1493 | |
| samplesPerBurst | 21673 | |
| subswath | "IW1" should be string | sar:subswaths_id |
| polarization | vh | sar:polarizations |
| start line | 1493 | |
| azimuthTime | 2024-05-10T00:40:19.788314 | |
| sensingTime | 2024-05-10T00:40:19.788314 | start_datetime datetime |
| byteOffset | 129538967 | |
| burstId_relative | 8690 should be string used to be called frame_id | sar:relative_burst |
| burstId_absolute | 115560765 | |
| burstID_internal | 2 |
| Sentinel-3 Odata attributes | data type | to be removed | target STAC extension (in bold new attributes to be added) | STAC Counterpart | asset level | Description | Example STAC | Example Odata |
| baselineCollection | StringAttribute | X | X | processing:version | OL__L1_.003.03.02, reflected in the: processing:version | 003 | ||
| beginningDateTime | DateTimeOffset | start_datetime datetime | start_datetime datetime | 2023-07-10T00:47:16.702921Z | 2024-05-04T00:02:03.199Z | |||
| cloudCover | DoubleAttribute | ? | eo:cloud_cover | 28 | 28 | |||
| coastalCover | DoubleAttribute | X | 1 | 0.009 | ||||
| cycleNumber | IntegerAttribute | sat:orbit_cycle | sat:orbit_cycle | The orbital cycle is 27 days (14+7/27 orbits per day, 385 orbits per cycle). The orbit cycle is the time taken for the satellite to pass over the same geographical point on the ground. | 112 | |||
| endingDateTime | DateTimeOffset | core STAC attribute | end_datetime | 2023-07-10T00:47:16.702921Z | 2024-05-04T00:05:03.199Z | |||
| freshInlandWaterCover | DoubleAttribute | X | s3:fresh_inland_water | 0 | 0 | |||
| instrumentShortName | StringAttribute | core STAC attribute | instruments | olci | OLCI | |||
| landCover | DoubleAttribute | ? | s3:land | 2 | 2 | |||
| operationalMode | StringAttribute | ? | To be harmonized across missions | Earth Observation | ||||
| orbitDirection | StringAttribute | sat | sat:orbit_state | descending | DESCENDING | |||
| orbitNumber | IntegerAttribute | sat | sat:absolute_orbit | 42767 | 42767 | |||
| platformSerialIdentifier | StringAttribute | core STAC attribute | platform | sentinel-3a | A | |||
| platformShortName | StringAttribute | core STAC attribute | constellation | sentinel-3 | SENTINEL-3 | |||
| processingDate | DateTimeOffset | processing | processing:datetime | 2023-07-10T00:47:16.702921Z | 2024-05-04T02:11:42+00:00 | |||
| processingLevel | StringAttribute | processing | processing:level | L2 | 2 | |||
| processorName | StringAttribute | X | To be dropped and discussed with ESA experts. | PUG | PUG | |||
| processorVersion | StringAttribute | X |
| 03.50 | ||||
| <sentinel3: processingBaseline>PB_ID.xxx.yy.zz </sentinel3: processingBaseline> from SAFE does not exists in Odata | processing:version OL__L1_.003.03.02 OL - instrument L1 - processing level 003 - baselineCollection 03.02 - S3 processorVersion | To be discussed with Jordi. https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-3-olci/processing-baseline | <sentinel3: processingBaseline>PB_ID.xxx.yy.zz </sentinel3: processingBaseline> <PB_ID> is unique and has as fixed format with 7 alphanumeric characters. | |||||
| productType | StringAttribute | product | product:type | OL_2_LFR___ | OL_2_LFR___ | |||
| relativeOrbitNumber | IntegerAttribute | sat:relative_orbit | sat:relative_orbit | 59 | 59 | |||
| salineWaterCover | DoubleAttribute | X | s3:saline_water | 44 | 2 | |||
| tidalRegionCover | DoubleAttribute | X | s3:tidal_region | 2 | 0 | |||
| timeliness | StringAttribute | product | product:timeliness product:timeliness_category |
NR | NR |
| Sentinel-2 Odata attributes | data type | to be removed | target STAC extension (in bold new attributes to be added) | querable | STAC Counterpart | asset level | Description | Example STAC | Example Odata |
| mediaContentType | StringAttribute | X | application/octet-stream | ||||||
| Id | StringAttribute | X | Odata internal id | X | 3e3b9d1a-18d5-43b8-83d8-564587ec3070 | ||||
| Name | StringAttribute | id (core STAC attribute) | X | s2:product_uri (to be removed) | product name. STAC "id" is without .SAFE | S2A_MSIL2A_20240308T100841_N0510_R022_T33UVR_20240308T143352 | S2B_MSIL2A_20240419T001429_N0510_R116_T56NNG_20240419T013152.SAFE | ||
| ContentType | StringAttribute | core STAC attribute | type | X | differs between Odata and STAC | image/jp2 | application/octet-stream | ||
| ContentLength | IntegerAttribute | file | file:size | X | in bytes | 720970508 | 720970508 | ||
| OriginDate | DateTimeOffsetAttribute | core STAC attribute | X | into eopf time of the publication at prip | 2024-03-08T14:33:52.000000Z | 2024-04-19T02:13:20.000Z | |||
| PublicationDate | DateTimeOffsetAttribute | core STAC attribute | X | published | 2024-03-08T14:33:52.000000Z | 2024-04-19T02:20:17.555Z | |||
| ModificationDate | DateTimeOffsetAttribute | core STAC attribute | X | updated | 2024-03-08T14:33:52.000000Z | 2024-04-19T02:21:14.300Z | |||
| Checksum | Checksum | file | file:checksum | X | Blake3/MD5 in Odata vs Multihash in STAC | ||||
| ContentDate.Start | DateTimeOffsetAttribute | core STAC attribute | X | datetime start_datetime | 2024-04-19T00:14:29.024Z | ||||
| ContentDate.End | DateTimeOffsetAttribute | core STAC attribute | X | end_datetime | 2024-04-19T00:14:29.024Z | ||||
| Footprint | X | X | X | X | |||||
| GeoFootprint | core STAC attribute | geometry | "GeoFootprint":{"type":"Polygon","coordinates": [[[153.9866661847601,0.945453049017732], [153.9866661847601,0.945453049017732]]]} | ||||||
| origin | StringAttribute | processing | processing:facility | from manifest or EUMETSAT | |||||
| cloudCover | DoubleAttribute | eo | X | eo:cloud_cover | 14.583966 | ||||
| orbitNumber | IntegerAttribute | sat | sat:absolute_orbit | 37179 | |||||
| sourceProduct | StringAttribute | X | S2B_OPER_MSI_L2A_TL_2BPS_20240419T013152_A037179_T56NNG_N05.10 S2B_OPER_MSI_L2A_DS_2BPS_20240419T013152_S20240419T001424_N05.10 | ||||||
| processingLevel | StringAttribute | processing | processing:level | L2 | S2MSI2A | ||||
| platformShortName | StringAttribute | core STAC attribute | constellation | sentinel-2 | SENTINEL-2 | ||||
| instrumentShortName | StringAttribute | core STAC attribute | instruments | msi | MSI | ||||
| relativeOrbitNumber | IntegerAttribute | sat | X | sat:relative_orbit | 22 | 116 | |||
| sourceProductOriginDate | StringAttribute | X | 2024-04-19T02:13:20Z 2024-04-19T01:32:14Z | ||||||
| platformSerialIdentifier | StringAttribute | core STAC attribute | platform | sentinel-2a | A | ||||
| beginningDateTime | DateTimeOffsetAttribute | core STAC attribute | start_datetime datetime | 2024-03-08T14:33:52.000000Z | 2024-04-19T00:14:29.024Z | ||||
| endingDateTime | DateTimeOffsetAttribute | core STAC attribute | end_datetime | 2024-03-08T14:33:52.000000Z | 2024-04-19T00:14:29.024Z | ||||
| granuleIdentifier | StringAttribute | X | None | s2:granule_id (removed) | S2A_OPER_MSI_L2A_TL_2APS_20240308T143352_A045493_T33UVR_N05.10 | S2A_OPER_MSI_L2A_TL_2APS_20240308T143352_A045493_T33UVR_N05.10 |
See the table below for details.
A priority should be to update the STAC Sentinel extensions to be less extensive at least. The plan is to find spaces in the general STAC community for these fields.
As a first step, we need to identify which fields are actually relevant to the general public.
For descriptions of the fields, please refer to the Sentinel extensions or the stactools-package implementations.
Idea is to keep a small variant of the Sentinel extensions as best practices, mostly using other extensions.
EOPF is for "private" fields that externals are not interested in.
| Field name | Data Type | Relevant to general public? | Potential future extension or field | Comments |
| Multi-Mission | ||||
| s1:processing_datetime s2:generation_time | date-time | Yes | processing:datetime (PR) | OData: processingDate S2 Example: 2024-04-19T01:31:52+00:00 (in STAC Z instead of +00:00) |
| s1:datatake_id s2:datatake_id | string | Yes | to be included in the CDSE STAC and added to eopf extension | OData: productGroupId S2 Example: GS2A_20240308T100841_045493_N05.10 |
| s2:product_type s3:product_type s5p:product_type | string | No? | product:type potentially restricted in s2 extension | What's the difference between name and type? Can it be just one property, e.g. the name? S2 example: S2MSI2A |
| s3:product_name s5p:product_name | string | Yes? | ||
| s1:product_timeliness s3:processing_timeliness | string | Yes? | product:timeliness potentially restricted in s2 extension | Can we find a common set of values for this? e.g. ISO 8601 Durations? |
| Sentinel-1 | ||||
| s1:instrument_configuration_ID | string | No? | ||
| s1:orbit_source | string | No? | ||
| s1:product_identifier | string | ? | externalIds? | |
| s1:resolution | string | No? | ||
| s1:slice_number | string | No | ||
| s1:total_slices | string | No | ||
| Sentinel-2 | ||||
| s2:tile_id | string | Yes? | grid:code (querable) |
|
| s2:product_uri | string | NO To be removed | NONE | Might be needed in the S2 extension by some other users of the extensions. |
| s2:datastrip_id | string | Yes? | EOPF | OData field: datastripId Example: S2A_OPER_MSI_L2A_DS_2APS_20240308T143352_S20240308T101546_N05.10 |
| s2:datatake_type | string | ON HOLD similar to instrument_mode in the SAR | EOPF | OData: operationalMode Example: INS-NOBS |
| s2:processing_baseline | string | Yes | processing:version (PR) | OData: processorVersion, example: 5.1 STAC example: 05.10 |
| s2:reflectance_conversion_factor | number | To be removed | To be removed | Example: 1.01707999697991 |
| Sentinel-3 | ||||
| s3:gsd | various | No? | to be dropped or used acrossed all missions "gsd" STAC core attribute | |
| s3:lrm_mode | number | Yes? | altm:instrument_type | |
| s3:sar_mode | number | Yes? | altm:instrument_mode | |
| Sentinel-3 (Asset-level properties) | ||||
| s3:spatial_resolution (in assets) | [number] | ? | raster:spatial_resolution as a single value? | |
| s3:altimetry_bands (in assets) | [Altimetry Band Object] | ? | bands STAC core attribute in STAC 1.1 | |
| Sentinel-5 | ||||
| s5p:processing_mode | string | ? | ||
| s5p:collection_identifier | string | ? | ||
| s5p:spatial_resolution | [number] | ? | raster:spatial_resolution as a single value? | |
| Sentinel-5 Container Objects | ||||
| s5p:aer_ai | Aer Ai Object | Flatten into top-level properties | None | |
| s5p:aer_lh | Aer Lh Object | Flatten into top-level properties | None | |
| s5p:ch4 | CH4 Object | Flatten into top-level properties | None | |
| s5p:cloud | Cloud Object | Flatten into top-level properties | None | |
| s5p:co | CO Object | Flatten into top-level properties | None | |
| s5p:hcho | HCHO Object | Flatten into top-level properties | None | |
| s5p:no2 | NO2 Object | Flatten into top-level properties | None | |
| s5p:npbd3 | NPBD Object | Flatten into top-level properties | None | |
| s5p:npbd6 | NPBD Object | Flatten into top-level properties | None | |
| s5p:npbd7 | NPBD Object | Flatten into top-level properties | None | |
| s5p:o3 | O2 Object | Flatten into top-level properties | None | |
| s5p:o3_tcl | O3 TCL Object | Flatten into top-level properties | None | |
| s5p:so2 | SO2 Object | Flatten into top-level properties | None | |
| Sentinel 5P Container Object Fields These fields appear in at least one of the Sentinel-5 Container Objects above. | ||||
| input_band | string / [string] | No | ||
| irradiance_accompanied | string | No? | ||
| geolocation_grid_from_band | integer | No? | ||
| cloud_mode | string | No? | ||
| shape_ccd | [integer] | No? | ||
| shape_csa | [integer] | No? | ||
| stratosphere_start_datetime | string | ? | ||
| stratosphere_end_datetime | string | ? | ||
| troposphere_start_datetime | string | ? | ||
| troposphere_end_datetime | string | ? | ||
| input_orbits | [integer] | No? | ||
| input_files | [string] | No | ||
| analysed_s5p_band | integer | No? | ||
| VIIRS_band | [integer] | No? | ||
| number_of_scaled_fov | integer | No? | ||
| Field name | Relevant to general public? | Potential future extension or field | Comments |
| General and Other | |||
| s3:land | ? | ||
| s2:unclassified_percentage | Yes, not queryable | classification:classes[*].percentage | |
| Clouds | |||
| s2:cloud_shadow_percentage | Yes, not queryable | classification:classes[*].percentage | |
| s2:high_proba_clouds_percentage | Yes, not queryable | classification:classes[*].percentage | |
| s2:medium_proba_clouds_percentage | Yes, not queryable | classification:classes[*].percentage | |
| s2:thin_cirrus_percentage | Yes, not queryable | classification:classes[*].percentage | |
| Water and Coastal | |||
| s2:water_percentage | Yes, queryable | new: eo:water_cover ? + classification:classes[*].percentage | |
| s3:closed_sea | ? | ||
| s3:fresh_inland_water | ? | ||
| s3:open_ocean | ? | ||
| s3:saline_water | ? | ||
| s3:tidal_region | ? | ||
| s3:coastal | ? | ||
| s3:continental_ice | ? | ||
| Unusable | |||
| s2:nodata_pixel_percentage | Yes, queryable | new: raster:nodata_percentage ? + classification:classes[*].percentage | |
| s3:bright | ? | ||
| s3:dubious_samples | ? | ||
| s3:duplicated | ? | ||
| s3:invalid | ? | ||
| s3:out_of_range | ? | ||
| s2:dark_features_percentage | Yes, not queryable | classification:classes[*].percentage | |
| s3:saturated s2:saturated_defective_pixel_percentage | Yes, not queryable | classification:classes[*].percentage | |
| Vegetation | |||
| s2:vegetation_percentage | Yes, queryable? | new: eo:vegetation_cover ? + classification:classes[*].percentage | |
| s2:not_vegetated_percentage | Yes, not queryable | classification:classes[*].percentage | |
Depending on the asset structure, some percentages may be provided as a classification percentages as proposed in https://github.com/stac-extensions/classification/pull/49
For completeness, the following fields did exist in the past and are already deprecated in favor of existing STAC fields:
| Field name | Data Type | New field name |
| s2:granule_id | string | Removed |
| s2:mgrs_tile | string | mgrs:* |
| s2:mean_solar_zenith | number | view:sun_azimuth |
| s2:mean_solar_azimuth | number | view:sun_elevation |
| s2:snow_ice_percentage s3:snow_or_ice | number | eo:snow_cover |
| s1:shape | [integer] | proj:shape |
| s1:processing_level | string | processing:level |
| s5p:shape | [integer] | proj:shape |
| s3:shape (in assets) | [integer] | proj:shape |
0. Simplify the geofootprint which is the largest attribute in the STAC response and slows down spatial querying (especially relevant for S-3 and S5P) ← to be provided by the Bureau d'Etude
1. Disable the overview displaying on items/assets level for selected collections e.g. Senitnel-3 where overviews generated in satellite projection is not displayed correctly.
2. [Done at the collection level] Implement the CEOS-ARD extension for Level-2 and Level-3 products https://github.com/stac-extensions/ceos-ard First would be the Sentinel-2 L2A (stac item example https://github.com/stac-extensions/ceos-ard/blob/main/examples/optical-sr/item.json), then Sentinel-3 and Sentinel-5P products. There is no CEOS ARD for radar data yet. Currently it is only for CEOS ARD PFSes (so surface reflectance and temperature, and aquatic reflectance)
3. Populate the development catalogue with the Sentinel-2 L1C and L2A products and make the online version of the catalogue publicly available for testing
4. Add new collections based on the on the stac-tools for Sentinel-1 (https://github.com/stactools-packages/sentinel1), Sentinel-3 (https://github.com/stactools-packages/sentinel3), Sentinel-5P (https://github.com/stactools-packages/sentinel5p) These collections will conform to the new Sentinel's extensions: https://github.com/stac-extensions/sentinel-1 , https://github.com/stac-extensions/sentinel-3 , https://github.com/stac-extensions/sentinel-5p
4. Update ASAP current "more generic" extensions: EO, SAR, etc. Add new Sentinel collections excluding the Sentinel specific extensions.
5. [In progress] Migrate some generic attributes from platform specific extension to more general extensions such as eo and sar. The rest of missions specific attributes (red crosses) should be maintained in the mission specific extensions not in the EOPF extension: https://github.com/CS-SI/eopf-stac-extension
7. Add to STAC Functionality of online/offline products. Add on demand product generation (url-s)
This product is absolutely normal with respect to the current IPF implementation. It is really small as only few pixels from the datastrip intersect this tile as you can see in the CDSE and QGIS screenshots attached (the rainbow effect visible for the TCI displayed in QGIS is normal, and due to the fact that the different spectral bands do not share exactly the same footprint).
A consequence of this very limited intersection between the tile footprint and the datastrip footprint is that we get only NaN viewing incidence values for several bands in the tile metadata, resulting in NaN mean viewing incidence values for these bands. This is because the grid on which the viewing incidence values are computed is very coarse (5 km x 5 km). Then this behaviour could happen sometimes for this kind of products (with limited intersection between the tile and the datastrip), and did happen before.