Feature: Airline lookup by callsign

[WeegeeNumbuh1]

Adds new airline lookup by callsign with the associated UI changes. Uses the operators.js file that's already part of tar1090-db that gets pulled when running the install script, so no need for additional databases or files.

---

Pics first

Adds to the infoblock and also has a tooltip with the country and telephonic name
Adds new column to the table
Also does the same tooltip thing like how the route column does it
Also available in the hoverbox thing
Disabled by default in defaults.js

---

operators.js limitations as of this post

Important

See this comparison table.

tl;dr it needed a lot of cleanup so I'm using my own database to get cleaner looking names.

off-topic ramblings

Maybe my database can be integrated into tar1090-db? Because imho the names used in the operators file looks like a set of basic filters and formatting was only applied to the FAA file.

oof

---

Additional features

• Handles "registration being used as callsign" conflicts (e.x. callsign = RPC123 vs. reg = RP-C123).

Known limitations and things I didn't test

• IATA prefixes won't be handled (usually seen with ADS-C)
• Special prefixes >3 characters are also not handled
• How this affects the history feature is unknown (I don't use this feature)
  • pTracks works fine so the history feature probably is fine too
• Unknown to what extent these changes would affect aggregators that already have some kind of airline matching present if this gets merged and they rebase their forks
• The extent of which the lookup affects client-side performance is not precisely quantified, especially at the scale of aggregators, but so far with my setup that usually handles about 300 aircraft at a time I see no perceptible changes
• Existing installs will probably have to add the airline feature flag manually to their existing configs if this gets merged
  • Updating if/once this is merged won't break things since defaults.js has all the added elements to handle this feature

Things that probably could be added later

• Adding airline name to the labels?
  • It's already crowded when the route feature is enabled
  • Probably can be displayed when pressing the 'O' button
• Filtering by airline
  • Can already be done just by the callsign prefix
• Further UI tweaks

Why this feature?

I got tired of seeing airline prefixes I didn't recognize and having to look them up manually in my own database, plus, I already figured out how to do callsign to airline matching with my other project, so it made sense to add the feature to tar1090. Also, I didn't see anyone else suggesting or adding a feature like this so I went ahead and did it.

Other things

First PR ever; I don't really know all the conventions with git/GitHub/branching and all that, all my own repos I just yolo it and commit to main/master lmao. Hopefully this PR is good.

[wiedehopf]

not sure when i'll have time to look at this.

no worries about the PR, looks fine.

This has been requested, i've been saying it's not necessary :P
But with a PR i'll look at it.

Wanted to use the data from Mictronics but if it's bad we can use your data and put it into tar1090-db i guess.
Though i don't really want to maintain any DB itself, tar1090-db just pulls data from other places.

[WeegeeNumbuh1]

Oh yeah no rush, hopefully someone else sees this PR and tries these changes before merging.

Maybe I can reach out to Mictronics about the airlines names so that tar1090-db doesn't have to change its sources, though I will mention that my airlines database might have differing naming priorities compared to what's being used now.