Tasking API - Washington DC - 2022

Paulo Cruz / Luis Veci

Staff Platform Engineer

The SkyWatch Mission

“To democratize remote-sensing data through a simple user experience”

​

2

CONFIDENTIAL | SKYWATCH

To make it simple

we have to walk through some challenges

3

CONFIDENTIAL | SKYWATCH

Integration challenges:

4

• Different authentication methods
• Different payload definitions
• Different responses
• Different behaviours when it comes to failures
• Distinct metadata format (json/xml/txt)
• Different service interfaces (Rest, Rpc, Soa)
• Multiple steps to get a satellite imagery from point A to point B
• Multiple delivery methods (s3, gcp, http, ftp)
• Security (credentials, communication, product storage)

​

CONFIDENTIAL | SKYWATCH

Some examples

5

CONFIDENTIAL | SKYWATCH

What do we learn from all

this?

6

CONFIDENTIAL | SKYWATCH

Standard product delivery

Simplified interface with optional filters

7

CONFIDENTIAL | SKYWATCH

8

Lessons learned

Abstract the most used properties to deliver a standard product

Offer advanced filtering as optionals

Modularize internal components for reuse

Make it flexible to easily solve business problems and adapt to change

CONFIDENTIAL | SKYWATCH

Questions?

9

@skywatchapps

paulo@skywatch.com

www.skywatch.com

CONFIDENTIAL | SKYWATCH

Tasking api suggestions

10

• Collectable properties (similar to stac queryable)
• Tasking properties that can be used for tasking requests
• Property selection
• increase standardization on top of stac
• sensor
• bands/polarization
• angles
• Scheduling options
• once, daily, weekly, biweekly, monthly
• Status convention
• processing, rejected, tasked, denied, cancelled, delivered
• Reasons for rejection
• cloudy, capacity (limited), not in path
• Callback
• web hooks
• sns
• Common term to differentiate archive (collections/item) from tasking
• Collect / item
• Task / item
• Collections (Task / Item)

​

CONFIDENTIAL | SKYWATCH