Unknow Airports in Push Alerts


#1

Hi Team,
I founded next issue on push alerst - some airports are not named by ICAO code, instead coordinates are sent. This make parsing on my site unavailable, also I am receiving some pushes I am not subscribed for.
Please look at the examples below:

{“long_desc”:“Ryanair #4321 arrived at Krakow Int’l (KRK) at 16:22 CEST from Pula (Pula) after 1:00 en route”,“short_desc”:“RYR4321 arrived at KRK from Pula”,“summary”:“RYR4321 arrived at KRK from Pula”,“eventcode”:“arrival”,“alert_id”:26874970,“flight”:{“ident”:“RYR4321”,“aircrafttype”:“B738”,“origin”:“L 45.04097 13.31608”,“destination”:“EPKK”,“filed_ete”:"",“route”:"",“faFlightID”:“RYR4321-1537449608-ed-0015”,“reg”:“EIFTC”,“filed_altitude”:0,“filed_airspeed_kts”:0,“filed_time”:1537449677,“filed_departuretime”:1537449677,“estimatedarrivaltime”:1537453260,“actualarrivaltime”:1537449677,“actualdeparturetime”:1537449677,“estimated_blockin_time”:1537453860,“filed_blockin_time”:1537453800,“actual_blockin_time”:0,“estimated_blockout_time”:1537447500,“filed_blockout_time”:1537447500,“actual_blockout_time”:1537448400,“filed_arrivaltime”:1537449677}}

{“long_desc”:“SAS / Air Nostrum #751 arrived at Warsaw Frederic Chopin (WAW) at 09:33 CEST from Copenhagen (Copenhagen) after 1:05 en route”,“short_desc”:“ANE751 arrived at WAW from Copenhagen”,“summary”:“ANE751 arrived at WAW from Copenhagen”,“eventcode”:“arrival”,“alert_id”:26874983,“flight”:{“ident”:“ANE751”,“aircrafttype”:“CRJ”,“origin”:“L 55.58812 12.59707”,“destination”:“EPWA”,“filed_ete”:“01:15:00”,“route”:"",“faFlightID”:“SAS97Y-1537719320-ed-0007”,“reg”:“ECMJQ”,“filed_altitude”:0,“filed_airspeed_kts”:289,“filed_time”:1537771658,“filed_departuretime”:1537770580,“estimatedarrivaltime”:1537774980,“actualarrivaltime”:1537774405,“actualdeparturetime”:1537770480,“estimated_blockin_time”:0,“filed_blockin_time”:0,“actual_blockin_time”:0,“estimated_blockout_time”:0,“filed_blockout_time”:0,“actual_blockout_time”:1537769700,“filed_arrivaltime”:1537775080}}

{“long_desc”:“Ryanair #1504 arrived at Leeds Bradford Int’l (LBA) at 15:51 BST from Rostock (Rostock) after 1:23 en route”,“short_desc”:“RYR1504 arrived at LBA from Rostock”,“summary”:“RYR1504 arrived at LBA from Rostock”,“eventcode”:“arrival”,“alert_id”:26874947,“flight”:{“ident”:“RYR1504”,“aircrafttype”:“B738”,“origin”:“L 53.57632 12.95749”,“destination”:“EGNM”,“filed_ete”:"",“route”:"",“faFlightID”:“RYR1504-1537450046-ed-0011”,“reg”:“EIDWW”,“filed_altitude”:0,“filed_airspeed_kts”:0,“filed_time”:1537450088,“filed_departuretime”:1537450058,“estimatedarrivaltime”:1537455060,“actualarrivaltime”:1537455060,“actualdeparturetime”:1537450058,“estimated_blockin_time”:1537455600,“filed_blockin_time”:1537456200,“actual_blockin_time”:1537455660,“estimated_blockout_time”:1537447800,“filed_blockout_time”:1537447800,“actual_blockout_time”:1537447800,“filed_arrivaltime”:1537450058}}


#2

This will normally occur if position-only flights are enabled on your account. This would allow alerts for flights that are discovered in air and may not accurately match with a known airport. in the case of SAS97Y-1537719320-ed-0007 it looks like this is the result of a codeshare where the expected departure message was not associated with the actual flight. We’re taking a closer look at it.

However, the two RyanAir examples are the result of an event that occurred on September 20th and resulted in erroneous alerts and data being generated. The data has since been corrected, but it is not possible to recall anything that was already sent. However, based on alert settings this all appear to match the alert rules set up at the time of delivery.


#3

Please do chek, that I have never enabled Position-Only Flights. I confirm this issue started from 20 SEPT - before I have never received airport as coordinates.

Also - I am still receving “build_json” flights.

{“long_desc”:“Lot - Polskie Linie Lotnicze #3932 arrived at Warsaw Frederic Chopin (WAW) at 16:24 CEST from Szczecin (SZZ)”,“short_desc”:“LOT3932 arrived at WAW from SZZ”,“summary”:“LOT3932 arrived at WAW from SZZ”,“eventcode”:“arrival”,“alert_id”:27203280,“flight”:{“faFlightID”:“LOT3932-1538549700-schedule-0001”,“error”:“Extended details unavailable: build_json_flight_body_v1 could not load details”}}