It is possible to use compressed representation of flight segments to reduce bandwidth. If configured, the XML response containing flight data will have CompressedSegmentList element in place of SegmentList.
XML Field |
Description |
CompressedSegmentList [Optional]
|
Compacted version of SegmentList, please contact Travelfusion to activate. |
-CompressedSegment |
Compacted version of Segment with value formatted in following way: origin_code,destination_code,depart_date,arrival_date,tf_vending_operator_code, tf_operator_code,flight_code,flight_number,tf_travel_class_code,[STOPS_LIST],supplier_travel_class,aircraft_name,aircraft_code,duration...
New fields may be added at any time on the end of this list of items. Your application should be able to ignore extra fields that may appear without notice on the end of the list. You should consider all values as optional. If any value is not supplied, it will appear as an empty string between the delimiting ',' characters.
Fields description origin_code corresponds to Segment/Origin/Code destination_code corresponds to Segment/Destination/Code depart_date corresponds to Segment/DepartDate arrival_date corresponds to Segment/ArriveDate tf_vending_operator_code corresponds to Segment/TFVendingOperator/Code tf_operator_code corresponds to Segment/TFOperator/Code flight_code corresponds to Segment/FlightId/Code flight_number corresponds to Segment/FlightId/Number tf_travel_class_code could have following values: VALUE | MEANING | 0 | Economy With Restrictions | 1 | Economy Without Restrictions | 2 | Economy Premium | 3 | Business | 4 | First |
STOPS_LIST could be either empty string in case there is no known stops for this segment or comma separated list of stops in following format: {stop_location_code,stop_arrival_date,stop_departure_date,stop_duration_minutes} stop_location_code corresponds to Segment/StopList/Stop/Location/Code stop_arrival_date corresponds to Segment/StopList/Stop/ArriveDate stop_departure_date corresponds to Segment/StopList/Stop/DepartDate stop_duration_minutes corresponds to Segment/StopList/Stop/Duration supplier_travel_class corresponds to Segment/TravelClass/SupplierClass new aircraft_name corresponds to Segment/AircraftType/AircraftName new aircraft_code corresponds to Segment/AircraftType/AircraftCode new duration corresponds to Segment/Duration new
New fields may be added at any time on the end of this list of items. Your application should be able to ignore extra fields that may appear without notice on the end of the list. You should consider all values as optional. If any value is not supplied, it will appear as an empty string between the delimiting ',' characters. I.e. [{,,,}] will mean that there is one stop along the route but no information is available about that stop.
|
Examples
<CompressedSegmentList> <CompressedSegment>DEL,MAA,18/12/2014-06:35,18/12/2014-09:25,SG1,SG1,SG301,301,0,[],Flex,,,150</CompressedSegment>
</CompressedSegmentList>
<CompressedSegmentList>
<CompressedSegment>DEL,MAA,28/11/2014-17:55,28/11/2014-22:20,SG1,SG1,SG219,219,0,[{PNQ,28/11/2014-20:05,28/11/2014-20:40,35},{RND,28/11/2014-21:05,28/11/2014-21:40,35}],Flex,,,150</CompressedSegment> </CompressedSegmentList>
<CompressedSegmentList>
<CompressedSegment>DEL,MAA,28/11/2014-17:55,28/11/2014-22:20,SG1,SG1,SG219,219,0,[{PNQ,,,}],Flex,,,150</CompressedSegment> </CompressedSegmentList>
<CompressedSegmentList>
<CompressedSegment>DEL,BLR,28/11/2014-06:05,,SG1,SG1,SG501,501,0,[],Flex,,,150</CompressedSegment> <CompressedSegment>BLR,MAA,,28/11/2014-12:20,SG1,SG1,SG3302,302,0,[],Flex,,,150</CompressedSegment> </CompressedSegmentList>
|