1
0
Fork 0
fgdata/Data/AI/FlightPlans/KSFO_depart_east_01R.xml
ehofman 2afaa933e3 David Culp:
First, preferences.xml will define the scenario filename.

For now, the other way of defining ai objects still works, so the sailboat
stays in preferences.xml.  Later, I'll move the sailboat into the demo
scenario.  If no scenario filename is given, then no scenario will be
processed.

I changed the demo scenario to create two 737's, one takes off on runway 01L,
and the other takes off on runway 01R.  This will make a good demo for the ai
system.  One problem, if you takeoff on 28L/R right away, you might run into
the taking-off 737's, or be scared.
2004-05-17 08:46:34 +00:00

73 lines
No EOL
1.6 KiB
XML

<?xml version="1.0"?>
<!-- Depart KSFO to the east over OAK and LIN
The departure can be found at http://www.airnav.com/airport/KSFO
Format:
<name> Waypoint name.
<lat> latitude, degrees
<lon> Longitude, degrees
<alt> altitude, feet
<crossat> Crossing altitude, feet
<ktas> Knots true airspeed
-->
<PropertyList>
<flightplan>
<wpt>
<name>01R</name>
<lat>37.606844</lat>
<lon>-122.380667</lon>
<alt>11.0</alt>
<ktas>20</ktas>
<gear-down>true</gear-down>
</wpt>
<wpt>
<name>accel</name>
<lat>37.607269</lat>
<lon>-122.380391</lon>
<alt>11.0</alt>
<ktas>150</ktas>
</wpt>
<wpt>
<name>rotate</name>
<lat>37.618127</lat>
<lon>-122.373221</lon>
<alt>400.0</alt>
<ktas>180</ktas>
<gear-down>false</gear-down>
</wpt>
<wpt>
<name>runway-end</name>
<lat>37.626579</lat>
<lon>-122.367638</lon>
<alt>10000.0</alt>
<ktas>280</ktas>
</wpt>
<wpt>
<name>OAK</name> <!-- Oakland VOR, 116.8 -->
<lat>37.726</lat>
<lon>-122.223667</lon>
<alt>30000.0</alt>
<ktas>360</ktas>
</wpt>
<wpt>
<name>END</name> <!-- Linden VOR, 114.8 -->
<lat>38.0745</lat>
<lon>-121.00383</lon>
<crossat>30000.0</crossat>
</wpt>
<wpt>
<name>EOF</name>
</wpt>
</flightplan>
</PropertyList>