Versions Compared

Old Version 54

changes.mady.by.user Matthias Mohr

Saved on

compared with

New Version 55

changes.mady.by.user Jan Musial

Saved on

Key

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

...

Mappings not directly defined in the Sentinel extensions:

Sentinel-2  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
mediaContentTypeStringAttributeXXX


application/octet-stream
IdStringAttributeXXX
Odata internal idX3e3b9d1a-18d5-43b8-83d8-564587ec3070
NameStringAttribute
id (core STAC attribute)s2:product_uri (to be removed)
product name. STAC "id" is without .SAFES2A_MSIL2A_20240308T100841_N0510_R022_T33UVR_20240308T143352
.SAFE
S2B_MSIL2A_20240419T001429_N0510_R116_T56NNG_20240419T013152.SAFE
ContentTypeStringAttribute
core STAC attributetypeXdiffers between Odata and STACimage/jp2application/octet-stream
ContentLengthIntegerAttribute
filefile:sizeXin bytes720970508720970508
OriginDateDateTimeOffsetAttribute
core STAC attribute
datetime


into eopf

time of the publication at prip

2024-03-08T14:33:52.000000Z2024-04-19T02:13:20.000Z
PublicationDateDateTimeOffsetAttribute
core STAC attributepublished

2024-03-08T14:33:52.000000Z2024-04-19T02:20:17.555Z
ModificationDateDateTimeOffsetAttribute
core STAC attributeupdated

2024-03-08T14:33:52.000000Z2024-04-19T02:21:14.300Z
ChecksumChecksum
filefile:checksumXBlake3/MD5 in Odata vs Multihash in STAC

ContentDate.StartDateTimeOffsetAttribute
core STAC attribute

datetime

start_datetime


the same as
end_
STAC core datetime2024-03-08T14:33:52.000000Z2024-04-19T00:14:29.024Z
ContentDate.EndDateTimeOffsetAttribute
core STAC attributeend_datetime


the same as

start

end_datetime

2024-03-08T14:33:52.000000Z2024-04-19T00:14:29.024Z
Footprint
XXX



GeoFootprint

core STAC attributegeometry

"geometry":{"type":"Polygon","coordinates":[[[13.588086,50.543732],
[15.13777,50.552211],[15.134971,49.564676],[13.616763,49.556488],
[13.588086,50.543732]]]}		"GeoFootprint":{"type":"Polygon","coordinates":
[[[153.9866661847601,0.945453049017732],
[153.9866661847601,0.945453049017732]]]}
originStringAttribute
processingprocessing:facility
ESA



from manifest or EUMETSAT
cloudCoverDoubleAttribute
eoeo:cloud_cover

15.014.583966
orbitNumberIntegerAttribute
satsat:absolute_orbit

4549337179
sourceProductStringAttributeX

 not needed as it is part of the tracebility and is redundant
S2B_OPER_MSI_L2A_TL_2BPS_20240419T013152_A037179_T56NNG_N05.10 S2B_OPER_MSI_L2A_DS_2BPS_20240419T013152_S20240419T001424_N05.10
processingLevelStringAttribute
processingprocessing:level
L2A


L2S2MSI2A
platformShortNameStringAttribute
core STAC attributeconstellation

sentinel-2SENTINEL-2
instrumentShortNameStringAttribute
core STAC attributeinstruments
MSI


msiMSI
relativeOrbitNumberIntegerAttribute
satsat:relative_orbit

22116
sourceProductOriginDateStringAttributeX
X
to be moved to eopf
2024-04-19T02:13:20Z 2024-04-19T01:32:14Z
platformSerialIdentifierStringAttribute
core STAC attributeplatform

sentinel-2a
B
A
beginningDateTimeDateTimeOffsetAttribute
core STAC attribute

start_datetime

datetime



2024-03-08T14:33:52.000000Z2024-04-19T00:14:29.024Z
endingDateTimeDateTimeOffsetAttribute
core STAC attributeend_datetime

2024-03-08T14:33:52.000000Z2024-04-19T00:14:29.024Z
granuleIdentifierStringAttributeXNones2:granule_id (removed)

S2A_OPER_MSI_L2A_TL_2APS_20240308T143352_A045493_T33UVR_N05.10S2A_OPER_MSI_L2A_TL_2APS_20240308T143352_A045493_T33UVR_N05.10

Sentinel-2 STAC extension attributes to be discussed (not all present in Odata):

...

Field nameData TypeRelevant to general public?
Potential future extension or field
Comments
Multi-Mission
s1:processing_datetime
s2:generation_time		date-timeYesprocessing:datetime (PR)
created in assets		OData: processingDate
S2 Example: 2024-04-19T01:31:52+00:00 (in STAC Z instead of +00:00)
s1:datatake_id
s2:datatake_id		stringYeskeep as isto 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)
or
and
mgrs:utm_zone (not querable)
mgrs:grid_square (not querable)
mgrs:latitude_bandband (not querable)

  • mgrs extention requires 3 fields (56, NN, G)
  • grid:code is one field (MGRS-56NNG)
  • Odata: tileId (56NNG)
s2:product_uristringYes?
  • id
  • STAC Link
  • EOPF extension
  • keep as is?
NO To be removedNONEMight be needed in the S2 extension by some other users of the extensions.
s2:datastrip_idstringYes?keep as isEOPFOData field: datastripId
Example: S2A_OPER_MSI_L2A_DS_2APS_20240308T143352_S20240308T101546_N05.10
s2:datatake_typestringNo?EOPFOData: operationalMode
Example: INS-NOBS
s2:processing_baselinestringYesprocessing:version (PR)OData: processorVersion, example: 5.1
STAC example: 05.10
s2:reflectance_conversion_factornumber?keep as is or EOPFExample: 1.01707999697991
Sentinel-3 
s3:gsdvariousNo?gsd as a single value?
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 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?

...