STAC compliance
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:
|
Retrieval functions
Retrieve Product
Queries
Call from LTA Client | "OGC API - Processes" operation | Details on query | 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 :
|
Product Staging Notification | Callback mechanism for completed jobs : requires to add a subscriber property in the order request | ||
JobStatus value correspondance
Odata status | OGC API - Processes status |
---|---|
queued | accepted |
in_progress | running |
completed | successful |
failed | failed |
cancelled | dismissed |