WIP: Resectorise TCSE into smaller RW sectors

[cpawley]

Fixes #5426

Needs OPS input
The Wiki needs updating when Merged
UKCP API update for next frequencies

Reference image:
https://britishskydiving.org/wp-content/uploads/2023/12/Form-185C-London-Terminal-Control-Sectors-Complex-issue-18.pdf

Summary of changes

• Existing London TC SE references split into TC BIG/GODLU/TIMBA
• Added some internal agreements (between the above)
• Added new lines to divide previous contiguous pieces of airspace

Discussions

There are quite some changes here which I shouldn't decide - this is something for the ops team and the community to input on...

• (1) Agreements/Airport/THAMES_TCGOD.txt
• (2) Agreements/Airport/THAMES_TCTIM.txt
• (3) Agreements/Internal/15_TCBIG.txt & Agreements/Internal/TCBIG_TCGOD.txt
• (4) Agreements/Internal/TCGOD_15.txt
• (5) Airports/EBOS/Sector_Boundaries.txt - ln 2
• (6) Do we define frequencies at this point? We have two frequencies spare which should be sufficient to let us define opening each sector solo and bandboxes...
• (7) note for me - If new posn's handle top down

Screenshots (if necessary)

I am TCSE (doing all 3 sectors) - LONS|LLAPP|KKAPP|THAMES online

I am TCSE (TC GODLU is online) - LONS|TCGOD|LLAPP|KKAPP|THAMES online
GODLU to GODLU - I am left with BIG+TIMBA online (have to fix EGMD)

I am TCSE (TC TIMBA is online) - LONS|TCTIM|LLAPP|KKAPP|THAMES online
TIMBA and GODLU to TIMBA - I am left with BIG online (SODVU box makes sense, EGMD needs fixing)

I am TCSE (TC TIMBA and TC GODLU online) - LONS|TCTIM|TCGOD|LLAPP|KKAPP|THAMES online)
Nothing changes (which is expected)

I am TC GODLU (no other TCSE online - LONS|LLAPP|KKAPP|THAMES online)
I own BIG and GODLU as expected

I am TC GODLU (TC TIMBA comes online - LONS|TCTIM|LLAPP|KKAPP|THAMES online)
no change - expected

I am TC GODLU (TC BIG(actually TC SE) and TC TIMBA on - LONS|TCBIG|TCTIM|LLAPP|KKAPP|THAMES online)
TC BIG goes to TCSE

I am TC TIMBA (no other TCSE online - LONS|LLAPP|KKAPP|THAMES online)
LONS owns BIG, I own the rest

I am TC TIMBA (TC SE is on - LONS|TCSE|LLAPP|KKAPP|THAMES online)
Nothing changes

I am TC TIMBA (TC SE and TC GODLU is on LONS|TCSE|TCGOD|LLAPP|KKAPP|THAMES online)
I am left only with TIMBA

I am TC TIMBA, if GODLU is open and TCSE closes, I still retain TIMBA (BIG goes to GODLU) (LONS|TCGOD|LLAPP|KKAPP|THAMES online)

[cpawley]

Ref to the #Discussions section above - these need input from people who are not me :)

Probably easiest to start with is Discussion 5

https://github.com/VATSIM-UK/UK-Sector-File/pull/5427/files#diff-c78d61d63333521197b841b20b91b65805a32a2db786447e2b191f2346ae7437

Previously the entire part of the EBOS line was shown to TC SE - but the North part is exactly overlapping the TC JACKO sector - so I swapped it to TC JACKO.

=====

Regarding Discussion 6

I propose a way to handle the following 5 Situations:

TCSE online only - BIG/GODLU/TIMBA are covered by TCSE (as now)
Split BIG and GODLU|TIMBA together - cover BIG as TCSE and GODLU|TIMBA with the TC TIMBA freq
Split TIMBA and GODLU|BIG together - cover TIMBA as TC TIMBA and GODLU|BIG with the TC GODLU freq
Split GODLU and TIMBA|BIG together - cover GODLU as TC GODLU and TIMBA|BIG with the TC SE freq
All Split - cover GODLU as TC GODLU, TIMBA as TC TIMBA and BIG as TCSE.

The (event) positions would then be
LTC_ST_CTR:London Control:120.180:TIMBA:L:LTC:CTR:-:-:0301:0377:N051.36.23.000:E001.12.10.000
LTC_SG_CTR:London Control:135.325:GODLU:L:LTC:CTR:-:-:0301:0377:N051.36.23.000:E001.12.10.000

