Update LIT, JAN, FSM, CBM, HOP and NMM approach control boundaries and the FSM recognized prefixes.
Description
These changes include updating several approach control boundaries to include notable airspace shelf areas and corrections. FSM position prefixes modified to coincide with vNAS network position callsign changes.
Motivation and Context
The original data pulled from the ZME sector file into the Project did not contain the airspace fidelity that the ARTCC currently uses. ZME decided it was in the best interest of the pilots using the resource and the controller providing service to show the greatest extent of the approach control airspace. Additionally, the CBM and NMM approach control boundary used invalid boundary data.
How to prove the effect of this PR?
CBM:
FSM:
HOP:
JAN:
LIT:
NMM:
Additional info
Is this a breaking change?
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
[x] My change or addition follow the formatting standard of the project.
[ ] I am on the list of approved contributors. (ZME FE pending approval requested 10/2023).
Update LIT, JAN, FSM, CBM, HOP and NMM approach control boundaries and the FSM recognized prefixes.
Description
These changes include updating several approach control boundaries to include notable airspace shelf areas and corrections. FSM position prefixes modified to coincide with vNAS network position callsign changes.
Motivation and Context
The original data pulled from the ZME sector file into the Project did not contain the airspace fidelity that the ARTCC currently uses. ZME decided it was in the best interest of the pilots using the resource and the controller providing service to show the greatest extent of the approach control airspace. Additionally, the CBM and NMM approach control boundary used invalid boundary data.
How to prove the effect of this PR?
CBM:
FSM:
HOP:
JAN:
LIT:
NMM:
Additional info
Is this a breaking change?
Checklist