For those using the "add to calendar" with "ics" formatted calendar events:
(1) yes, this works with Google Calendar. Save the "ics" file to your local disk (your desktop, whatever), and then in Google Calendar just go to the "add" drop-down on the bottom left-hand side of the calendar, and select "Import Calendar". Select the "ics" file you saved and import this into your calendar.
(2) and, yes, if you have a round-trip or multi-destination trip -- with the same confirmation number -- after adding the first "ics" file, adding the second "ics" file will delete the first one. (Technically, adding the second "ics" file *updates* the first one.) That's because the UID in the ics files is the confirmation number; that is, in the two "ics" files, they have the same UID.
This is not too difficult to fix, however:
* save all "ics" files for your trip to your local disk,
* open them with a text editor, and
* append to the UID the number for the leg of your trip; e.g., append "1" for the outbound trip, and "2" for the return trip (and "3" if it's a multi-destination trip with the same conf number).
For example, going from "HERE" to "THERE", the "ics" files will be named "HERE_to_THERE.ics" and "THERE_to_HERE.ics". But the UID in *both* files is "X1ABCD" (it should be unique in each file). So, just edit:
* "HERE_to_THERE.ics" from "UID:X1ABCD" to "UID:X1ABCD1", and
* "THERE_to_HERE.ics" from "UID:X1ABCD" to "UID:X1ABCD2"
Now, they are imported as unique events....
(3) and, finally, yes, SW, you can create a "add to Google Calendar" link and bypass the ics file altogether...
Cheers,
Michael
... View more