I made a rather crude Python script to generate a Glideslope.cfg entry for a base:
https://pastebin.com/tr5euFqM
I'm not too confident trying to overwrite people's .cfg files so have left the user to do some copying and pasting.
Usage:
1. Copy contents of the entire base file (e.g. Zaragoza.cfg) to the clipboard
2. Run the script in Python and paste when prompted, then enter q on a single line to end the multi-line input.
3. Copy and paste the output string into the base section in Glideslope.cfg
Support:
Base position and name are parsed.
Runway lengths and directions are calculated.
Multiple runways in the same direction are handled.
Limitations:
PAPI and VASI are assumed to be at the default distances.
Multiple runways in the same direction are suffixed with a,b,c instead of L,C,R but you can manually rename these.
https://pastebin.com/tr5euFqM
I'm not too confident trying to overwrite people's .cfg files so have left the user to do some copying and pasting.
Usage:
1. Copy contents of the entire base file (e.g. Zaragoza.cfg) to the clipboard
2. Run the script in Python and paste when prompted, then enter q on a single line to end the multi-line input.
3. Copy and paste the output string into the base section in Glideslope.cfg
Support:
Base position and name are parsed.
Runway lengths and directions are calculated.
Multiple runways in the same direction are handled.
Limitations:
PAPI and VASI are assumed to be at the default distances.
Multiple runways in the same direction are suffixed with a,b,c instead of L,C,R but you can manually rename these.
