FlightXML3 - AirportBoards - Uknown Time = -1 instead of 0


#1

Looks like there are some instances where unknown times are getting reported as -1 (along with a miss-translated local time for the evening of epoch-eve, 1969 - see bold in copy/paste below).

In cases like this, I think you probably want {“epoch”:0} to indicate a null or unknown value. Attempts to insert -1 into my database were crashing my app, as the times are being stored as unsigned integers.

{“ident”:“N208QS”,“faFlightID”:“N208QS-1501268283-adhoc-0”,“tailnumber”:“N208QS”,“type”:“General_Aviation”,“blocked”:false,“diverted”:false,“cancelled”:true,“origin”:{“code”:“KMSP”,“city”:“Minneapolis, MN”,“alternate_ident”:"",“airport_name”:“Minneapolis/St Paul Intl”},“destination”:{“code”:"",“city”:"",“alternate_ident”:"",“airport_name”:""},“filed_airspeed_mach”:0,“filed_departure_time”:{“epoch”:1501268283,“tz”:“CDT”,“dow”:“Friday”,“time”:“01:58PM”,“date”:“07/28/2017”,“localtime”:1501250283},“estimated_departure_time”:{“epoch”:1501268283,“tz”:“CDT”,“dow”:“Friday”,“time”:“01:58PM”,“date”:“07/28/2017”,“localtime”:1501250283},"actual_departure_time":{“epoch”:-1,“tz”:“CST”,“dow”:“Wednesday”,“time”:“05:59PM”,“date”:“12/31/1969”,“localtime”:-21601},“departure_delay”:0,“filed_arrival_time”:{“epoch”:0},“estimated_arrival_time”:{“epoch”:-1,“tz”:“UTC”,“dow”:“Wednesday”,“time”:“11:59PM”,“date”:“12/31/1969”,“localtime”:-1},“actual_arrival_time”:{“epoch”:-1,“tz”:“UTC”,“dow”:“Wednesday”,“time”:“11:59PM”,“date”:“12/31/1969”,“localtime”:-1},“status”:“result”,“progress_percent”:100,“aircrafttype”:“CL60”,“full_aircrafttype”:“CL60”,“inbound_faFlightID”:“EJA208-1501169759-12-0-27”,“adhoc”:true}


#2

Thanks I’ve got the bug filed for that. We’re starting to work on some of these FlightXML bugs this week.