I tried the business trip I'm taking next week, and that I just researched on hipmunk earlier today.
"Boston to Tunis to Barcelona"
Big bag of fail. Adioso's trying to send me from "Boston, Texas" to "Barcelona, Venezuela", and finds no matching flights.
Even the simpler search "Boston to Barcelona" is sending me to Venezuela, not Catalonia. It's finding no matching flights.
I tried "Barcelona, Spain", editing the URL to be barcelona-es, barcelona-sp. Nothing worked. Maybe it's a corner case or maybe it's deeper than that, but I figured I'd send along the feedback. I do wish you the best, as airline "exploring" is a right pain in the ass.
Placename disambiguation is something we've wrestled with a lot lately. The way we do it now is: (a) find the most likely origin you meant based on proximity & size; (b) if we have historical data, choose the most likely destination given previous popularity, and (c) whatever the case, give prompts on each one to let you tell us you meant a different one.
Also, we don't currently support multi-city trips, so that would've confused the search parser.
But just running these searches now, they seem to give results:
"Boston to Tunis to Barcelona"
Big bag of fail. Adioso's trying to send me from "Boston, Texas" to "Barcelona, Venezuela", and finds no matching flights.
Even the simpler search "Boston to Barcelona" is sending me to Venezuela, not Catalonia. It's finding no matching flights.
I tried "Barcelona, Spain", editing the URL to be barcelona-es, barcelona-sp. Nothing worked. Maybe it's a corner case or maybe it's deeper than that, but I figured I'd send along the feedback. I do wish you the best, as airline "exploring" is a right pain in the ass.