Next step... get it to map the ADS-B broadcast ICAO callsign and the IATA flight number. At the airport you'll see the IATA number but in the ADS-B you'll have

Next step... get it to map the ADS-B broadcast ICAO callsign and the IATA flight number. At the airport you'll see the IATA number but in the ADS-B you'll have ICAO. In his example it says: Flight TAP1369... Flight TAP23NP... Flight TAP1691... Flight RZO134... TAP1369 (ICAO) is TP1369 (IATA); similar for TAP1691 (ICAO) and TP1691 (IATA). But TAP23NP (ICAO) is TP1823 (IATA) and RZO134 (ICAO) is S4 134 (IATA). What's broadcast in ADS-B is very often very different from what's shown at the airport and not what someone would recognize. Doing this mapping is a pain. The OP is using OpenSky Network who say: callsign This column contains the callsign that was broadcast by the aircraft. Most airlines indicate the airline and the flight number in the callsign, but there is no unified system. In our example, the callsign indicates that this state vector belongs to UPS flight 858. By looking up the flightnumber on services like flightaware.com, you’ll find out that this flight goes from Lousville to Phoenix every day. i.e. go look this data up elsewhere. I asked ChatGPT: Write me some JavaScript that can map an ICAO callsign broadcast by ADS-B to an IATA flight number for the same flight. Mapping an ICAO callsign broadcast by ADS-B to an IATA flight number is a complex task that typically requires access to a comprehensive aviation database. Such databases are often provided by aviation data providers and may not be freely available. However, I can provide you with a simplified example of how you might approach this task if you had access to the necessary data.