Issues Regarding APAC Region

[BokBoy]

Hello,
Continuing from #101 to fix the extending to part of the apac region map.
Original idea was about checking controller description to see it but I was proven wrong.
Works on APAC map (search up, VATPAC map, click 2nd or 3rd link)
It would be cool for an implementation.
Adding labels Bug and Low priority (because it would be nice but it's not required)

Update - changed title to issues regarding APAC region because I found a couple new ones.

[BokBoy]

Welp the labels didn't add...

[AgentWolfFBI]

Just transferred what was on the old thread to here;

The only way to effectively implement this would be to identify which FIR frequencies are open. Extending controllers couple the frequencies of the sectors they're extending to. For example, if a controller's primary sector was Yarrowee [YYWE] and they were extending Eildon Weir [YELW] and Bindook [YBIK], the following frequencies would be coupled & open: 134.325, 123.75, 129.8.

Each sector has a frequency:
YWE: 134.325
BIK: 123.75
ELW: 129.8
etc

This is how the VATPAC map works. The sectors and their frequencies can be found here.

As to how VATPAC is able to identify which frequencies are open, I'm not sure. The code is written primarily in JS and can be found on Github here. I know @badvectors works on the VATPAC map and might be able to provide some insights.

[BokBoy]

Found another issue - When you fixed the approaches and departures, it shows up like this on the ATC stats menu.

Its properly identified on the map.

[barf]

possible duplicate of anti-meridian issue #65
#65

but that issue was closed... this really needs attention