Skip to main content
Sign in

Tasking and SAR Data Access Release Notes - 6 December 2023

  • Updated

New

New Tasking Tier names

Tasking Tiers in both the Capella Console and APIs have been renamed to provide more clarity around how the Scheduler recognizes the importance of a tasking request for collection. 

Previous Name New Name Description

Routine

Routine

(no change)
Get coverage on a regular basis.
Offers premium importance for data collection when regularity and consistent imaging geometry are crucial.
Customers set their own acquisition windows. Minimum repeat cycle is 24 hours.
1-Day Urgent

Designed for time-sensitive situations where rapid collection speed is mission critical.

Urgent tasks are considered for scheduling first.

Minimum acquisition window is 24 hours.
3-Day Priority

Optimal minimum acquisition window for situations when precise imaging geometries matter.

Priority tasks are considered for scheduling after Urgent tasks.

Minimum acquisition window is 72 hours.
7-Day Standard

Provides assured data collection upon acceptance.

Standard tasks are considered for scheduling after the Urgent and Priority tasks.

Minimum acquisition window is 7 days.
Background Flexible

Ideal for leveraging variations in capacity without the risk of interfering with tasks of higher importance. 

Flexible tasks can be added, shuffled, and removed from the schedule to accommodate tasks with higher importance.

Minimum acquisition window or repeat cycle is 24 hours.
Existing tasking requests submitted prior to December 6, 2023 with the previous Tasking Tier names will continue to be considered for scheduling as the scheduling horizon window slides. There is no need to cancel existing requests and resubmit with the new names.
More information on how to use the tasking tiers can be found in the What are Capella's Tasking Tiers? support article. 

Tasking Tiers in Console

The new Tasking Tier names are available in Console today. The previous names will continue to appear in the Task Table until January 31, 2024. Console will automatically handle the mapping between the old and new tier names when retasking an existing task. 
singletask.png
repeatask.png


Tasking Tiers in the API

We ask that API users begin using the new names in the collectionTier parameter, as described in the documentation. The API will continue to accept both the previous and the new Tasking Tier names until January 31, 2024 to give users time to update workflows. 

Related articles