Versions Compared

Old Version 66

changes.mady.by.user Jan Musial

Saved on

compared with

New Version 67

changes.mady.by.user Jan Musial

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
baselineCollectionStringAttribute??To be discussed with Jordi

shoud be reflected in the STAC collection name e.g. "Sentinel-2 L2A Collection1"
002
beginningDateTimeDateTimeOffset

start_datetime

datetime

start_datetime

datetime



2023-07-10T00:47:16.702921Z2024-05-04T00:02:03.199Z
cloudCoverDoubleAttribute
?eo:cloud_cover

2828
coastalCoverDoubleAttributeX



10.009
cycleNumberIntegerAttribute
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
endingDateTimeDateTimeOffset
core STAC attributeend_datetime

2023-07-10T00:47:16.702921Z2024-05-04T00:05:03.199Z
freshInlandWaterCoverDoubleAttributeX
s3:fresh_inland_water

00
instrumentShortNameStringAttribute
core STAC attributeinstruments

olciOLCI
landCoverDoubleAttribute
?s3:land

22
operationalModeStringAttribute
????????????????

To be harmonized across missions
Earth Observation
orbitDirectionStringAttribute
satsat:orbit_state

descendingDESCENDING
orbitNumberIntegerAttribute
satsat:absolute_orbit

4276742767
platformSerialIdentifierStringAttribute
core STAC attributeplatform

sentinel-3aA
platformShortNameStringAttribute
core STAC attributeconstellation

sentinel-3SENTINEL-3
processingDateDateTimeOffset
processingprocessing:datetime

2023-07-10T00:47:16.702921Z2024-05-04T02:11:42+00:00
processingLevelStringAttribute
processingprocessing:level

L22
processorNameStringAttributeX


To be dropped and discussed with ESA experts.PUGPUG
processorVersionStringAttributeX

 





03.50
<sentinel3: processingBaseline>PB_ID.xxx.yy.zz </sentinel3: processingBaseline> from SAFE does not exists in Odata

part of the processing:version

OL__L1_.003.03.02

OL - instrument

L1 - processing level 

003 - baselineCollection

03.02 - S3 processorVersion

s3:processing_baseline

To be discussed with Jordi. https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-3-olci/processing-

baseline		03.45

baseline

<sentinel3: processingBaseline>PB_ID.xxx.yy.zz </sentinel3: processingBaseline>


<PB_ID> is unique and has as fixed format with 7 alphanumeric characters.
The definition of xxx.yy.zz version is the following:
xxx : baseline collection (starting from 002, 003 or 004 depending on the chain)
yy : minor changes in IPF or in static ADF (starting from zero for new baseline collection)
zz: changes in L0/PUG processing/task tables/PM or any other changes not expected to affect
the quality of the products (starting from zero when new baseline collection or minor change
is introduced). Only one PB_ID is applied on OLCI L1: e.g. in case of change of RAC or SPC
IPF which has no significant impact on product quality, zz shall be incremented.

03.50


productTypeStringAttribute
productproduct:type

OL_2_LFR___OL_2_LFR___
relativeOrbitNumberIntegerAttribute
sat:relative_orbitsat:relative_orbit

5959
salineWaterCoverDoubleAttributeX
s3:saline_water

442
tidalRegionCoverDoubleAttributeX
s3:tidal_region

20
timelinessStringAttribute
productproduct:timeliness
product:timeliness_category

PT3H

NR

NR

...

Field nameData TypeRelevant to general public?
Potential future extension or field
Comments
Multi-Mission
s1:processing_datetime
s2:generation_time		date-timeYesprocessing: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		stringYesto be included in the CDSE STAC and added to eopf extensionOData: productGroupId
S2 Example: GS2A_20240308T100841_045493_N05.10
s2:product_type
s3:product_type
s5p:product_type		stringNo?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		stringYes?
s1:product_timeliness
s3:processing_timeliness		stringYes?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_IDstringNo?

s1:orbit_sourcestringNo?

s1:product_identifierstring?externalIds?
s1:resolutionstringNo?

s1:slice_numberstringNo

s1:total_slicesstringNo

Sentinel-2 
s2:tile_idstringYes?

grid:code (querable)

and
mgrs:utm_zone (not querable)
mgrs:grid_square (not querable)
mgrs:latitude_band (not querable)

  • mgrs extention requires 3 fields (56, NN, G)
  • grid:code is one field (MGRS-56NNG)
  • Odata: tileId (56NNG)
s2:product_uristringNO To be removedNONEMight be needed in the S2 extension by some other users of the extensions.
s2:datastrip_idstringYes?EOPFOData field: datastripId
Example: S2A_OPER_MSI_L2A_DS_2APS_20240308T143352_S20240308T101546_N05.10
s2:datatake_typestringON HOLD similar to instrument_mode in the SAREOPFOData: operationalMode
Example: INS-NOBS
s2:processing_baselinestringYesprocessing:version (PR)OData: processorVersion, example: 5.1
STAC example: 05.10
s2:reflectance_conversion_factornumberTo be removedTo be removedExample: 1.01707999697991
Sentinel-3 
s3:gsdvariousNo?

to be dropped or used acrossed all missions

gsd as a single value?

"gsd" STAC core attribute 


s3:lrm_modenumberYes?altm:instrument_type
s3:sar_modenumberYes?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_modestring?

s5p:collection_identifierstring?

s5p:spatial_resolution[number]?raster:spatial_resolution as a single value?
Sentinel-5 Container Objects 
s5p:aer_aiAer Ai ObjectFlatten into top-level propertiesNone
s5p:aer_lhAer Lh ObjectFlatten into top-level propertiesNone
s5p:ch4CH4 ObjectFlatten into top-level propertiesNone
s5p:cloudCloud ObjectFlatten into top-level propertiesNone
s5p:coCO ObjectFlatten into top-level propertiesNone
s5p:hchoHCHO ObjectFlatten into top-level propertiesNone
s5p:no2NO2 ObjectFlatten into top-level propertiesNone
s5p:npbd3NPBD ObjectFlatten into top-level propertiesNone
s5p:npbd6NPBD ObjectFlatten into top-level propertiesNone
s5p:npbd7NPBD ObjectFlatten into top-level propertiesNone
s5p:o3O2 ObjectFlatten into top-level propertiesNone
s5p:o3_tclO3 TCL ObjectFlatten into top-level propertiesNone
s5p:so2SO2 ObjectFlatten into top-level propertiesNone
Sentinel 5P Container Object Fields
These fields appear in at least one of the Sentinel-5 Container Objects above.

input_bandstring / [string]No?

irradiance_accompaniedstringNo?

geolocation_grid_from_bandintegerNo?

cloud_modestringNo?

shape_ccd[integer]No?

shape_csa[integer]No?

stratosphere_start_datetimestring?

stratosphere_end_datetimestring?

troposphere_start_datetimestring?

troposphere_end_datetimestring?

input_orbits[integer]No?

input_files[string]No?

analysed_s5p_bandintegerNo?

VIIRS_band[integer]No?

number_of_scaled_fovintegerNo?

...