While I’m very happy with your ability to share my trips with my friends, and I appreciate the semi-annual personal report, I need to share something with you.

I’m never going on a trip to Delta, Canada.

I’m also never going to visit Virgin, UT. Nothing against Utah (I’ve been there and many parts are quite lovely) but it’s just not on my list of places to go.

In fact, I’m willing to bet that of all the people who’ve ever emailed their confirmations from Delta or Virgin America to trips@dopplr.com, hoping that your automated parser would figure out their destinations, none of them have ever actually been headed to either of those places.

Maybe Nokia can help you figure out how to tune that parser, eh?

Sincerely

Baffled in Boston

Tripit’s mechanism for adding trips is superior. The ability to simply forward (or even set an automatic rule to forward) confirmation emails is a major step forward . . . Where TripIt seems better at pulling data in, Dopplr seems to be better so far at pushing their data out, or letting people pull it into other contexts.

Well, now Dopplr’s gone and added some new import mechanisms of their own. This post from the Dopplr blog (ok, it was posted back on July 8th, but it has been sitting in my queue to write about) lays out three new options: Twitter, SMS, and Email:

Today I’m really happy to say we’re taking the wraps off a number of new ways to get your future into Dopplr and share your travel information with those you trust: Dopplr by Twitter, SMS and… Email!

Although I love twitter as a notification service (a way of letting me know something relevant happened) I don’t see myself using it as a data input service. For those of you who would like to, just follow the dopplr user and send direct messages with your trips, like: d dopplr a trip to London July 28th to August 3rd. (Nicely, it also happily accepts @dopplr posts, in case you want to announce your trips as well as put them in dopplr). SMS is another option – you associate your SMS number with your Dopplr account and you can text message the same types of messages to Dopplr’s number.

Finally, they’ve got email working at trips@dopplr.com (wonder how many people will confuse plans@tripit.com with trips@dopplr.com – did they make plans@dopplr.com an alias?).

Interestingly, you can use the same kind of shorthand messages used for Twitter or SMS – “a trip to London July 28th to August 3rd” – or you can forward confirmation messages from booking services (which is how TripIt handles import). This is because Dopplr did not set out to parse all the complex formats used by different agencies, but took a simper approach, as explained by MattB:

There are an awful lot of ways to format a travel itinerary. When people asked us to extract trips from emails, we looked at our long history of e-tickets, confirmations and reservations, and scratched our heads.

Inspiration came in the shape of Apple’s last OS X release, Leopard, and an intriguing feature called “Data detectors“.

We realised that instead of creating a piece of code to decode every email format out there, we could look for patterns of dates and place names in the text (and later, other information too) and turn those into trips.

A happy side-effect of this approach is that as well as extracting information from automatic reservation emails, it works well with short text strings like “I’ll be in San Francisco from 3rd July to 7th July”. This means we can work with many hand-written emails, with Twitters, and with SMSes too.

Of course it won’t work with every variation under the sun (for example, it’s most reliable when an email contains just a return trip in a single hop), but we’ve had very satisfying results in our testing. And of course every email you send us will be added to our test suite so that our engine can get better and better over time.

In other words, rather than specifically targeting all the different potential formats, and parsing them in some structured way, Dopplr looks for some specific patterns in the text and tries to understand their meaning without knowing the format of the email in advance.

I wonder how different this is from what TripIt actually does behind the scenes – how much they plan for specific formats they know in advance – and how successful it will be “in the field.” For now it is enough to convince me to turn off my automated importing and give trips@dopplr.com a try on my next few confirm messages. Then, I can automate a rule in my email such that travel confirmations get auto-forwarded to both plans@tripit.com and trips@dopplr.com, and be sharing my travel plans painlessly.

It’s basically a roll-your-own lifestream, though for now at least it isn’t integrated to anyone else’s streams, as in Friendfeed or Socialthing.

This morning I posted a new plugin which picks up TripIt Activity Streams.

TripIt’s activity stream is a private Atom feed which posts an item whenever you begin a trip, complete a trip, or start planning a trip. For example, here’s a recent entry from my feed:

You can download the plugin from the MTAS page.

In my ideal world, the act of forwarding a travel confirmation to TripIt, which establishes a trip, would also create the same trip in Dopplr, which my Dopplr badge, news feed on Facebook, Fire Eagle account, and lifestream would then share with the public, abstracting the details of flights and hotels and such. (Not that I’m terribly worried one could discover them, but just to simplify as Dopplr does well, so that only those who actually want to connect need to get to the details).

That possible crept a bit closer as Dopplr announced the ability to subscribe to your Google Calendar and learn your trips from it.

For some time, Dopplr has been able to export trips to calendars; TripIt can also adds trips to a calendar, but does so in a much more precise fashion, actually adding the flight info and such.

[Update: I had originally posted that the format Dopplr expects is different enough from the one TripIt produces that the two cannot be linked. I was wrong - they can be.]

To link your TripIt account to your Dopplr account, log in to TripIt and locate your iCal feed on your “MyTrips” page (click on the green ICAL feed icon):

Then, log in to Dopplr, go to “Your Account” and choose “Import trips from external calendars.”

Paste in the address of your TripIt iCal feed and Voila! – automated import of TripIt trips into Dopplr.

The logic is smart enough to notice where you already have trips, and not double book you in Dopplr.

Very cool. Now all I need is an Action Stream plugin for Movable Type which notes actual travel segments, so that I can add “John flew from Boston to Austin” to a day like today on JohnEckman.com. I suppose I could write one that checks the iCal feed from TripIt once or twice a day, and creates an action only when the travel date matches today’s date?