A small update, this adds the ability to cope with some common miscodings of callsigns when searching for routes:
1) Callsigns that have leading zeros added to the start of the flight number (e.g. BAW001 instead of BAW1).
2) Callsigns where the IATA code was entered instead of the ICAO code (e.g. VS1 instead of VIR1).
It also adds support for searching for routes against all of the ICAOs for an airline, but only if the flight number in the callsign is numeric. So given the example of GEC (Lufthansa Cargo, IATA LH) and DLH (Lufthansa, IATA LH), if GEC123 cannot be found then it will search for a route against DLH123, but if GEC1XY cannot be found then it will not search for a route against DLH1XY.
New releases will be announced here.
1 post • Page 1 of 1