Versions Compared

Old Version 16

changes.mady.by.user Olivier Gaquiere

Saved on

compared with

New Version Current

changes.mady.by.user Olivier Gaquiere

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

ICD for AIP LTA draft version can be downloaded from this link: CAP-TN-037-BE_ICD_for_LTA-1.0-RC1.docx

PDF version : CAP-TN-037-BE_ICD_for_LTA-1.0-RC1.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 
is not returned 
in response		OGC API standard don't allow to specify additional fields

in jobStatus response

Use the "finished" property of Job status.
When job completed, "finished" is
updated with date of completion.

Use the specific STAC property order:date. It requires

the 

the STAC item corresponding to product to order is

updated 

updated when the order is created

Automatic creation of Batch OrdersbulkCreateBatch orders processes are
created 
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

of queries to send by the client. 


Setting of FilterParam query parameterbulkCreate"FilterParam" property is a string
with 
with the complete criteria"FilterParam" property becomes a array
of objects. Each object is a criterion for
product filtering

Less complexity on client side to define STAC query.

The query is built by the service and is

compliant
with

compliant with STAC Filter extension

keeping the whole query as a string
BatchOrder query sub-stepbulkCreateThe bulkCreate step don't return the
list 
list of Batch Orders but the client needs
to 
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 
a predefined callback URL The notification is sent asynchronously through a AMPQ
message
broler  
broker  

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

However, this requires a overwork on client side.

Comments

...

Results from discussion with Werum

Question: can BulkCreate be synchronous
Answer: NO because potential time to execute "Bulk Create request" can be long (several mn)
Decision: stick to asynchonous process 

Question: Are each batch order created when Bulk create ?
Answer: yes and persisted in a DB

...



Answer: NO because it can be very resource resource/time consuming in the case of reprocessing (a lot of Batch orders !!) Note on sequence diagrams: generated with with https://plantuml.online/uml