SmilingBoy: Basel/Mulhouse/Freiburg is such a strange duck that it's not worth rejigging the whole database structure to accommodate it. I think what you're done is fine: MLH is now the "main" entry (with the ICAO code), and BSL is another airport that just happens to be in the same place.

I've just implemented the idea of "airline aliases", which works around some of the most common FlightMemory<->OpenFlights naming discrepancies, and eg. SAS Scandinavian and SN Brussels flights should now import correctly.

Airline history, like SN representing Sabena, SN Brussels and Brussels at various points in time, gets really complicated. For imports, there isn't really a practical way to differentiate these: it will use the code, and that code maps to current airline using it, in this case Brussels. The option to add new airlines, incl. historical ones, and assign your flights to them is in the works though.

apoivre: To add an IATA code to an existing DAFIF airport, you need to [Load] it into the editor, add the IATA code and city name, then save it. The new, saved copy goes into the OpenFlights DB, which can then be used for your flights.

tfung: Anybody's map will look a little messy with almost 1000 flights all over the world. But I've slimmed down the flight paths for frequently flown routes a bit. Great Circle routes are on the to-do list, but the rendering math involved gets pretty complicated pretty fast.