[kristiankunc]

@cpawley I've marked the PR as a draft as it is WIP, once it is ready for review, you can convert it back.

[cpawley]

Regarding Discussion 6

I propose a way to handle the following 5 Situations:

TCSE online only - BIG/GODLU/TIMBA are covered by TCSE (as now) Split BIG and GODLU|TIMBA together - cover BIG as TCSE and GODLU|TIMBA with the TC TIMBA freq Split TIMBA and GODLU|BIG together - cover TIMBA as TC TIMBA and GODLU|BIG with the TC GODLU freq Split GODLU and TIMBA|BIG together - cover GODLU as TC GODLU and TIMBA|BIG with the TC SE freq All Split - cover GODLU as TC GODLU, TIMBA as TC TIMBA and BIG as TCSE.

The (event) positions would then be LTC_ST_CTR:London Control:120.180:TIMBA:L:LTC:CTR:-:-:0301:0377:N051.36.23.000:E001.12.10.000 LTC_SG_CTR:London Control:135.325:GODLU:L:LTC:CTR:-:-:0301:0377:N051.36.23.000:E001.12.10.000

This is now implimented in the PR and the screenshots above

[PLM1995]

@cpawley Does Discussion 5 and Discussion 6 refer to something I'm unaware of sorry? To me this just feels like quite a major change appearing out of the blue, I wasn't aware of any internal discussion surrounding it :) Obviously area stuff is a bit beyond my knowlegde.

[cpawley]

@cpawley Does Discussion 5 and Discussion 6 refer to something I'm unaware of sorry? To me this just feels like quite a major change appearing out of the blue, I wasn't aware of any internal discussion surrounding it :) Obviously area stuff is a bit beyond my knowlegde.

Hi!

5/6 refers to my bullet points above as things that should reach a resolution with ops input before this is merged. Have tried to make that clearer by editing the first post.

The baseline will be that this does not actually change anything (other than a few ms of load time) by default - it just gives options for the future (e.g. if we do a Gatwick event and want to split things in TCSE differently than in the past).

This would be in the style of adding functionality in TC Midlands way back when ("just in case") - and now it's a sector of it's own self-standing.

LTC SE and LTC SW are the last remaining parts of our sector setup without the true real world components listed - so I was just following the way we have represented all the other parts of the enroute airspace (though admittedly many of these splits I also did, so it's a bit of a self fulfilling prophacy...

The baseline would be to simply define all the mini sectors and give them all to TCSE and then be done with it - but there's obviously more that could be done here with making sectors that the Ops team could activate for a Thames/Gatwick/Heathrow event if they wanted

[KHardern]

@cpawley Sorry for not inputting sooner. Regarding discussion point 6:
My instinct is to do slightly different than your proposal, specifically to have GODLU cover TIMBA. My thinking as follows:

• Our most likely use of this in an event split is for Gatwick events. Therefore the most useful split is to be able to open TIMBA alone (purely to manage holding at peak) and secondarily to have a way to split GODLU+TIMBA from BIG (in any config)
• Our second most likely use for this being Heathrow events, particularly deps, where an option to separate BIG from the other two (as above) is useful
• GODLU+BIG is in itself not a useful split, because there is no substantial traffic flow between those two positions in normal circumstances and an event with any of those flows is not going to be useful to separate TIMBA. So the utility of this split is to split off TIMBA. I think we can debate which way around it is easier to split off in an 'emergency', however it's probably lower workload to transfer fewer planes (which is probably the TIMBA stack)

[KHardern]

Discussion point 6:
I think there's no harm in putting in frequencies. As they are event-only, we can always change them around if we decide it was a bad idea.
Both of the r/w GODLU/TIMBA frequencies do have conflicts with TWR positions in EUD (over 300NM away) and so are probably OK as event-only sectors taking the risk of text conflict at higher altitude. I would prefer us not to allocate more than 2 frequencies to it as we are likely never to use.

[KHardern]

Ref to discussion 5:
EBOS lines, I think I drew them that way for the EBOS airspace but probably wasn't thinking too much about the TCSE/Jacko boundary.
North line could be split in 2 of course and display half for TCSE. Your way is fine too - as ultimately there will always be a Brussels line over the top of the display anyway.