The following presentation contains a short gap analysis regarding STAC and the AIP of the LTA service:
This table focuses on product properties that should be exposed by AIP instances and that are not currently backed by STAC Core or extensions.
Property Name | Possible values / Example | Common | Comment | Proposed solution |
---|---|---|---|---|
Online |
| Order extension field order:status:
| ||
to be stated in the ICD : Offline : no assets ? Online : the item embeds assets |
Call from LTA Client | "OGC API - Processes" operation | Details | Response of query |
---|---|---|---|
Product Order Request | /processes/{PROCESSID}/execution | Query type : POST PROCESSID = order-request Input parameters :
| By default returned by service:
Other parameters (can be retrieved through endpoint /jobs/{JOBID} |
Order Status Query (status = completed) | /jobs/{JOBID}?status=successful | JOBID = order ID returned previously | List of completed Jobs with their ID and following parameters :
use job result to get some parameters ??? |
Product Staging Notification | Callback mechanism for completed jobs : requires to add a subscriber property in the order request (notification endpoint) | To assess : authorisation for callback | |
TODO :add a table on Process definition with input and output parameters (as a requirement)
Odata status | OGC API - Processes status |
---|---|
queued | accepted |
in_progress | running |
completed | successful |
failed | failed |
cancelled | dismissed |
The bulk is defined by a list of products or query filter parameters and a batch size
1st level assumption: not "as is" in the OGC standard.
Ideas :