{"action":"opened","issue":{"url":"https://api.github.com/repos/zlsa/atc/issues/745","repository_url":"https://api.github.com/repos/zlsa/atc","labels_url":"https://api.github.com/repos/zlsa/atc/issues/745/labels{/name}","comments_url":"https://api.github.com/repos/zlsa/atc/issues/745/comments","events_url":"https://api.github.com/repos/zlsa/atc/issues/745/events","html_url":"https://github.com/zlsa/atc/issues/745","id":191839698,"number":745,"title":"Separate \"airport\" from \"sector\"","user":{"login":"erikquinn","id":5103735,"avatar_url":"https://avatars.githubusercontent.com/u/5103735?v=3","gravatar_id":"","url":"https://api.github.com/users/erikquinn","html_url":"https://github.com/erikquinn","followers_url":"https://api.github.com/users/erikquinn/followers","following_url":"https://api.github.com/users/erikquinn/following{/other_user}","gists_url":"https://api.github.com/users/erikquinn/gists{/gist_id}","starred_url":"https://api.github.com/users/erikquinn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erikquinn/subscriptions","organizations_url":"https://api.github.com/users/erikquinn/orgs","repos_url":"https://api.github.com/users/erikquinn/repos","events_url":"https://api.github.com/users/erikquinn/events{/privacy}","received_events_url":"https://api.github.com/users/erikquinn/received_events","type":"User","site_admin":false},"labels":[{"id":122474653,"url":"https://api.github.com/repos/zlsa/atc/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-27T03:18:30Z","updated_at":"2016-11-27T03:18:30Z","closed_at":null,"body":"Currently, everything that has to do with playing in a certain airspace is stored as properties of the \"airport\". But what about places where a single ATC facility is providing services to *multiple* airports? (aka just about everywhere)\r\n\r\nWork should be done to move away from keeping things like navigational data (fixes/airways/procedures), video maps, etc under the airport, and make a new class called `Sector` which represents the given ATC control position being simulated. For example, if I am working Miami Approach (consolidated to a single sector), I would work arrivals/departures to/from KMIA, KFLL, KOPF, KTMB, and others. My `Sector` has the stuff relating to my role in the simulation, and each of the airports are an `Airport`, which have their own runways defined within."}}
{"actor":{"display_login":"erikquinn"}}