importfixpairs

Overview ¶

cmd/importfixpairs/main.go Copyright(c) 2022-2026 vice contributors, licensed under the GNU Public License, Version 3. SPDX: GPL-3.0-only

Imports STARS DMS fix-pair adaptation dumps into a facility configuration. Input is the text dumps of the three DMS fix-pair windows, given in any order and identified by the table sections they contain:

• "Fix Pair Configurations (1 of 2)": the FIXPAIRS table (fix pairs in sequential match order, with flight type and RNAV route flag)
• "Fix Pair Configurations (2 of 2)": the CONFIGURATION table (the facility's configuration plans) and the FIXPAIRS_TCP table (the owning TCP per fix pair and plan)
• "Fix Pair Reassignment": the FIXPAIR_REASSIGNMENT table (derived fix pair rules; its columns continue in a second table joined by row)
• "Significant Points" (optional): the FIX table, whose adapted locations resolve fixes the fix pairs reference

The tables are combined into a "fix_pair_configuration" block that replaces any existing one in the target config's "facility_adaptations", preserving the rest of the file. A facility with a single configuration plan gets its TCPs keyed by "*" (the plan is always in effect); with several plans the TCPs are keyed by plan id, which must then be renamed by hand to the vice configuration ids the scenarios use. The FIXPAIRS table's Terminal Sector, From Facility, and partial-resectorization Fix Pair Id columns have no vice counterpart and are dropped, as are fix pairs whose TCPs are not control positions of the target facility.

Fixes the fix pairs reference but the config doesn't adapt are resolved into new "significant_points" / "airports" entries where possible: from the significant points dump when one is given, and otherwise from the nav database (navaids and fixes become empty entries, which vice locates at load; airports get their name and location). A derived location is only accepted within -range nm of the facility center, guarding against a same-named fix elsewhere in the country. STARS-internal derived fixes (pseudo fixes with no real-world location) can only come from a significant points dump; without one they are reported for hand adaptation.

After writing, the config is validated the same way vice validates it at load and remaining problems are reported.

Must be run from the top of a vice checkout so that the resources are found.

Usage:

importfixpairs [-dryrun] -config resources/configurations/ZNY/N90.json dump.txt...