FlightXML2 Web Services calling GetFlightID returns exception


#1

When we call the GetFlightID method in your service with the following parameters, as an example, an exception is returned:

client.GetFlightID(“UA198”, 1511872200)

Why is this returning an exception? Is the date okay, as it works with other calls? We have many calls failing.

Exception returned from service call:
End element ‘Fault’ from namespace ‘http://schemas.xmlsoap.org/soap/envelope/’ expected. Found element ‘SOAP-ENV:detail’ from namespace ‘http://schemas.xmlsoap.org/soap/envelope/’. Line 2, position 357.

Can you reply asap with anymore information you need to help solve this issue?

Regards,
Pal


#2

Additional exception information:
System.ServiceModel.CommunicationException

Server returned an invalid SOAP Fault. Please see InnerException for more details. Server stack trace: at System.ServiceModel.Channels.MessageFault.CreateFault(Message message, Int32 maxBufferSize) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrownat [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HCModel.Model.FlightXML2.FlightXML2Soap.GetFlightID(GetFlightIDRequest request) at HCModel.Model.FlightXML2.FlightXML2SoapClient.HCModel.Model.FlightXML2.FlightXML2Soap.GetFlightID(GetFlightIDRequest request) at HCModel.Model.FlightXML2.FlightXML2SoapClient.GetFlightID(String ident, Int32 departureTime) at HCModel.Model.FlightAware.GetFaFlightId(String FlightNo, DateTime departureTime, Int32 buyerId, Int32 userId)


#3

The timestamp you are specifying translates to “Tue Nov 28 12:30:00 UTC 2017”

However, the scheduled departure time of that flight is 12:30PM PST, so you are likely converting timestamps incorrectly. If you use 1511901000 (Tue Nov 28 20:30:00 UTC 2017), it should work correctly. I also recommend using the ICAO identifier for the airline “UAL” rather than “UA”

The equivalent request in REST/JSON is this, and it works:

https://flightxml.flightaware.com/json/FlightXML2/GetFlightID?ident=UAL198&departureTime=1511901000


#4

Thanks for quick response, will look into it tomorrow and get back to you.

Thanks again,
Pal


#5

I’m getting no result found for the following flight: JBU1980 on the 20 May 2018 14:59 PDT. I’m sending the following request but it returns no results:

@flightxml.flightaware.com/json/FlightXML2/GetFlightID?ident=JBU1980&departureTime=1526853540

is this correct format for the depature time?


#6

I’ve managed to find the flight via the scheduled take off time (15:09) instead of the scheduled departure time (14:59). Looking at past data for JBU1980 the FiledDepartureTime changes between 15:09 to 14:59, is this normal behaviour? Below are some results I found:

2018-05-20 15:09:00.000
2018-05-18 14:59:00.000
2018-05-17 14:59:00.000
2018-05-16 14:59:00.000
2018-05-15 14:59:00.000
2018-05-14 14:59:00.000
2018-05-13 14:59:00.000
2018-05-12 14:59:00.000
2018-05-11 14:59:00.000
2018-05-10 14:59:00.000
2018-05-09 14:59:00.000
2018-05-08 14:59:00.000
2018-05-07 14:59:00.000
2018-05-06 14:59:00.000
2018-05-05 14:59:00.000
2018-05-04 14:59:00.000
2018-05-03 14:59:00.000
2018-05-02 14:59:00.000
2018-05-01 17:58:58.000
2018-05-01 15:09:00.000
2018-04-30 15:09:00.000
2018-04-29 15:09:00.000
2018-04-28 15:09:00.000
2018-04-27 15:09:00.000
2018-04-26 15:09:00.000
2018-04-25 15:09:00.000
2018-04-24 15:09:00.000
2018-04-23 15:09:00.000
2018-04-22 15:09:00.000
2018-04-21 15:09:00.000
2018-04-20 15:09:00.000
2018-04-19 15:09:00.000
2018-04-18 15:09:00.000
2018-04-17 15:09:00.000
2018-04-16 15:09:00.000
2018-04-15 15:09:00.000
2018-04-14 15:09:00.000
2018-04-13 15:09:00.000
2018-04-12 15:09:00.000
2018-04-11 15:09:00.000
2018-04-10 15:09:00.000
2018-04-09 15:09:00.000
2018-04-08 15:09:00.000
2018-04-07 15:09:00.000
2018-04-06 15:09:00.000
2018-04-05 15:09:00.000
2018-04-04 15:09:00.000
2018-04-03 15:09:00.000
2018-04-02 15:09:00.000
2018-04-01 15:09:00.000
2018-03-31 15:09:00.000
2018-03-30 15:09:00.000


#7

Here is the JSON for the flight, why is the departure time on the first example showing the filed departure time with the take off value but the second is using the departure time?:

First example using take off time

{
“FlightInfoStatusResult”: {
“next_offset”: -1,
“flights”: [
{
“ident”: “JBU1980”,
“faFlightID”: “JBU1980-1526621170-airline-0322”,
“airline”: “JBU”,
“airline_iata”: “B6”,
“flightnumber”: “1980”,
“tailnumber”: “N625JB”,
“type”: “Form_Airline”,
“codeshares”: “HAL2366”,
“blocked”: false,
“diverted”: false,
“cancelled”: false,
“origin”: {
“code”: “KLGB”,
“city”: “Long Beach, CA”,
“alternate_ident”: “LGB”,
“airport_name”: “Daugherty Field”
},
“destination”: {
“code”: “KLAS”,
“city”: “Las Vegas, NV”,
“alternate_ident”: “LAS”,
“airport_name”: “McCarran Intl”
},
“filed_ete”: 3660,
“route”: “ZOOMM1 MISEN KEPEC6”,
“filed_altitude”: 270,
“display_filed_altitude”: “27,000 feet”,
“filed_airspeed_kts”: 440,
“distance_filed”: 306,
“filed_departure_time”: {
“epoch”: 1526854140,
“tz”: “PDT”,
“dow”: “Sunday”,
“time”: “15:09”,
“date”: “05/20/2018”,
“localtime”: 1526828940
},
“estimated_departure_time”: {
“epoch”: 1526857380,
“tz”: “PDT”,
“dow”: “Sunday”,
“time”: “16:03”,
“date”: “05/20/2018”,
“localtime”: 1526832180
},
“actual_departure_time”: {
“epoch”: 1526857365,
“tz”: “PDT”,
“dow”: “Sunday”,
“time”: “16:02”,
“date”: “05/20/2018”,
“localtime”: 1526832165
},
“departure_delay”: 1440,
“filed_arrival_time”: {
“epoch”: 1526857800,
“tz”: “PDT”,
“dow”: “Sunday”,
“time”: “16:10”,
“date”: “05/20/2018”,
“localtime”: 1526832600
},
“estimated_arrival_time”: {
“epoch”: 1526860320,
“tz”: “PDT”,
“dow”: “Sunday”,
“time”: “16:52”,
“date”: “05/20/2018”,
“localtime”: 1526835120
},
“actual_arrival_time”: {
“epoch”: 0
},
“arrival_delay”: 3420,
“status”: “En Route / Delayed”,
“progress_percent”: 10,
“aircrafttype”: “A320”,
“full_aircrafttype”: “A320”,
“inbound_faFlightID”: “JBU1625-1526621170-airline-0502”,
“adhoc”: false
}
]
}
}

Second Example using departure time
{
“FlightInfoStatusResult”: {
“next_offset”: -1,
“flights”: [
{
“ident”: “JBU1980”,
“faFlightID”: “JBU1980-1526448337-airline-0021”,
“airline”: “JBU”,
“airline_iata”: “B6”,
“flightnumber”: “1980”,
“tailnumber”: “N504JB”,
“type”: “Form_Airline”,
“codeshares”: “HAL2366”,
“blocked”: false,
“diverted”: false,
“cancelled”: false,
“origin”: {
“code”: “KLGB”,
“city”: “Long Beach, CA”,
“alternate_ident”: “LGB”,
“airport_name”: “Daugherty Field”
},
“destination”: {
“code”: “KLAS”,
“city”: “Las Vegas, NV”,
“alternate_ident”: “LAS”,
“airport_name”: “McCarran Intl”
},
“filed_ete”: 4800,
“route”: “ZOOMM1 MISEN KEPEC6”,
“filed_altitude”: 270,
“display_filed_altitude”: “27,000 feet”,
“filed_airspeed_kts”: 440,
“distance_filed”: 231,
“filed_departure_time”: {
“epoch”: 1526680740,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “14:59”,
“date”: “05/18/2018”,
“localtime”: 1526655540
},
“estimated_departure_time”: {
“epoch”: 1526681640,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “15:14”,
“date”: “05/18/2018”,
“localtime”: 1526656440
},
“actual_departure_time”: {
“epoch”: 1526681640,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “15:14”,
“date”: “05/18/2018”,
“localtime”: 1526656440
},
“departure_delay”: -240,
“filed_arrival_time”: {
“epoch”: 1526685540,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “16:19”,
“date”: “05/18/2018”,
“localtime”: 1526660340
},
“estimated_arrival_time”: {
“epoch”: 1526684566,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “16:02”,
“date”: “05/18/2018”,
“localtime”: 1526659366
},
“actual_arrival_time”: {
“epoch”: 1526684566,
“tz”: “PDT”,
“dow”: “Friday”,
“time”: “16:02”,
“date”: “05/18/2018”,
“localtime”: 1526659366
},
“arrival_delay”: -60,
“status”: “Arrived / Gate Arrival”,
“progress_percent”: 100,
“aircrafttype”: “A320”,
“full_aircrafttype”: “A320”,
“inbound_faFlightID”: “JBU1625-1526448337-airline-0271”,
“adhoc”: false
}
]
}
}


#8

If you were searching for the flightid prior to departure, you would have needed to use filed departure time which was departureTime=1526854140. If you were searching for the flightid after departure, you would have needed to use the actual departure time which was departureTime=1526857365


#9

my issue isn’t with the filed and actual departure times its to do with the “filed_departure_time” switching between providing Gate Departure Time and Take off time. Is there a reason why this one field changes between those 2 times?