Use TopSky on TC/APP Displays

[luke11brown]

What is the current situation?

TopSky only used on area profiles

What is the proposed change?

Approach & TC profiles/displays to use TopSky at the minimum to display part time airspace and danger area activations, other features can be omitted. Tag functionalities such as auto text (on heading assign for example) will therefore be retained.

• [x] Symbols to be disabled (this seems to be the problem, possiblity of using native ES radar track symbols for all)
• [ ] Colours to be changed (see below solution for login callsign based settings)
• [ ] TopSky lines in ASRs require setting up
• [ ] non-TopSky area profiles can have TopSky enabled but retain the tag family

Reference materials (e.g. screenshots)

Additional context

[luke11brown]

Instead of another TopSky instance:

Use TopSkySettingsLocal for the following: [EGPH_] (weird colour NOVA)

[EGCC], [EGPD] etc. (normal NOVA)

[_APP] (NODE)

[LTC], [MAN], [STC_] NODE

Note: ordering of this file is important. It needs to be more general at the start, becoming more login specific. Therefore, it should follow (I think) global, Suffix, Prefix based settings.

OCAS areas to have the following added (infills, but retain outline for all): ASRDATA:NERC

NERC ASRs to have the following line added: PLUGIN:TopSky plugin:ShowMapData:NERC

COLORDEF lines in TopSkyMaps.txt and TopSkyAreas.txt to be amended to one of the changeable defintions. e.g. Grey becomes: Color_Active_Map_Type_1 This can then be changed using the SettingsLocal file based on login callsign. Note: Color_Active_Map_Type_1 is currently used for all danger areas.

currently defined in TopSkyMaps.txt

COLORDEF:Grey:80:80:80
COLORDEF:Freetext:65:65:65
COLORDEF:Red:120:0:0
COLORDEF:Line:120:120:120
COLORDEF:Centreline:75:75:75
COLORDEF:OCAS:55:55:57
COLORDEF:CAS:28:28:28
COLORDEF:Fix:140:140:140

Becomes defined in TopSkySettingsLocal.txt

//Danger area (red)
Color_Active_Map_Type_1=120,120,120
//ARTCC High (Grey on NERC)
Color_Active_Map_Type_2=80,80,80
//Freetext
Color_Active_Map_Type_3=65,65,65
//STARs (RMA Lines)
Color_Active_Map_Type_4=120,0,0
//Centrelines
Color_Active_Map_Type_5=75,75,75
//OCAS infill
Color_Active_Map_Type_6=55,55,57
//Sector background infill
Color_Active_Map_Type_7=28,28,28
//Fixes
Color_Active_Map_Type_8=140,140,140

[luke11brown]

Run 4 versions of TopSky within the pack?

Automation to check parity of certain file such as TopSkyMaps.txt

name: TopSky data match

on: 
  push:
    paths:
      - '/UK/Data/Plugin/TopSky/TopSkyMaps.txt'
      - '/UK/Data/Plugin/TopSky_iTEC/TopSkyMaps.txt'
      - '/UK/Data/Plugin/TopSky_iTEC/TopSkyMaps.txt'

jobs:
  check_files:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v2

      - name: Check if files match
        run: |
          if ! cmp --silent TopSkyMaps.txt file2.txt || ! cmp --silent file1.txt file3.txt; then
            echo "TopSKyMaps.txt files do not match!"
            exit 1
          fi
        shell: bash

TopSky files that should be the same across instances

• ICAO_Aircraft.json
• ICAO_Aircraft.txt
• ICAO_Airlines.txt
• ICAO_Airports.txt
• TopSkyAirspace.txt
• TopSkyAreas.txt
• TopSkyCallsigns.txt
• TopSkyCallsignsLocal.txt
• TopSkyCPDLC.txt
• TopSkyCPDLChoppieCode.txt
• TopSkyMaps.txt
• TopSkyMSAW.txt
• TopSKyRadars.txt
• TopSkySSRCodes.txt