Collects
What is a Collect?
A Collect is an object that describes the radar parameters and geometry of a single imaging operation. Once a Task has reached a SCHEDULED state, one or more Collects are generated. Collects provide a more detailed view of how the Task is being fulfilled, including a visualization of the imaging footprint, and the exact parameters to be used during collection.
Relationship to Tasks
- A Task defines what to image, when, and how.
- When scheduled, the Task generates one or more Collects to carry out the request.
- Collects are the unit of execution: they represent the actual satellite imaging operations.
- Collects produce deliverables: once a Collect is processed and delivered, its assets (e.g., GeoTIFF, SICD, SIDD, CPHD) are available via the STAC API.
Collect Statuses
Similar to Tasks, Canopy provides real-time visibility into the lifecycle of each Collect throughout the fulfillment of a task.
Terminal Statuses Statuses marked with a † are considered terminal and Collects will not transition away from these statuses without human involvement.
| Status | Description |
|---|---|
| SCHEDULED | The Collect is on the mission schedule. |
| COMMANDED | The Collect has been commanded to the satellite. |
| COLLECTED | Satellite has successfully captured the Collect. The data will begin downlinking shortly. |
| CANCELED † | The collect was removed from the schedule. |
| TRANSMITTED | The satellite has been commanded to downlink the raw collect data. |
| FAILED † | The satellite did not perform the commanded collect operation. |
| PARSED | Umbra automation has received and parsed the first transmission containing the raw collect data. |
| INCOMPLETE | Some of the raw collect data is downlinked, but not enough for processing. The Collect will transition back to TRANSMITTED when Umbra's automation attempts to downlink the remaining data on future passes. |
| ASSEMBLED | The raw collect data has been parsed and is ready to be staged for processing. If not enough data was parsed for processing, the collect will transition to INCOMPLETE. |
| STAGED | We have downlinked 99% of the raw collect data and staged it for processing. |
| PROCESSING | The collect is processing. |
| STALLED | The collect processing has stalled due to resource constraints. |
| PROCESSING_DELAY | There was an unexpected delay in processing. |
| PROCESSED | The collect has been processed into deliverables. |
| CORRUPT † | The data failed Umbra's automated QA and will not be DELIVERED. |
| DELIVERING | The collect is in the process of being delivered. |
| DELIVERED | The collect deliverables have been delivered to the customer. |
| DELIVERY_DELAYED | The delivery of the collect is delayed due to a transient issue and delivery is still in progress. |
| DELIVERY_STALLED | The collect was unable to be delivered. Umbra will attempt to correct the issue and redeliver. |
| DELIVERY_ERROR | The collect was unable to be delivered due to a delivery misconfiguration that must be corrected by the customer (oftentimes related to S3 bucket policy). Contact Umbra Support for further assistance. |
| UNKNOWN_COLLECT_STATUS † | The collect is in an unknown state. Contact Umbra Support for further assistance. |
Updated 21 days ago
What’s Next