very nice! thank you.

how can one see (from the homepage? didn't see an option) other users' flights? I only see the recently added ones or after login, just my own.

prefers1a: For Flightmemory imports, the previous version only supported matching by IATA code, but I've added rudimentary support for ICAO codes and custom airports today. Add the airport first, making sure to use the same airport name as your FlightMemory log, and then try importing again.

MuAT: There is no full public index of other users (yet?), but the basic format is always "openflights.org/user/username" (eg. http://openflights.org/user/jpatokal). "Top 10" lists of the most active users can be found at http://openflights.org/about.html ; if the user's name is not linked, it means their map is private.

Autocompletion implemented for airports, airlines
 

In celebration of the Day of the Turkey, that famously flightless bird, I've rolled out a new version of OpenFlights with the flight editor interface almost totally rebuilt. Basically, everything (airports, airlines, planes) can now be entered through autocompletion: type in "SIN" and pause for a second, and it will suggest Singapore-Changi (SIN), Singapore-Seletar (XSP), Singkep-Dabo (SIQ) in a dropdown box, from where you can pick the one you meant. Alternatively, punch in "SIN" without pausing, and it'll pick the most likely option and expand it for you automatically.

This all required lots of jiggling about behind the scenes and some pretty darn complex database magic, so I'm very interested in hearing not only about out-and-out bugs, but also any cases where it doesn't Do The Right Thing(TM) automatically: is it missing the obvious airport for "Bar", or suggesting way too many obscure Zambian landing strips for "Foo"? Drop me a line.

Error in Importing flightmemory data
 

Hi, I was just reviewing my flight data and noticed a few things:

Several flights were imported from flightmemory without the airline name (but the airline code).

In one case, aparently there must be an erroneous linebreak somewhere.

For my flight on 01.01.1980 from FRA-ZAG it lists as flight number RK36. On flightmemory, this flight is (correctly) listed as GDA-CDG on 24.04.1980 (two lines below the FRA-ZAG flight, which has no flight number). Before I go on inputing my data, I'd like you to check the import process, to see if there are other missmatches.

I'm forwarding this together with all the flightmemory html to your e-mail address.

prefers1a: Fixed, there was a little bug for handling flights that did not have an airline. Your flight record is impressively complicated, I think I'll start using it as a test case from now on :D

Impressively complicated? The only complicated thing are the airline codes of airlines which don't exist anymore (i.e. RK) - otherwise, the last time I checked, almost all airports still are served (well, LH does not fly to MLW with a 707 anymore, but that is a different case). ;)

This is getting better and better!

I have two suggestions:

- Would it be possible to have fields to enter departure and arrival time?
- I would prefer flights to be sorted descendingly by default, i.e. the last flights at the top, and my 1993 flights at the bottom. The way it is now, if I want to change something on a recent flight, I always have to scroll all the way to the bottom...

CSV import/export
 

Today's new feature: CSV import/export. This means you can backup your OpenFlights, edit them in Excel or any other standard spreadsheet, and import it right back -- or import data from anywhere else suitable. (See specification.) Settings->Backup to save all your flights, or List flights->Export to save the currently filtered selection.

And prefers1a, I just meant that your record is very varied -- some flights have airline name and code, some have only the code, some only the name, etc. Makes for a great test case :D

This was the very first feature request ever recorded! But the reason it hasn't been done is that calculating durations from departure/arrival times requires knowing airport time zones, and that gets quite complicated quite fast (esp. with daylight savings time and whatnot).

Hmm, there's an idea, will probably implement that tomorrow. As workaround, though, you can set the filter to 2008, or click the sorting icons above "Date" in the List flights view to flip the order.

Have you seen http://www.earthtools.org/webservices.htm#timezone ? Not perfect for DST yet, though.

What about allowing times to be entered now, but not base the duration calculation on it? At least this way I could get on with entering departure and arrival times while I go along...

I was entering some flights today and it seemed rather sluggish on the auto-complete. And if I tab out of the field it seems to never complete and won't let me add the flight as it never resolved the airport. Perhaps a jscript call to force it to try to resolve the airport when the submit is clicked would solve the problem??

Also, I noticed when adding a number of trips today that it has a habit of not defaulting to the trip name that was just added. I had to go back and fix a few entries because of that.

From the CSV spec:

5. Airline
Airline name. Mandatory if "Flight Number" with airline code or "Airline_Code" is not provided. Looked up from database if "Flight Number" or "Airline_Code" provides airline code.

Just to make sure I understand correctly...can I use airline_code (instead of airline name) for this data element?

Rolled out a slew of minor changes this morning. Most notably, unknown airline are now permitted, so if you leave the field blank, OpenFlights will just shrug its virtual shoulders and call it "Unknown".

SmilingBoy: Flights are now sorted newest up top. I'll see what I can do about the arrival and departure times. And thanks for the earthtools tip, that looks so much easier than attempting to parse the raw DAFIF timezone file. ^

sbm12: Autocomplete has now been sped up considerably with two hacks: airports you've already been to are looked up locally, no need to touch network/DB, and duplicate autocomplete searches have been nuked. And yes, the new trip handling was buggy :o, it should be fixed now.

CVO 1K 2 Million: The "_Code" fields referred to the internal OpenFlights IDs like "3456", not IATA/ICAO codes; they're now renamed as "_OID" to make this a bit more clear, and I've attempted to clarify the spec a bit. Anyway, you can place airline codes in the "Flight_Number" field, but not the "Airline" field (which is for the full name only). And please don't hesitate to PM me if you run into any issues, the CSV import/export and its format is still somewhat experimental.

Thanks! ^

I think I found another small bug. I usually replace the duration with the actual duration. However, when I click on "edit flight" in the list of flights, the duration gets overwritten with the Openflights calculated duration.

Fixed! (For the second time, actually, it just broke again with the recent autocompletion changes.)

And the new feature of the day is Basic mode, which strips flight entry to the essentials: from where, to where, when and (optional) what airline. You can also enter up to four flights simultaneously this way, which speeds up entry considerably if you're not concerned with planespotting trivia. Click on Basic/Detailed in "Add flights" to toggle between the two, or set your default mode under "Settings". Comments and bug reports welcome!