Configuration guide

This application comes with a set of config files. See example configurations here. When downloading the release files you will find *.schema.yaml-files where all possible values are listed.

Tip

Install the VSCode YAML extension from Red Hat to get help writing valid config files.

airports.yaml

This contains the core configuration for each airport.

As a minimum, you must define:

• the airport location: this is used for fetching wind information
• runway threshold locations: these are used as the last point in the descent trajectory calculations

Sequencing horizons

Custom time horizons can be configured per airport using the ISO_8601 duration format. Time from

sequencingHorizon: PT30M 
lockedHorizon: PT10M

Independent Runway Systems

In the airports.yaml, you can also define independent runway systems.

independentRunwaySystems:
  - ["07L"]
  - ["07C", "07R"]
  - ["25R"]
  - ["25C", "25L"]

Aircraft approaching runways in different runway systems will be treated as independent for the sequencing logic. For example, aircraft approaching 07L and 07R are independent while 07C and 07R are treated as dependent.

For runways that are part of the same system (dependent), arrivals will be scheduled using a staggered/segregated pattern based on the configured minimum separation.

By default all runways of an airport are considered to be a single system where all runways are dependent.

Metering points

Metering points can be used to group and display aircraft by arrival entry fix rather than by runway. This is useful for modeling upstream arrival streams, showing where traffic enters the system, and building timelines around flow-in points instead of touchdown time.

airports:
  ENGM:
    meteringPoints: ["LUNIP", "ADOPI", "ESEBA", "BELGU", "INREX", "RIPAM", "VALPU", "INSUV", "TITLA", "BAVAD"]

The master client calculates STA and ETA for each configured metering point and publishes them to slave clients. Slave clients can then configure timeline views based on those published times.

Note

TTL and TTG advisories are still based on the landing sequence and landing time, not the metering point time.

The metering points can be referenced in the timeline configurations in settings.yaml:

timelines:
  ENGM:
    - timelineTitle: "VALPU / INSUV"
      arrivalLabelLayoutId: osloArr
      left:
        meteringPoints: ["VALPU"]
      right:
        meteringPoints: ["INSUV"]

settings.yaml

This defines general application settings and timeline configurations for each airport.

stars/<airport-icao>.yaml

These files should define typical altitudes and airspeed along each STAR for an airport. This will make descent trajectories and estimated landing times more accurate. Make sure the STAR names and fixes match exactly with the ones defined in the EuroScope .ese sector file. If the STAR names contains special characters you should also make sure that the yaml file is saved with ANSI/Windows-1252 character encoding.