Create the lateral boundaries of Valley TRACON in ZHU #357
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dirtyformal
requested changes
Apr 2, 2024
|
|
kmoberg
approved these changes
Apr 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add the Valley TRACON in ZHU.
Motivation and Context
Before vNAS and CRC, ZHU ran a consolidated TRACON encompassing Corpus and Valley airspaces. We have since decided to unmerge the two facilities and return to real-world mirror of the area. This file creates the Valley TRACON.
How to prove the effect of this PR?
All FAA TRACONS showing the split between Corpus and Valley.
Additional info
Yellow sector area in screenshot from QGIS.
Is this a breaking change?
Checklist