March 3, 2014
The Tnooz THack event at ITA Google's headquarters in Boston was a lesson in how overwhelming development for the travel industry can be. On the morning of the first day of the hackathon, the eleven API hosts provided brief descriptions of their APIs and their respective functionality or access to data. It became clear, very quickly, that most of the APIs were not like the Twitter API or Google Maps API. Many of the APIs delivered a lot of complex data in a highly structured format. Building some kind of mash-up using any of the APIs would be a challenge.
Planning a trip, whether just down the road or into the next city, normally revolves around the distance of the desired location. It's common practice to search for the distance between two points on a map, then take a rough guess as to how long it will actually take to get there. But we all know that distance isn't the only factor to consider. What about mode of transport, peak traffic hours or alternate routes? All these can dramatically affect how long it actually takes to get to your destination. This post will discuss how iGeolise's Travel Time and the Travel Time API changes the way people search and the results that are produced.
Have you had to pick someone up from the airport only to end-up doing several laps of the airport because the flight was late? This sort of setback due to arrival delays is one of those modern day inconveniences that FlightCaster and their FlightCaster API hope to eliminate.