This page details the new attributes that shall be defined in EOPF extension.
| Attribute name | Odata type | Example value | Description | In ? (collection, item, asset) | Stac type | Equivalent OData attribute | originator eg. catalogue/processor/orchestrator? |
|---|---|---|---|---|---|---|---|
| origin_datetime | DateTimeOffsetAttribute | 2024-03-08T14:33:52.000000Z | Date time of the input data considered to create the item. For example, for PRIP, it is the time of the availability of all CADU data on the CADIP/XBIP. | Item | Datetime | OriginDate | |
| datatake_id | StringAttribute | S1/S2/S3/S5P Datatake Id | Item | String | DatatakeID | ||
| datastrip_id | StringAttribute | S2A_OPER_MSI_L2A_DS_2APS_20240308T143352_S20240308T101546_N05.10 | S2 Datastrip ID | Item | String | DatastripId | |
| instrument_configuration_id | IntegerAttribute | 5 | Item | Integer | InstrumentConfigurationID | ||
| instrument_mode | StringAttribute | INS-NOBS (nominal observation), INS-EOBS (extended observation), INS-DASC (dark signal calibration), INS-ABSR (absolute radiometry calibration), INS-VIC (vicarious calibration), INS-RAW (raw measurement), INS-TST (test mode) | to be added to EO, it is already is sar and altimetry | Item | String |
1 Comment
Anonymous
Catherine from DPR:
datatake_type should be replaced by instrument /sensing /operation mode to be generic for all sentinels.
Are datatake_id and datastrip_id really needed in STAC ? as they are specific for S1 and S2, they should be in other_metadata (non STAC mission-specific metadata).
Add Comment