A job is a unique instance of a pre-configured workflow that delivers the outputs defined by the JSON parameters shown in the job configuration window.
A workflow can have one or more jobs. For instance, a user builds a workflow based on the processing block Aircraft Detection, in order to detect planes from high-resolution satellite images. This workflow can be configured and run as a job multiple times. The examples below show the same workflow that has been run as 2 separate jobs: one job for Kuwait and one job for Great Britain.
This guide assumes that you already created a workflow. For more information: Create a Workflow.
Once the workflow is created, click Save & Configure Job. You will be redirected to the job configuration window. On the left side, the job type, geometric filter, JSON parameters and job estimation are shown. On the right side, the basemap is shown.
Select one of the following job types: Test Query or Live Job. The difference between the 2 job types is shown in the table below.
|Test Query||Searches for available data and provides information about the available|
images (metadata and quicklooks). A test query (or dry run)
does not download or process data and it does not consume credits.
It is always recommended to run a test query before running a live job.
|Live Job||Runs the job with the adjusted JSON parameters and consumes credits. |
A live job (or real job) generates real outputs (data and/or algorithm
results) delivered in TGZ archive format.
A geometric filter represents the spatial relation between the data to be retrieved and the Area of Interest. There are three geometric filter options available: bounding box, contains, and intersects. The difference between the 3 geometric filters is shown in the table below.
|Bounding Box||Creates a rectangular AOI with an array of 4 coordinates. The images |
returned intersect this bounding box and it is not guaranteed that they
will fully cover this AOI.
|Contains||Creates a polygon AOI. The images returned are 100% overlapped on this AOI.|
|Intersects||Creates a polygon AOI. The images returned are intersecting this AOI and |
it is not guaranteed that they will fully cover this AOI.
The JSON parameters define how the data retrieval and analysis will be performed during a job run. Before adjusting the JSON parameters, it is recommended to check the requirements of each data block and processing block.
|Examples of JSON parameters||Values|
To validate the JSON parameters and make sure the brackets are correct, we recommend using the external tool JSONLint.
Example JSON parameters:
On the basemap, you can draw or upload an AOI. To draw an AOI, click anywhere on the basemap, then start creating a polygon by selecting the geometric filter. The table below shows the accepted file formats for uploading the AOI.
|Accepted vector file formats for uploading an AOI|
Multi-polygons or polygons with self-intersecting vertices will generate a job failure.
The coordinates of the AOI can also be copied and pasted from other sources as a GeoJSON geometry. We recommend using the online GIS tool GeoJSON.io.
The AOI size is displayed on the bottom of the basemap, after closing the polygon with the last vertex. You can change the AOI by deleting the current one.
Before running the job, users can view the job estimation, which includes the total processing time and price. Please note that the AOI size and the adjusted JSON parameters directly influence the processing time and credit costs.
To reduce the credit costs, you can reduce the AOI size.
If the job estimation is displayed, then the JSON parameters are correctly configured.
After you configured the JSON parameters and viewed the job estimation, you can run the job. To proceed, go to Run Job.