Currently an association of a product with a certain datatake (a concept used in some, but not all EO missions) is only possible via mission-specific product parameters. Also, a reference between datatakes and downlinks (possibly spanning multiple ground stations with overlapping data reception) may be of use for several missions, but cannot be represented with the current data model.
The request therefore is to add entities for Datatakes and Downlinks with the following properties:
Downlinks can be spread over several ground stations (passes with or without overlapping)
Datatakes can be split into data segments, each associated with a specific downlink/pass
Multiple datatakes can be grouped into one "acquisition" in the case of satellite formations with synchronized datatakes
Downlinks/passes/data segments can be marked as "planned" and as "received", whereby deviations of the actual received elements from the planned elements are possible
Downlinks/passes/data segments/datatakes can be timestamped with planned and actual (received) times (microsecond precision, as with all times in prosEO)
Products can be associated with datatakes and/or acquisitions
Currently an association of a product with a certain datatake (a concept used in some, but not all EO missions) is only possible via mission-specific product parameters. Also, a reference between datatakes and downlinks (possibly spanning multiple ground stations with overlapping data reception) may be of use for several missions, but cannot be represented with the current data model.
The request therefore is to add entities for Datatakes and Downlinks with the following properties: