Howto:Make a helipad
Creating the model
Every face in FlightGear is solid and can be landed on by default, so helipads can be modeled just like any other object.
Placing lights is very easy. FlightGear contains two basic lights in the $FG ROOT/Models/Effects/Lights/ directory: the red one is usually used to mark obstructions, while the green ones mark the helipad. You can link to those models from your buildings .xml file like this:
<model> <path>Models/Effects/Lights/GreenLight.xml</path> <offsets> <x-m> -11.50</x-m> <y-m>-160.50</y-m> <z-m> 34.7</z-m> <heading-deg>0</heading-deg> </offsets> </model>
Right now your helipad can be landed on, but we do like to takeoff from it aswell, don't we? Therefore, we need to extend the apt.dat file, which stores all airport information. You can find it likely in $FG ROOT/Airports.(Mac route = FlightGear/data/Airports). Before we can edit the file we need to unzip it first. Be sure to always make a backup before you change anything.
Once it's unpacked, open it with any texteditor you like (TextEdit is prefered for MAC users) and scroll down to the bottom of the file, where the heliports are listed (lines with [H]) in alphabetical order. Now we need to add one or two line(s) to the file, in order to add our helipad as a startup location.
As an example, the lines below are used for the helipad on the roof of a large hospital in the Netherlands.
17 126 0 0 EH0001 [H] VU medisch centrum
10 52.33434 4.85911 H1x 360.00 40 0000.0000 0000.0000 36 111111 2 0 2 0.25 0 0300.0300
In the airport list of FGrun it will appear as EH0001, VU medisch centrum [H] with runway H1.
Let us take a closer look at these two lines. The first line is only neccesary when the airport/heliport does not exist yet. If that is the case, you can add the helipad with just the second line.
|17||Defines this as a heliport.|
|126||Elevation above MSL.|
|0||No control tower available.|
|0||No default buildings.|
|EH0001||The ICAO code of the helideck.|
|10||Defines this as runway (in this case helipad).|
|52.33434||Latitude of helipad.|
|4.85911||Longitude of helipad.|
|H1x||Runway number (in this casehelipad number).|
|360.00||Runway heading (true).|
|40||Length of runway (in this case helideck) in feet.|
|0000.0000 0000.0000||Just leave them like this.|
|36||Width of runway, also in feet.|
|111111 2 0 2 0.25 0 0300.0300||Just leave them like this.|
To find the center of the helipad, place a model at the center of the helipad using the UFO and press the key to export the location data to the console. The lat, long and alt values can be copied to the lines that you include in the apt.dat file.
Save the file after you've made your changes and zip it again, overwriting/replacing the old apt.dat.gz file.
At the time of writing this wiki, the Mac's GUI launcher cannot synchronize the apt.dat update at run time, and is also not able to access the Helipad part of the apt.dat file, and therefore the Heliports are not listed in the ‘position’ page of the Launcher, where you usually choose your starting points.
- Add --airport=EH0001 (replace with your helipad ICAO code) in the window on the ‘Others’ page of the Launcher.
- In the ‘Positions’ page of the Launcher, choose and select KSFO.
- Now just start your flight as usually.
Refresh your FlightGears airport cache, with the button on the Airport page of the Launcher. Now your heliport should come up in the list. Just select it as every other airport and run FlightGear to see if your hard work paid of.
If you want your helipad to be included with a further FlightGear release, make sure to send your change/addition to apt.dat to http://data.x-plane.com/ and upload your model to the FlightGear Scenery Database.
Untill FlightGear moves to the new apt.dat format, place your apt.dat changes in FlightGear User Created Helipad List, so others can enjoy your helipads aswell. If you send your changes to Vic Marriott(firstname.lastname@example.org), he will update the list for you.