No departure/destination information is read from ADSBEx data. Route information is only looked up based on call sign from OpenSky.
Suggested Solution
ADSBEx seems now to deliver from/to information when known, see this example:
{"postime":"1642859891871","icao":"4B8750","reg":"TC-AZP","type":"B738","wtc":"2","spd":"11.2","altt":"0","alt":"","galt":"","talt":"","lat":"53.360138","lon":"-2.278309","vsit":"0","vsi":"","trkh":"1","ttrk":"","trak":"177.2","sqk":"5262","call":"PGT83N","gnd":"1","trt":"5","pos":"1","mlat":"0","tisb":"0","sat":"0","opicao":"PGT","cou":"Turkey","mil":"0","interested":"0","from":"MAN Manchester United Kingdom","to":"SAW Sabiha G\u00f6k\u00e7en Istanbul Turkey","dst":"0.16"}
It contains "from":"MAN Manchester United Kingdom","to":"SAW Sabiha G\u00f6k\u00e7en Istanbul Turkey" towards the end.
This is unfortunately not the 4-letter ICAO airport codes we receive from OpenSky, but is better than nothing and should be used somehow, ideally only if OpenSky doesn't return anything. Maybe it can just be read and stored, verifying that the OpenSky request is sent nonetheless and overwrites in case it returns something.
Note: Watch the fact that it includes Unicode characters.
Current Situation / Problem
No departure/destination information is read from ADSBEx data. Route information is only looked up based on call sign from OpenSky.
Suggested Solution
ADSBEx seems now to deliver from/to information when known, see this example:
It contains
"from":"MAN Manchester United Kingdom","to":"SAW Sabiha G\u00f6k\u00e7en Istanbul Turkey"towards the end.This is unfortunately not the 4-letter ICAO airport codes we receive from OpenSky, but is better than nothing and should be used somehow, ideally only if OpenSky doesn't return anything. Maybe it can just be read and stored, verifying that the OpenSky request is sent nonetheless and overwrites in case it returns something.
Note: Watch the fact that it includes Unicode characters.
Additional context
Found while analysing data for #223.