Author
Topic: Logos (Read 115163 times)

To try to avoid problems with the forum slowing down, this seems like a good time to start a new logos thread - I've locked the old one now, but you can stll download the logos from there - it finished with a zip so that folk can easily keep up to date.

Here's a reminder of the logic currently used to decide which logo is displayed, as given in the first post of the earlier thread.

-------------------------------------------

1 - If the Flight ID is blank or just numeric, no logo.

2 - If the Flight ID is the same as the Registration (with spaces, dashesetc removed), find a logo file to match. This means that if, for example,the flight ID for G-WXYZ is GWXYZ, it will display GWXYZ.bmp. If there is nomatching logo file, show a blank.

3 - If the flight ID starts with three or more letters, find a logo filethat matches all those letters. This means that if the Flight ID is TARTAN2,it will display TARTAN.bmp. If the Flight ID is TAR123, it will displayTAR.bmp. If there is no matching logo file, show a blank.

4 - If the Flight ID starts with two letters, or either of the first twocharacters is a letter, look up the two characters in the IATA code (C2)field of the Airlines table of NavData.db3. Find the corresponding ICAO code(C3 in the Airlines table) and find the matching logo file. If there is nomatch in the table, or no matching logo file, show a blank.

WHAT THIS MEANS FOR US.

Point 2 - we can create logos for individual aircraft that use theirRegistrations as Flight IDs.

Point 3 - we can create logos for missions such as REACH, and we won't getAer Arann showing up instead!

Point 4 -we need to update the Airlines table in NavData.db3. A lot of thedata there is old, it doesn't have the latest airlines, and, because so manyaircraft use unofficial two-letter codes instead of their official IATAtwo-letter codes, we can edit the table to suit ourselves.