Generates a time and distance matrix for specified waypoints. Can use multiple ways of routing.
GET/tdtable/:vehicle_type/:wkt_waypoints
Returns JSON with a proposed route or error if a route can not be found. Request table for 2 points and single time of departure:
/tdtable/v1/driving/44.0925729,56.2944997;44.0879421,56.2958883?timestamp=2019-09-09T12:00:05Z
Request table for 2 points and separate time for every starting point:
/tdtable/v1/driving/44.0925729,56.2944997;44.0879421,56.2958883?start_times=2019-09-09T12:00:05+03:00;2019-09-09T13:00:05+03:00
Request table for 4 points where 2 of them are sources with individual departure times:
/tdtable/v1/driving/116.066862,52.109515;116.052582,52.109345;116.052582,52.106243;116.066863,52.106020?sources=0;3&approaches=curb;curb;curb;curb&start_times=2019-09-09T12:00:05+03;2019-09-10T13:00:05+03
Use 50 meter distance sense to prevent from using for short transfer:
/tdtable/v1/driving/44.0925729,56.2944997;44.0879421,56.2958883?start_time=2019-09-09T12:00:05Z&distance_sense=50
The Routingenging support producing non-square time\distance matrices by providing a list of indeces for dropoff or picksups in sources and destination field.
Request
Responses
- 200
- 400
- 403
- 404
successful operation
This result code is returned for requests that are not valid: for example, request type is not recognized, request contains unrecognized parameter or parameter value is invalid. With this result code http reply contains a json document in the body, where a short description of invalid part of the request is stored as a string data.
Request is not authenicated or is not allowed for this user
This code can be returned for route/tdroute requests when daemon could not find a route between waypoints. Json document containing short description of issue is always returned with this result code inside the http reply body.