ENOS + ENOR sector changes proposal

[Adrian2k]

Following ENOS changes has been proposed:

ENOS_CTR: Change main sector to sector 5
ENOS_4_CTR: New sector, only covering S3+S4
ENOS_8_CTR: Demote as a primary sector, only to be covering S8 regardless of other sectors being online.

Reason:
Sector 5 is rarely used and can be used as a main sector instead. This allows us to have a S3+S4 split that can be used during Oslo Monday events. IRL sector 3 and 4 is rarely split.
Most controllers believe ENOS8 only covers S8, which is not true. This change will simply allign with peoples expectations of ENOS8. Also no need for 3 main ENOS sectors

ENOR Suggestion:
Establish ENOR_SC_CTR which will cover the old ENOR_S_CTR's area.

[srekdal]

I agree with this proposal. It makes sense.

The available splits would then be:

If one logs on ENOS_3_CTR, they will only cover S3. This allow us to still split S3 and S4 if really needed.

[Adrian2k]

To be implemented:

• Implement ENOR_SC_CTR covering ENOS+ENSV+ENBD-S
• Change ENOS_CTR from 4R to 5R
• Implement ENOR_4_CTR as sector, covering 4+3
• ENOS_8_CTR to only cover S8
• ENSV_E_CTR to only cover S13+S14

To do:

• Make changes in GNG
• Update login profiles
• Update topsky relevant files (CPDLC stations, frequency display by border)
• Coordinate LOA Scottish
• Coordinate LOA Sweden
• Coordinate LOA Denmark
• Coordinate with Reykjavik
• Update VATspy sectors
• Update VATATIS

[Adrian2k]

@marud94 VATATIS changes:
Reassign ENOS_CTR to freq 127.250 (current yENOS_5_CTR)
Create new ENOS_4_CTR sector, freq 118.875
Create new ENOR_SC_CTR sector, freq 134.515
Remove ENSV_E_CTR

ENBR, ENZV, ENSG, ENBL, ENFL, ENHD, Ekofisk + Tampen - Remove ENSV_E_CTR

ENGM -Remove ENOR_8_CTR
ENCN - Remove ENOS_5_CTR
ENTO/ENRY - Remove ENOS_8_CTR & add ENOR_4_CTR (before ENOR_CTR)

ENBR, ENZV, ENSG, ENBL, ENFL, ENHD, Ekofisk + Tampen, ENGM, ENCN, ENTO, ENRY, ENRO, ENVA, ENOL, ENKB, ENML, ENAL - Add ENOR_SC_CTR (before ENOR_CTR)

ENOS_CTR 118.875 should not be touched until AIRAC day.
ENOS_4_CTR probably not smart to add until ENOS_CTR has been changed.

All other sectors safe to do now.

[Adrian2k]

@morettio
Topsky:

• All instances of 4R must be changed to 5R.
• Add frequency display for new 4R sector in area S3+S4
• Add frequency display for new ENOR_SC_CTR sector, ID: NC
• Add CPDLC station for NC
• Remove 8R frequency display in all sectors outside of S8 (so no longer Sweden).
• Remove 13R frequency displays (no longer bordering any FIR neighbours)

Anything else?

[krislarsen]

To be implemented:

• Implement ENOR_SC_CTR covering ENOS+ENSV+ENBD-S
• Change ENOS_CTR from 4R to 5R
• Implement ENOR_4_CTR as sector, covering 4+3
• ENOS_8_CTR to only cover S8
• ENSV_E_CTR to only cover S13+S14

To do:

• Make changes in GNG
• Update login profiles
• Update topsky relevant files (CPDLC stations, frequency display by border)
• Coordinate LOA Scottish
• Coordinate LOA Sweden
• Coordinate LOA Denmark
• Coordinate with Reykjavik
• Update VATspy sectors
• Update VATATIS

Sweden and Demark is informed and has "approved" changes, though LoA change still WIP.

[marud94]

(For own memory)
VATATIS changes:

• Reassign ENOS_CTR to freq 127.250 (currently ENOS_5_CTR)
• Create new ENOS_4_CTR sector, freq 118.875
• ENTO/ENRY - add ENOS_4_CTR (before ENOS_CTR)

NOT BEFORE NEW SECTORFILE IS READY

Rest as posted by Adrian is completed.

[morettio]

Topsky Done, It needs testing after sector release.

[Adrian2k]

GNG changes done (not tested).
VATspy changes done and sent for review.

Pending:
Topsky testing @morettio (?)
VATATIS @marud94

[marud94]

GNG changes done (not tested). VATspy changes done and sent for review.

Pending: Topsky testing @morettio (?) VATATIS @marud94

VATATIS completed

[Adrian2k]

@morettio MVA maps not working for ENOR_SC

[morettio]

Will fix this evening *Jakob Arne Brønstad* *Tlf: (+47) 986 50 540* tor. 16. mai 2024 kl. 17:28 skrev Adrian Bjerke ***@***.***>:

…

@morettio <https://github.com/morettio> MVA maps not working for ENOR_SC — Reply to this email directly, view it on GitHub <#370 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOICE6JSFLGUR3XRCXDLW7DZCTGB7AVCNFSM6AAAAABGNX2D7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVGU2TEMRZGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[morettio]

@morettio MVA maps not working for ENOR_SC

Done @Adrian2k