#1531 – Direction API

Posted in ‘The Booking Form integration’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 29 March 2019 16:02 UTC

We use now our own API key, could you add the direction API function who calculate the time between two points with a specific departure time.

"Traffic Information
Caution: Requests using traffic information are billed at a higher rate. Learn more about how Directions API usage is billed.
Traffic information is used when all of the following apply (these are the conditions required to receive the duration_in_traffic field in the Directions response):

The travel mode parameter is driving, or is not specified (driving is the default travel mode).
The request includes a valid departure_time parameter. The departure_time can be set to the current time or some time in the future. It cannot be in the past.
The request does not include stopover waypoints. If the request includes waypoints, prefix each waypoint with via: to influence the route but avoid stopovers. For example,
&waypoints=via:San Francisco|via:Mountain View|...
Optionally, you can include the traffic_model parameter in your request to specify the assumptions to use when calculating time in traffic.

The following URL initiates a Directions request for a journey from Boston, MA to Concord, MA, via Charlestown and Lexington. The request includes a departure time, meeting all the requirements to return the duration_in_traffic field in the Directions response."

Best regards
Monday, 01 April 2019 10:54 UTC
Hi there,
from all our research regarding Google Maps API, we have come to a conclusion that Google cannot more accurately predict the duration of a trip in the future than with the Directions API that we use at the moment. Directions API uses historical data about the route between 2 points and displays the average duration via the shortest distance.
I see what they have suggested - using "Traffic information" but you understand that traffic conditions can change at any time and it is highly unlikely that it's predicted correctly for a future period.
If you insist on using it we will have to build it as an option at the back office so only you can take advantage of it by turning it on. This will require some custom development and we will have to charge you a development fee.
Let us know if you are interested so we can provide you with a time frame and price quote for development.

Kind regards.
Monday, 01 April 2019 11:13 UTC
Yes i understand.

The calculation of google is actually done on an average and this fact is stable.

The problem I had is that there seems to be an effect depending on the time of the request. (not time of the travel)

The calculation remains on an observed average but the path can change.

For exactly the same request in a big city, if you ask at 8AM you don't have the same resultat than if you ask in the middle of the night.

The calculation is done by km, a rate normally including a bypass via motorway can change enormously by crossing the city.

For my part, I finally create zones and cars by period of time and i solved the problem.

And ... the best is the enemy of good

Best regards;)
Monday, 01 April 2019 11:19 UTC
Hi again,
I'm glad you solved the problem.
Should I consider this ticket as closed then?

Kind regards.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.