How is Coverage Evaluated

Tasking Orders

For tasking orders, satellite captures are compared against the tasking request, to see if they satisfy the tasking request requirements.  If they do, they are added to the tasking request as a result.  How much of the area is satisfied, is often referred to as the coverage.

This evaluation is done by:

(1) Satellite captures are first evaluated to see if they meet the date range and satellite source of the tasking request. 

(2) If the date range and satellite sources match, the geometry of the satellite capture, is compared against the geometry of the tasking request.  The intersecting geometry of the two, is referred to as the coverage, and expressed as intersection_percent_coverage, relative to the size of the tasking request area.

This intersection_percent_coverage (actual value), is then compared against the aoi_intersection_percent  (the minimum required area of the tasking request) to see if the tasking order is fulfilled. 

If the aoi_intersection_percent requirement has been met, then the tasking request is considered fulfilled, and it proceeds to consolidate all the results, to perform post processing and finalization of the order.

If the aoi_intersection_percent requirement has not yet been met, then it continues to check for additional captures (results), until either the aoi_intersection_percent requirement has been met and the order is fulfilled, or the end_date of the tasking request passes.

When creating a tasking request, the aoi_intersection_percent requirement is defined as 85% for tasking requests created through the front end.  When creating taskings through the API, this value has a default value of 85%, but can be defined as any value between 0.1 and 100 percent.  This is sometimes referred to as "standard coverage".

Screenshot of an API Reponse, or a Tasking Request.  An aoi_intersection_percent value of 85% is shown, with a intersection_percent_coverage calculated as 83.41% for one of the request's satellite captures:

 

Archive Orders

For archive orders, coverage is evaluated differently than taskings, as archive orders have the results presented prior to order creation, whereas when tasking orders are created, the results do not exist yet.

Archive orders thus have their aoi_intersection_percent set to 0% on the front end, where any intersection will be returned as a result. When archive orders are created through the API, the aoi_intersection_percent value has a default value of 0% set by default, but can be defined as any value between 1e-8 and 100 percent.

Screenshot showing archive request, with aoi_intersection_percent defined as 85 percent: