A significant challenge for Rome2rio’s development team revolves around the manner in which we recognise and treat political boundaries and borders, so that search results and drive overlays do not return unrealistic travel options. We often get feedback from our users on this topic: search results such as the one below, Melbourne to Tel Aviv, demonstrate why. We correctly offer the option of flying into Amman, Jordan and then using a combination of buses and taxis to continue the trip to Tel Aviv, crossing the border at the King Hussein (or Allenby, depending on which side you approach it from) Bridge. Hmmm… while this route is certainly possible, it is perhaps not a journey many travelers would be willing to take. Israeli citizens, in fact, are not permitted to use the border crossing station at Allenby, so this route is simply not an option for them.
Technically correct, but practically unlikely for most travelers.
Another example of this dilemma is the US-Mexico border. A search for journey options from Rosarito to San Diego suggests that a taxi will make the trip in just under an hour. Well, yes, but then again perhaps not. Even if a taxi were allowed to pass—it wouldn’t be—it would spend a couple of hours waiting to cross the border, no matter what time of day. So our result fails on a couple of scores. While the algorithm has produced a “perfect” result, we sadly live in an imperfect, complicated world, where perfect is not always useful.
A pity about the San Ysidro Border Crossing…
We are committed to improving Rome2rio’s methodology so that in cases where political or geographical boundaries make certain results impractical, those results are minimized or eliminated. While we continue to perfect our methodology we appreciate any feedback pointing to results that are less than ideal: if you’re aware of a Rome2rio search result that is practically challenging (or just plain impossible), let us know.