Order Statuses - Archive
Archive orders can have different statuses. Below is a description of what each status represents.
Example:
Pending Approval
User has submitted an archive order, and it is waiting on the provider to either Accept or Decline
Approved
The order has been approved by the provider and will be processed. It will automatically transition to the processing status.
Processing
The order is applying the necessary image processing operations (clipping to AOI, generating metadata and preview images, etc.)
Fulfilled
The order has finished processing, and the results are ready to be downloaded by the user.
Declined
The provider was declined the order. It will not be processed.
Processing Cancelled
The order started processing, but was cancelled before it could complete. No results are available to download.
Processing Failed
The order started processing, but encountered an error before it could complete. No results are available to download.
Order Statuses - Tasking
Tasking orders can have different statuses. Below is a description of what each status represents.
Example:
Pending Approval
User has submitted a tasking order, and it is waiting on the provider to either Accept or Decline
Approved
The tasking order has been approved by the provider. The provider will need to mark the tasking as scheduled, in order to transition to the collection_scheduled status (i.e. when a collection has been scheduled in the provider’s mission planning software)
Collection Scheduled
The tasking order has been scheduled for a tasking (i.e. a collection has been scheduled in the provider’s mission planning software)
Collection in Progress
The tasking order’s satellite collection is currently in progress. This status is automatically triggered for orders who have the status collection_scheduled and whose start_date has passed
Collected
The order's status while the tasking order’s first result has the status “fulfilling". Used to represent the data having been collected, and downlinked from the satellite.
Processing
The tasking order has at least one collection, but has not yet returned a successful result (e.g. the collection satisfies <85% of the tasking AOI)
Fulfilled
The tasking order has finished processing and met the order requirements. The result(s) are ready for download
Collection Failed
The collection has been scheduled, however the end_date has passed and the order has not fulfilled
Processing Failed
An error occurred during processing, and the processing of the results could not be completed. No results are available for download
Collection Cancelled
The tasking order was approved, but prior to collection it was cancelled
Declined
The tasking order was not approved, and was instead declined by the provider
Expired
The tasking order’s was not accepted by the provider, before the expiration timestamp value (72h after placing order, by default)
Result Status
Each tasking order can have multiple collections, and each collection has its own status. Each collection becomes a result for the order. Below is a description of what each result's status represents.
Example:
Fulfilled
This collection has finished processing and has met the necessary criteria. It can be delivered when the order completes
Fulfilling
This collection is still processing, it is not yet know if it has met the necessary criteria
Failed
The collection finished processing, and has not met the criteria. It will not be delivered when the order completes
Result Status Reasons
Each result can have different statuses (above). In addition to the status, a reason gives further detail for how the status was determined. Below is a description of what each reason represents
Example:
The result has been selected for fulfillment
This single collection has met the criteria of the order
Selected for multi product fulfillment
This single collection has met some of the coverage of the order, so has been selected, but the order is waiting for other collections, to meet the required coverage (85% of the AOI, by default)
Product was replaced due to a lower coverage
A different collection better met the requirements for the order, and will replace this collection
Product does not match the expected request interval
The collection did not meet the required date range
Product does not have minimum expected area size
The collection has not met the minimum intersecting area required to be considered a result (0.1 km2 by default)
Product does not intersect with requested aoi
There is no intersecting area (no overlap) between the tasking request AOI, and this collection
Product does not have a valid intersection coverage percentage
This single collection has not met the required coverage, so has been selected as a result. (85% of the AOI by default, for taskings with single-product selected)
Product does not have a valid cloud coverage
The amount of cloud cover in the collection was too high, to be used for the order
Product has invalid pixels
Some of the data in the collect could not be processed, resulting in an error. This collect cannot be used
Comments
0 comments
Article is closed for comments.