fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Data/AI/FlightPlans/KSFO_depart_south_01L.xml

110 lines
2.5 KiB
XML
Raw Normal View History

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
<?xml version="1.0"?>
<!-- Based on the Porte departure at KSFO, left turnout to WAGES
The departure can be found at http://www.airnav.com/airport/KSFO
Format:
David Culp: 1. Removed aircraft roll on ground. 2. Decreased descent pitch angle. 3. Updated flightplans to include <on-ground> 4. Fixed property indexing, so all AI aircraft have their own property branch The default value of <on-ground> is false, so you only need to specify it when on the ground. For takeoff you need to specify <on-ground>true</on-ground> for the first waypoint, and for the acceleration waypoint. For landing you need to specify it for the touchdown point and any taxi points.
2004-05-21 16:51:05 +00:00
<name> Waypoint name. When a waypoint named END is reached
the AI airplane will delete itself.
<lat> latitude, degrees (-90 to 90)
<lon> Longitude, degrees (-180 to 180)
<alt> altitude above sea level, feet
<crossat> Crossing altitude, feet
<ktas> Knots true airspeed
<on-ground> set true if on the ground
<gear-down> set true for gear down, false for gear up
<flaps-down> set true for flaps down, false for flaps up
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
-->
<PropertyList>
<flightplan>
<wpt>
<name>01L</name>
<lat>37.609015</lat>
<lon>-122.382153</lon>
<alt>11.0</alt>
<ktas>20</ktas>
David Culp: 1. Removed aircraft roll on ground. 2. Decreased descent pitch angle. 3. Updated flightplans to include <on-ground> 4. Fixed property indexing, so all AI aircraft have their own property branch The default value of <on-ground> is false, so you only need to specify it when on the ground. For takeoff you need to specify <on-ground>true</on-ground> for the first waypoint, and for the acceleration waypoint. For landing you need to specify it for the touchdown point and any taxi points.
2004-05-21 16:51:05 +00:00
<on-ground>true</on-ground>
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
<gear-down>true</gear-down>
</wpt>
<wpt>
<name>accel</name>
<lat>37.6093</lat>
<lon>-122.381964</lon>
<alt>11.0</alt>
<ktas>150</ktas>
David Culp: 1. Removed aircraft roll on ground. 2. Decreased descent pitch angle. 3. Updated flightplans to include <on-ground> 4. Fixed property indexing, so all AI aircraft have their own property branch The default value of <on-ground> is false, so you only need to specify it when on the ground. For takeoff you need to specify <on-ground>true</on-ground> for the first waypoint, and for the acceleration waypoint. For landing you need to specify it for the touchdown point and any taxi points.
2004-05-21 16:51:05 +00:00
<on-ground>true</on-ground>
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
</wpt>
<wpt>
<name>rotate</name>
<lat>37.61971</lat>
<lon>-122.375098</lon>
<alt>400.0</alt>
<ktas>180</ktas>
<gear-down>false</gear-down>
</wpt>
<wpt>
<name>runway-end</name>
<lat>37.626773</lat>
<lon>-122.370432</lon>
<alt>30000.0</alt>
<ktas>225</ktas>
</wpt>
<wpt>
<name>SFO350at4</name> <!-- SFO 350/04, 115.8 -->
<lat>37.685667</lat>
<lon>-122.363667</lon>
<alt>30000.0</alt>
<ktas>225</ktas>
</wpt>
<wpt>
<name>turn1</name>
<lat>37.693788</lat>
<lon>-122.384405</lon>
<alt>30000.0</alt>
<ktas>225</ktas>
</wpt>
<wpt>
<name>turn2</name>
<lat>37.6665</lat>
<lon>-122.5</lon>
<alt>30000.0</alt>
<ktas>265</ktas>
</wpt>
<wpt>
<name>PORTE</name>
<lat>37.4898333</lat>
<lon>-122.4745</lon>
<alt>30000.0</alt>
<ktas>350</ktas>
</wpt>
<wpt>
<name>PESCA</name>
<lat>37.2681667</lat>
<lon>-122.3286667</lon>
<alt>30000.0</alt>
<ktas>370</ktas>
</wpt>
<wpt>
<name>END</name> <!-- WAGES intersection, OSI 116/36, 113.9 -->
<lat>36.991</lat>
<lon>-121.737</lon>
</wpt>
<wpt>
<name>EOF</name>
</wpt>
</flightplan>
</PropertyList>
Copy permalink