pinatacolada / topskylppc Goto Github PK

Stands 104-108 attribution rules

Detected stand 601

Someone parked on 605 is detected as 604

https://vatsim-scandinavia.org/forums/topic/3555-ground-radar-plugin-14-beta-2/

oops

AMC, AMCRS and NOTAM areas

File GRpluginStands.txt contains bad information: Line 241 : STAND:LPPT:607:N038.46.15.670:W009.08.15.920:LPPT:30 (Problem: Invalid stand radius)

B738 and A320 on 205 and 203 respectively, taxi was accurate

EGGX_FSS CID GXR

LED123, 124, LER86, TRA54 and 55 are missing the border from the definition.

Bragança and Mogadouro are flat out commented out.

To send a HOP without any transfer conditions, select the “HOP” option in the Callsign menu.
To send a HOP with a transfer condition (assigned heading, direct-to point or assigned speed):

1. open the AHDG or ASP menu and select the “HOP” option (found in the “More” folder)
2. select the desired value (to select a direct-to point, select the “Point” option in the AHDG menu and then left-click on the point on the radar screen

The transferring controller should keep an eye on both the track label and the Message In Window as there are three ways for the accepting controller to answer a HOP. In order of preference, they are:

• From the Callsign menu, select “ROF”. This sends a ROF message to the transferring controller.
  o See chapter ROF for indications
• Left-click on the AHDG, ASP or COPN item. This opens the Combined Transfer Menu. In it, select “Accept”. This sends an Accept message to the transferring controller.
  o The labels on both controllers’ screens return to normal sector state coloring
  o A message is put into the Message In Window for the transferring controller
  o A message is put into the Message Out Window for the accepting controller
• From the Callsign menu, select “Assume”. This assumes the aircraft (with the other two answers the aircraft remains assumed by the transferring controller)
  o The labels on both controllers’ screens return to normal sector state coloring

Note: if a HOP is sent to a controller not using the TopSky plugin, it will only be displayed on your label. To the accepting controller it will look like a normal transfer. Any proposed values will be shown also on the accepting controller’s label but they will not be colored as proposals.
Note: if a HOP is sent to a manually selected controller and is answered by either “Accept” or “ROF”, the next controller is reset to the automatically calculated one. The correct controller needs to be manually selected again before transferring the aircraft.

To send the RTI message:

1. open the AHDG, ASP or ARC menu and select the “RTI” option (found in the “More” folder)
2. select the desired value in the list (the “Point” option in the AHDG menu can’t be chosen)
   When the message is sent, the following indications are shown:
   Transferring controller: Accepting controller:

• Proposed value in white
• Message in Message In Window
• Proposed value in white
• Message in Message Out Window

To answer the message, left-click on the proposed value on line 0. This opens the Tactical Transfer menu where you can either accept or reject the proposal. When clicking on “Accept”, the menu closes and the following indications are displayed:
Transferring controller: Accepting controller:

• Accepted value in sector state color - Relevant label field value in green
  (until the accepted value is set)
• Message in Message Out Window
• Accepted value in sector state color - Relevant label field value in green
  (until the accepted value is set)
• Message in Message In Window

When the accepted value has been set (either by going back to the Tactical Transfer menu and selecting “Apply” or setting the value some other way), the label field returns to the sector state color.

On the other hand, if “Reject” is chosen, the menu closes the indications are as follows:
Transferring controller: Accepting controller: - Rejected value in yellow

• Message in Message Out Window - Rejected value in yellow
• Message in Message In Window

A rejected coordination value will be removed from the label after a specified time (60 seconds by default).
Note: if an RTI or TIP is sent to a controller not using the TopSky plugin or the message fails to go through, an error message will be put into the Personal Queue Window. The message counter in the Global Menu will be highlighted if the window is not open.

Stands 801-806 attribution rules

left or right clicks on list or tag do nothing

who keeps CPDLC open? Do both open? With what callsign? It's a mystery, nobody knows

Stands 114-117 attribution rules

topsky leader line is visible in ground radar for example

title

Even if with broadly accurate coordinates, it will be needed for fuaman to work

Stands 141-147 attribution rules

A321 parked, just outside of range

Position was accurate during taxi

One way of communicating a release to the next controller is to select the “Trf & release” option instead of “Transfer” in the Callsign menu when transferring the aircraft. This opens a menu to select the desired release condition. The available choices are “Climb”, “Descent”, “Turn” and “Full”. Selecting an option will start the transfer with the selected release condition.
The release will be displayed on line 0 of the track label (in white during the transfer), showing the first letter of the release condition.

After the accepting controller assumes the aircraft, the release indicator changes to sector state color. It remains in the transferring controller’s label until it becomes unconcerned, and in the accepting controller’s label for 3 minutes.
Note: if a release is sent to a controller not using the TopSky plugin, it will only be displayed on your label. To the accepting controller it will look like a normal transfer.

Stands 301-302 attribution rules

Example A320 callsign WUK from EGKK was auto assigned to 204

KLM B738 auto assigned 806 with 11x and 12x all available

map needs to be updated to the new airac spec

#134 left documentation outdated for departure list and tags

Neither agadir but agadir was intentional meh

A319 parked correctly, just outside the range

Scenery: X-Design LPPT Xplane 11. Accurate to the pixel while taxiing

A359 parked

For example callsign GAF on an A319, auto assigned to 105.

Probably needs a list of military callsigns added to fix this

Stands 501-506 attribution rules

To send a ROF message, select the “ROF” option in the Callsign menu of the aircraft in question. The example label below shows the indications when the message is sent (there are no indications in the accepting controller’s track label)

The indications are removed when a “Transfer”, “Trf & release” or “HOP” is performed.
Note: if a ROF is sent to a controller not using the TopSky plugin or the message fails to go through, an error message will be put into the Personal Queue Window. The message counter in the Global Menu will be highlighted in yellow if the window is not open.

Stands 221-225 attribution rules

If the CPDLC connection is terminated by the pilot, a “CPDLC P ABT” warning is inserted above the label. Left-clicking acknowledges the warning.

If an uplink clearance is not answered in time, a “ P LATE” warning will be inserted above the label. Left-clicking on it opens a menu that gives options to either abort the clearance or answer it yourself with “WILCO” (after confirmation from the pilot of course).

If an uplink clearance is sent successfully but you are not the currently active ATC unit in the aircraft’s CPDLC system, a “ NOT CDA” warning will be inserted above the label. Left-clicking acknowledges the warning and aborts the clearance, displaying the previous value in the label.

Stands 200-209 attribution rules

Stands 701-706 attribution rules

Stands 600-609 attribution rules

Stands 411-416 attribution rules

AT76 from GMFF got auto assigned to 146, bit too big 👀

Stands 421-426 attribution rules

sent an AJU citation to 601 thats 🅱️ ad

Military Apron attribution rules

Stands 401-406 attribution rules

Stands 122-126 attribution rules

A coordination is displayed by coloring the proposed values white in the track label and the flight lists. Additionally a message is displayed in the Message In Window for received coordinations and in the Message Out Window for coordinations sent by you.
To send a PEL (Planned Entry Level) coordination, left-click on the PEL value in the track label or a flight list. This opens a menu to select a value. To send a COPN (Entry Point) coordination, left-click on the COPN value in the track label or a flight list. This opens the Waypoint menu. Select “Routing”. This opens a menu to select the desired point. Keep an eye for the answer as it can be a counter-proposal as well, so the color of the values staying white doesn’t necessarily mean the coordination hasn’t been answered!

To answer an incoming coordination, left-click on a proposed value or the corresponding message in the Message In Window. This opens a menu where you can select the response (Accept, Refuse or Change). After the response, the track label and lists display depends on the answer:

• Accept: accepted values, sector state color
• Refuse: original values, sector state color (due to EuroScope bug, should be yellow)
• Change: new proposed values in white

ugly

A coordination is displayed by coloring the proposed values white in the track label and the flight lists. Additionally a message is displayed in the Message In Window for received coordinations and in the Message Out Window for coordinations sent by you.
To send an XFL (Exit Flight Level) coordination, left-click on the XFL value in the track label or a flight list. This opens a menu to select a value. To send a COPX (Exit Point) coordination, left-click on the COPX value in the track label or a flight list. This opens the Waypoint menu. Select “Routing”. This opens a menu to select the desired point. Keep an eye for the answer as it can be a counter-proposal as well, so the color of the values staying white doesn’t necessarily mean the coordination hasn’t been answered!

To answer an incoming coordination, left-click on a proposed value or the corresponding message in the Message In Window. This opens a menu where you can select the response (Accept, Refuse or Change). After the response, the track label and lists display depends on the answer:

• Accept: accepted values, sector state color
• Refuse: original values, sector state color (due to EuroScope bug, should be yellow)
• Change: new proposed values in white