ICD for LTA last version can be downloaded from this link: CAP-TN-037-BE_ICD_for_LTA-1.0-RC3.docx

and the PDF version : CAP-TN-037-BE_ICD_for_LTA-1.0-RC3.pdf

Differences with current ICD, limitations & improvements

FunctionalityOperation(s)Current ICDFuture ICDJustification / Open questionSolutions / Alternatives
Returns real priority calculated for requested order productOrder
batchOrder

"priority" field is returned
in order response.
Mandatory for productOrder

"priority" field is not returned 
in response		OGC API standard don't allow to specify additional fields in jobStatus responsenone
Returns estimatedDate information for requested order productOrder
batchOrder		"estimatedDate" field is returned 
in order response. 
Mandatory for productOrder		"estimatedDate" field is not returned 
in response		OGC API standard don't allow to specify additional fields in jobStatus response

Use the specific STAC property order:date. It requires the STAC item corresponding to product to order is updated when the order is created

Decision has been made to get rid of this field

Automatic creation of Batch OrdersbulkCreateBatch orders processes are created in advance in the bulkCreate step
but not triggered. The client has to
trigger each of them for execution.

Batch Orders processes are not automatically created.

The client has to execute a new process called "batchOrder"
for each internally prepared/stored Batch order 

No concept of "process triggering" in OGC API; only process execution.

It doesn't change anything in terms of number of queries to send by the client. 


Setting of FilterParam query parameterbulkCreate"FilterParam" property is a string with the complete criteria"FilterParam" property is conform to CQL2 JSON 

Filtering can b e tested directly with a STAC query.


BatchOrder query sub-stepbulkCreateThe bulkCreate step don't return the list of Batch Orders but the client needs to send another query to get them.Job result of bulkCreate process contains
the list of batchOrders as an output parameter		simplification of workflow
Subscription creationsubscriptionCreate
New input parameter for operation: collectionForce a subscription to be related to a 
product type (STAC collection) 

Notification about asynchronous process completion: credentials information

productOrder
batchOrder
bulkCreate		Provide notificationUsername and
notificationPassword parameters

subscriber property in execute payload just includes callback endpoint without any credentials information  

Open question: is reference implementation of OGC API - Processes able to build 
notification request with additional input 
parameters ? 

Add following input process parameters: 

  • notificationUsername: The username associated with the
    Endpoint URI provided in the subscriber.successUri property of the
    execution payload
  • notificationPassword: The password associated with the
    Endpoint URI provided in the     subscriber.successUri property of the execution payload 
Notification on Subscriptions
The LTA service posts a HTTP query to a predefined callback URL The notification is sent asynchronously through a 
message broker (AMQP or MQTT). Conform to OGC API Publish-Subscribe Workflow   

More robust, especially if client's URL is irresponsive. 

However, this requires a overwork on client side to subscribe to channels and consume messages.



Note on sequence diagrams: generated with https://plantuml.online/uml 

  • No labels