We need the list in xml format, not in pdf.
That wouldn't really help you - the XML comes from a relational database that can handle multiple (i.e. more than two) legs per flight:
<?xml version="1.0" encoding="utf-8" ?>
- <Flight>
<FlightNumber>UAL840</FlightNumber>
<Callsign>United 840</Callsign>
- <Leg>- <Origin>
<ICAOCode>YMML</ICAOCode>
<IATACode>MEL</IATACode>
<AirportName>MELBOURNE</AirportName>
<Country>AUSTRALIA</Country>
</Origin>
- <Destination>
<ICAOCode>YSSY</ICAOCode>
<IATACode>SYD</IATACode>
<AirportName>SYDNEY (KINGSFORD SMITH)</AirportName>
<Country>AUSTRALIA</Country>
</Destination>
<GCDistanceNM>381</GCDistanceNM>
</Leg>
- <Leg>- <Origin>
<ICAOCode>YSSY</ICAOCode>
<IATACode>SYD</IATACode>
<AirportName>SYDNEY (KINGSFORD SMITH)</AirportName>
<Country>AUSTRALIA</Country>
</Origin>
- <Destination>
<ICAOCode>KLAX</ICAOCode>
<IATACode>LAX</IATACode>
<AirportName>LOS ANGELES (INTERNATIONAL)</AirportName>
<Country>UNITED STATES</Country>
</Destination>
<GCDistanceNM>6508</GCDistanceNM>
</Leg>
- <Leg>- <Origin>
<ICAOCode>KLAX</ICAOCode>
<IATACode>LAX</IATACode>
<AirportName>LOS ANGELES (INTERNATIONAL)</AirportName>
<Country>UNITED STATES</Country>
</Origin>
- <Destination>
<ICAOCode>KORD</ICAOCode>
<IATACode>ORD</IATACode>
<AirportName>CHICAGO (O'HARE INTERNATIONAL)</AirportName>
<Country>UNITED STATES</Country>
</Destination>
<GCDistanceNM>1512</GCDistanceNM>
</Leg> </Flight>
As the previous poster points out, the simplistic From/To/Via structure of the NavData flights table can't handle that - UAL840 never gets as far as Chicago in your database.