Restructure Airport.departures to utilize routes

[erikquinn]

Currently, departures are like:

"departures": {
    "airlines": [
      ["ual", 10],
      ["aal", 8],
      ["dal", 6],
      ["ual/long", 5],
      ["aal/long", 2],
      ["dal/long", 2],
      ["swa", 5],
      ["asa", 3],
      ["aca", 2],
      ["cpa", 2],
      ["baw/long", 2],
      ["ups", 1],
      ["fdx", 1],
      ["klm/long", 2],
      ["afr/long", 2],
      ["uae", 4],
      ["kal/long", 2],
      ["vir", 2]
    ],
    "destinations": [
      "MOLEN7", "OFFSH9", "PORTE7", "QUIET7"
    ],
    "type": "random",
    "offset": 0,
    "frequency": 38
  }

...and arrivals are like:

  "arrivals": [
    {
      "type": "random",
      "route":   "QUINN.BDEGA2.KSFO",
      "frequency": 10,
      "altitude":  24000,
      "speed":    280,
      "airlines":  [
        ["ual", 5],
        ["ual/long", 2],
        ["swa", 1],
        ["dal", 5],
        ["dal/long", 2],
        ["aal", 5],
        ["aal/long", 2],
        ["asa", 1],
        ["fdx", 1]
      ]
    },
    {
      "type": "random",
      "route":   "BSR.BSR2.KSFO",

Obviously, the approach used with departures does not enable us to use routes, just SIDs with randomly assigned exit points. To resolve this the correct way, the departures should be changed such that they are set up in the airport files like the arrivals are: with routes.

[erikquinn]

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

Thank you!

Closing this issue.