Journey Plans Made Smarter With Travel Time

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.

iGeolise's Travel Time is a system that enables its users to search for how much time a journey takes rather than its distance away. For example, Instead of searching for restaurants within 10 miles of your location (with no idea of how long it will take to get there), you can search for restaurants within 10 minutes of your location, using your desired mode of transport; be it walking, driving or by bus or train.

Travel Time can be a great Resource for personal or business use. Here are some of the benefits:

  • Users can create their own Travel Time maps by selecting a start point, journey time and mode of transport.
  • Businesses can upload up to 3000 points, viewing the travel time from each location back to the origin, and determining whether the specified catchment is within a convenient travel time from the location.
  • Users can download all postcode data within the travel time area.
  • Users can upload their own data and rank, sort and display it by journey time for detailed analysis.
  • Users can print as many maps as required.

iGeolise have provided the Travel Time API that allows developers or site owners to plugin over a RESTful API. At the moment access to the API is free, as long as credit is provided wherever it is used. Developers who are interested in taking advantage of this can sign up on the iGeolise website.

Be sure to read the next API article: "Repeatable Innovation" is in The Commons