I’m trying to use AirlineFlightSchedules to verify time of flights in our system but it doesn’t seem to return proper arrival/departure time. Here’s what I found:
Request:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:FlightXML2="http://flightxml.flightaware.com/soap/FlightXML2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<FlightXML2:AirlineFlightSchedulesRequest>
<FlightXML2:startDate>1440968400</FlightXML2:startDate>
<FlightXML2:endDate>1441054799</FlightXML2:endDate>
<FlightXML2:origin>UUWW</FlightXML2:origin>
<FlightXML2:destination>HESH</FlightXML2:destination>
<FlightXML2:airline>TSO</FlightXML2:airline>
<FlightXML2:flightno>851</FlightXML2:flightno>
<FlightXML2:howMany>1</FlightXML2:howMany>
<FlightXML2:offset>0</FlightXML2:offset>
</FlightXML2:AirlineFlightSchedulesRequest>
</env:Body>
</env:Envelope>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:FlightXML2="http://flightxml.flightaware.com/soap/FlightXML2" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Body>
<FlightXML2:AirlineFlightSchedulesResults>
<FlightXML2:AirlineFlightSchedulesResult>
<FlightXML2:next_offset>-1</FlightXML2:next_offset>
<FlightXML2:data>
<FlightXML2:ident>TSO851</FlightXML2:ident>
<FlightXML2:actual_ident />
<FlightXML2:departuretime>1441013400</FlightXML2:departuretime>
<FlightXML2:arrivaltime>1441030500</FlightXML2:arrivaltime>
<FlightXML2:origin>UUWW</FlightXML2:origin>
<FlightXML2:destination>HESH</FlightXML2:destination>
<FlightXML2:aircrafttype>B744</FlightXML2:aircrafttype>
<FlightXML2:meal_service>Business: Meal / Economy: Meal</FlightXML2:meal_service>
<FlightXML2:seats_cabin_first>0</FlightXML2:seats_cabin_first>
<FlightXML2:seats_cabin_business>12</FlightXML2:seats_cabin_business>
<FlightXML2:seats_cabin_coach>510</FlightXML2:seats_cabin_coach>
</FlightXML2:data>
</FlightXML2:AirlineFlightSchedulesResult>
</FlightXML2:AirlineFlightSchedulesResults>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
It says that it departs at 2015-08-31 12:30:00 (Moscow +3) and arrives at 2015-08-31 17:15:00 (Egypt +2).
The correct arrival time for this flight is 16:15.
Could you check it ASAP please?
Thanks, we’re investigating this as internal ticket 53402.
I’m not able to confirm your problem. The arrivaltime epoch timestamp of 1441030500 actually does translate to 16:15:00 EET (or 14:15:00 GMT)
Oh, so you’re giving me time in GMT? Not the local airport time. That explains a lot.
Sorry, but I still don’t get it.
1443864900 => Sat, 03 Oct 2015 09:35:00 GMT => 2015-10-03 12:35:00 +0300 (Moscow)
Actual departure time for this flight is 13:35 +0300 (Moscow) (reference)
You should really check your timezone info. We used to have +4 last year in Moscow. Might be outdated.
https://photos-2.dropbox.com/t/2/AAAOXZ23Qfd8WNr-rM4okIfosyLc2d2vaueGeQkGb5eLBA/12/30442879/png/32x32/1/_/1/2/Screenshot%202015-09-06%2000.36.55.png/EI20-hYYhpgGIAcoBw/nQgD3oOF19MRRzX_b6ppoYBWPmX1tuxqEUBnwVEumQg?size=1280x960&size_mode=2
Request
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:FlightXML2="http://flightxml.flightaware.com/soap/FlightXML2" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<FlightXML2:AirlineFlightSchedulesRequest>
<FlightXML2:startDate>1443819600</FlightXML2:startDate>
<FlightXML2:endDate>1443905999</FlightXML2:endDate>
<FlightXML2:origin>URSS</FlightXML2:origin>
<FlightXML2:destination>UUDD</FlightXML2:destination>
<FlightXML2:airline>TSO</FlightXML2:airline>
<FlightXML2:flightno>2142</FlightXML2:flightno>
<FlightXML2:howMany>1</FlightXML2:howMany>
<FlightXML2:offset>0</FlightXML2:offset>
</FlightXML2:AirlineFlightSchedulesRequest>
</env:Body>
</env:Envelope>
Response
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:FlightXML2="http://flightxml.flightaware.com/soap/FlightXML2">
<SOAP-ENV:Body>
<FlightXML2:AirlineFlightSchedulesResults>
<FlightXML2:AirlineFlightSchedulesResult>
<FlightXML2:next_offset>-1</FlightXML2:next_offset>
<FlightXML2:data>
<FlightXML2:ident>TSO2142</FlightXML2:ident>
<FlightXML2:actual_ident></FlightXML2:actual_ident>
<FlightXML2:departuretime>1443864900</FlightXML2:departuretime>
<FlightXML2:arrivaltime>1443873000</FlightXML2:arrivaltime>
<FlightXML2:origin>URSS</FlightXML2:origin>
<FlightXML2:destination>UUDD</FlightXML2:destination>
<FlightXML2:aircrafttype>B744</FlightXML2:aircrafttype>
<FlightXML2:meal_service>Business: Dinner / Economy: Dinner</FlightXML2:meal_service>
<FlightXML2:seats_cabin_first>0</FlightXML2:seats_cabin_first>
<FlightXML2:seats_cabin_business>12</FlightXML2:seats_cabin_business>
<FlightXML2:seats_cabin_coach>510</FlightXML2:seats_cabin_coach>
</FlightXML2:data>
</FlightXML2:AirlineFlightSchedulesResult>
</FlightXML2:AirlineFlightSchedulesResults>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The image in your last post is not displayable. Can you repost?
There may be cases where times listed on our website can be off because it is using slightly obsolete timezones. However, I believe the timestamps returned by FlightXML should be correct since they are always in UTC and unaffected by timezones. Is that what you are seeing?
Thanks, @bovineone, but I believe that is not the case. The issue is real and actually affects the usage of your API.
Here’s the image that was broken in my previous post: dropbox.com/s/nex8zx33iz6r9 … 7.png?dl=0
My guess is that the information might get broken before you pass it via the API. Maybe, some of your parsers are not performing correctly when accessing the airline’s db.
Could you please look into it, as I have a tool built specifically for your API but cannot use it due to this critical issue?
Thanks!
This issue is still being investigated and researched.
Any updates on this issue? This is a real show-stopper for us.
Dear FlightAware team,
You demonstrate intention to accept payments for your service, but so far you only wasted our developer’s time on integrating your API without any positive outcome as it does not function properly in our case.
I would ask you one more time to investigate the issue and get back to us as soon as you can.
Thank you.
Our flight tracking and flight schedule information consists of data provided to us by multiple providers, who are in turn given data through multiple chains of custody. Identifying, reporting, and getting a corrective action made to a specific data quality concern is time consuming and frustrating for us as well. Unfortunately, the flight areas that you are currently querying are not in one of our primary coverage areas so the amount of data provider redundancy we have to cross-validate our information there is limited at this time. We are continuing to try to cause an improvement in tracking and schedule data for those specific flights, but I cannot provide you with any more specific resolution estimation at this time.
leveltravel, can you recheck your analysis to see if there is any difference to those Russian airports? There have been recent updates to our airport databases that might have improved some of the time handling there.
