Generate Travel iCalendar File

This form generates an iCalendar-format file describing travel from one place to another, paying particular attention to getting the timezones right.

For example, you say you're flying from "Seattle" in "United States", and it allows you to choose which American timezone that's in ("America/Los_Angeles" is the right answer here). And you're flying to "Wellington" in "New Zealand" (which automatically selects "Pacific/Auckland" as the timezone). Put in a date and a time for each, and it generates an iCal-formatted file for an appointment called "Seattle to Wellington" that you can import into your calendar software.

Times and dates are parsed semi-intelligently. I didn't write the code that does that, so I don't know precisely what it does. The following kind of things seem to work:

Place (optional) Country Timezone Date and Time
Description (optional):

You may need to experiment with the following options to get something that works:

Convert timezones to UTC

This converts the times to UTC, aka Zulu Time, aka Greenwich Mean Time. This bypasses the whole timezone mess, making it absolutely clear precisely which point in time you mean and making it much harder for your calendar software to screw things up. This is probably what you want, and is the default.

Strip zone information from times

This leaves the time "floating" free of any timezone information at all. That is, 15:00 means 3PM in whichever timezone you happen to be in when the alarm goes off. If your calendar software doesn't munge everything around when you change timezones, this is the best option.

Keep timezones as they are

This leaves the times and timezones exactly as you specified. This means your calendar software needs to understand the timezones involved in order to correctly display the appointment. Since your calendar software may very well never have heard of "Kwajalein time", that means the generated file has to wrap up all the information about how they tell the time in Kwajalein, including daylight savings shifts and so on. Your calendar software which, like all calendar software, is crap, will almost certainly choke on this, so it is probably not what you want. However, if the Marshall Islands pass a law six days before you leave moving daylight savings time a week early, and your calendar software is particularly clever, it could make the difference between catching and missing your flight.

Adjust arrival timezone to match departure timezone

This converts the arrival time into the timezone of the place of departure. So if you take off at 3PM from New York and land in Los Angeles at 6PM, the arrival time is recorded as 9PM New York time. This is the best option if your software can cope with timezones, but chokes if the start time has a different timezone from the end time.

Adjust departure timezone to match arrival timezone

This converts the departure time into the timezone of the place of arrival. In the above example, the departure time would be adjusted to 12PM Los Angeles time. Personally, I can't imagine why I would want this, but it's a natural counterpart to the above option, and so it's easier to leave it in than take it out.