How zla-artcc/vatis-profiles works
Project Overview
• This project is a specialized profile compilation tool for vATIS. It takes raw data stored in multiple .station files organized by TRACON/region (CTR, JCF, L30, SBA, SCT) and compiles them into standardized JSON profile files (both production and DEV versions).
• The tool includes two main Python scripts – one for generating production profiles (compiler.py) and another for DEV/test profiles (devcompiler.py).
Main Components
a. Input Data:
• The “stations” directory containing subdirectories (CTR, JCF, L30, SBA, SCT).
• Each subdirectory has individual .station files which hold station-specific data.
b. Compilation Engine:
• "compiler.py": Reads all relevant .station files and produces non-DEV, auto-updating JSON files (e.g., vATIS-Profile-ZLA.json, vATIS-Profile-ZLA-2.json, vATIS-Profile-ZLA-Static.json).
• "devcompiler.py": Reads the same or similar inputs for generating DEV test profile JSON files (e.g., vATIS-Profile-DEV-ZLA.json, vATIS-Profile-DEV-SCT.json).
c. Output Artifacts:
• JSON files such as vATIS-Profile-DEV-SCT.json, vATIS-Profile-DEV-ZLA.json, and others which are then used by vATIS systems.
d. Versioning and Contribution Process:
• The README instructs contributors to edit the .station files and not the JSON outputs. This highlights the importance of the raw data and how the compilers process that data.
Relationships and Interactions
• The compiler (both production and DEV versions) will have input dependencies on the stations’ data and then output the consolidated JSON profiles.
Architectural Patterns and Design Principles
• Design is file-based and script-driven – a simple pipeline: raw files → compiler processing → JSON outputs.
• Separation of concerns is visible by having separate scripts for DEV and production profiles.
• Emphasis on auto-updating for certain profiles indicates that the system is designed for dynamic content updates through periodic (or triggered) compilation.
Technologies and Tools
• Python for compiler scripts.
• JSON for data output formats.
• The project is version controlled (with .gitignore present) on GitHub.
• The file organization within stations indicates a modular approach by geographical regions.