AxelGlobe Tasking API (2.1.0)

The AxelGlobe Tasking API allows for automation of our satellite tasking process. You can request a specific area of interest be captured at a specific date and time.

Beta

List of terms used in the API

The structure of the AxelGlobe Tasking API follows the OGC API "Features" standard. Each collection of features are represented as GeoJSON.

The typical tasking workflow has the following steps:

1. Authenticate
2. Create a Task Plan
3. Review list of Task Candidates
4. Request Task be scheduled
5. Check Task status and download data

Step 1: Authenticate

Before connecting to the API you must generate a Token with credentials from our platform. Please contact us for more information about API access.

Use the Create an authorization Token request to generate a token. Securely store this token locally for up to 24 hours. Use this token for all subsequent requests in a session. After the token expires you can request a new one.

Step 1: Create a Task Plan

To get started tasking you have to plan a capture. This will allow our system to generate capture candidates that have been calculated and validated so they can be scheduled.

To create a Task Plan make a POST request to the Create Task Plan endpoint.

Note the validation rules for a Task Plan in the request body schema below.

Step 3: Review list of Task Candidates

Once the Task Plan is created our system will take up to 20 minutes to generate validated Task Candidates.

After waiting 20 minutes then list all the candidates using the List Candidates endpoint. This endpoint is paginated, and a the full list can be fetched by following the links with of type rel=next.

Note: if the list of candidates is empty after 20 or more minutes then we are not able to capture the planned AOI or TOI.

At this point any of the Candidates are able to be tasked. Review the list and decide on the optimal Task Candidate that fits your needs.

Step 4: Request Task be scheduled

To schedule a Task Candidate create a Task Request using the Create Task request endpoint.

Provide the ID of the Candidate and the priority of the Task.

Note: this must be done within the lifetime of a Candidate (within approximately 24 hours after the candidate was created). If the Candidate is expired then fetch the list Candidate again to get fresh ones.

Step 5: Check Task status and download data

After the Task Request is accepted you can check the status of the Request. Use the Task Request Details endpoint to check the status of the Request.

We recommend polling the API approximately once per hour to check for status updates. Once the status becomes DATA_AVAILABLE there will be a link to our STAC API with all the data from the capture. Generally data will be available 24-48 hours after the capture.

• Capabilities
• Satellites
• Task Plans
• Task Candidates
• Task Requests

To use the API you need to create a Token with our authentication server.

This token should be reused between requests until it expires.

OGC Spatial Data on the Web Best Practices

Information about our AxelGlobe GRUS satellite constellation. Basic information and future orbit data is provided as reference data to better understand how you can Task our satellites.

Register an AOI to plan a capture

Create a Task Plan to get information about potential captures.

Task Plan Status

After creating a Plan it can take 10 ~ 20 minutes for candidates to be generated.

When a Plan has status ACTIVE then you can check for possible candidates using the rel=candidates link in the Plan response.

A Task Candidate is one calculated potential scene related to a Task Plan

Request a capture be scheduled. A Task Request has information about the scheduled capture and processed data. Task Requests are limited and your account may be charged.

Task Request Status:

After Tasks reach 'DATA_AVAILABLE' status assets can be fetched from the STAC API.