Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best practice to display control boundaries #628

Open
Mistadouf opened this issue Dec 11, 2022 · 1 comment
Open

Best practice to display control boundaries #628

Mistadouf opened this issue Dec 11, 2022 · 1 comment
Labels
discussion question Further information is requested

Comments

@Mistadouf
Copy link
Contributor

Mistadouf commented Dec 11, 2022

In Canada, we have some areas of an FIR that are controlled by another FIR's ACC. E.g. Montreal covers parts of Toronto. Moncton covers a part of Montreal. Edmonton covers parts of Winnipeg and Toronto.
What would be the best practice to show pilots who they have to contact in these delegated areas, as they aren't necessarily from SFC-FL600?

I'm asking this because you mention that:

Included Sectors
To keep the map clear and not too cluttered, any new additions to the dataset should cover whole FIR's (e.g. HECC/KZFW). Some exceptions can be made for further splits if the (sub)sector is controlled consistently outside of events and the amount of traffic justifies it. This will be reviewed on a case by case basis.

@Mistadouf
Copy link
Contributor Author

image

@Adrian2k Adrian2k added question Further information is requested discussion labels Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants