flight-blender

A standards compliant Network Remote ID and Flight Authorisation server for UTM / U-Space. Also has integrations for consuming geofences and live flight data aggregation and fusing.

View the Project on GitHub openskies-sh/flight-blender

Introduction and objective

In this article you will understand how to deploy the OpenUTM system and the associated data flow. There are really three pieces of software that required:

Overview

openutm-flow

Quickstart

In this document, we will setup

Flight Blender follows the ASTM standads for access

Detailed Instructions

Setting up authorization server

The OpenUTM system is a standards compliant system and requires a OAUTH server for managing Identity and Authorization, the ASTM standard requires that JWT tokens be used to access UTM services, JWT tokens can be issued by any server, we recommend using Flight Passport since it gives full authorization capabilites.

Creating a .env file

When you deploy Blender you will need a environment file. The environment file can be requested via our contact form.

The section below deatils the environment file variables and a short comment on where they are used.

1

Used to upload data into Flight Blender, see importers directory in Flight Blender for more information. A JWT Bearer Token is needed to write any data into Flight Blender, this set of environment variables enable you to write data into Flight Blender.

| Variable Key | Description | |————–|:—–:|

BLENDER_WRITE_CLIENT_ID The client credentials ID set in Flight Passport
BLENDER_WRITE_CLIENT_SECRET -
BLENDER_AUDIENCE -
BLENDER_WRITE_SCOPE -
BLENDER_AUDIENCE -

2

Used in Flight Spotlight, these settings are used in the Spotlight to enable login into the system. Client ID and Client Secret are standard

Variable Key Description
PASSPORT_WEB_CLIENT_ID -
PASSPORT_WEB_CLIENT_SECRET -
OIDC_DOMAIN -
CALLBACK_URL -

3

Used in Flight Spotlight, these variables are used in Spotlight for basemaps as XYZ tiles.

Variable Key Description
BING_KEY Get a key from Bing Portal
MAPBOX_KEY -
MAPBOX_ID -

4

Used in Flight Spotlight, these variables specify the backend servers for Spotlight to do data processing | Variable Key | Description | |————–|:—–:| | REDIS_URL | - | | TILE38_SERVER| - | | TILE38_PORT | - | | DEFAULT_APPROVED | - |

5

Used in Flight Blender, these varialbles are used in Flight Blender to ensure DSS connectivity and inter-operability ith other

Variable Key Description
DSS_SELF_AUDIENCE -
AUTH_DSS_CLIENT_ID -
AUTH_DSS_CLIENT_SECRET -
DSS_BASE_URL -
DSS_AUTH_TOKEN_ENDPOINT -
DSS_AUTH_JWKS_ENDPOINT -
BLENDER_FQDN -

6

Used in Flight Blender, these are the key backend services that are used in Blender

Variable Key Description
REDIS_HOST Location of the Redis instance e.g. redis if using Docker Compose
REDIS_PORT 6379, if you using default / Docker compose, see also redis.conf file for changing this.
REDIS_BROKER_URL This is used in Django to manage the Celery / task management processes if you are usnig
HEARTBEAT_RATE_SECS This is the refresh rate of the system, normally set to 1 or 2 seconds
OPENSKY_NETWORK_USERNAME Get a Username from https://opensky-network.org/
OPENSKY_NETWORK_PASSWORD -

Running Flight Blender

You can run Blender by running docker compose up and then go to http://localhost:8000