Sometimes length matters ;-)

Usually a route is optimized for travel time. The result is a fast route a real driver would follow accepting a longer distance, if necessary. But there are use cases where you want to optimize a route for distance, for example in case of billing purposes based on distance.

In the new version of the PTV Developer Routing API V1.13.0 you have the possibility to use the new parameter ‘routingMode’ by selecting ‘FAST’ (optimize for travel time) or ‘SHORT’ (optimize for distance).

In the above example there is the orange route with longer distance but lower travel time using mainly the motorway (‘FAST’) compared to the blue route with shorter distance but higher travel time crossing the black forest (‘SHORT’).

Please note that both modes do not calculate the absolutely fastest or shortest route. The results are still meaningful and avoid rural roads and residential areas. If you want to know more, just have a look on the corresponding technical concept or test it with our brand new code sample.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Route violated! But where?

When there is no valid route for your vehicle between two waypoints possible at all, the route is nevertheless calculated and marked as violated. This is typically the case for prohibited areas around waypoints, which have to be entered or exited anyway. Other “obstacles” like weight restrictions on the way are usually bypassed and not part of the calculated route.

Up to now, you can request violation events in such routes containing the position, time and the vehicle property in question. In the new version of the PTV Developer Routing API V1.12.0 we also provide the polylines of the violated route parts by using the new parameter ‘VIOLATION_EVENTS_POLYLINE’.

With this polyline it is easy to display the violated route parts on a map. Illustrated above, the first part of the route is marked in red as this is prohibited for the current vehicle because of the surrounding forest. Of course, there is a new code sample for this feature and you are welcome to play around with it! 

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

How to recalulate a driven route and calculate the toll costs?

Do you have a use case, where you need to calculate the toll costs or emmissions for a driven route?

You can calculate toll or emissions for a driven route if you combine the PTV Developer Map Matching API and PTV Developer Routing API

We now offer you a new Technical concept which describes in detail how to establish that! You also can check out our tutorial regardig toll routing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Traffic events

Do you remember the traffic delay introduced in one of the last versions of the PTV Developer Routing API? For the delay we compare the travel time with and without live traffic on the same route (see this blog post).

In the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘TRAFFIC_EVENTS’ provides traffic events chronologically along the route in the event list, together with all other events like waypoints, maneuvers or toll (see this concept). Then you know exactly where and why there is a delay.

Check out the traffic events in the code sample for recalculating a route with events. Do you need a RouteId? Just create one with the code sample for RouteIds.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Guided navigation

With guided navigation you have the possibility to use a calculated route from PTV Developer in our truck app PTV Navigator. For this we offer in the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘GUIDED_NAVIGATION’ to get the calculated route in an additional format easy to import in PTV Navigator.

Detailed information is available in the corresponding concept. In addition you can test it in our new code sample!

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Choose a ferry or rail shuttle connection

Up to now ferries or rail shuttles are automatically used on a route, if it is advantageous compared to road (as so called combined transport) and of course, if you don’t want to avoid them (see this blog post). In the new version of the PTV Developer Routing API V1.9.0 you even have the possibility to choose a specific ferry or rail shuttle connection.

For this you just specify an additional waypoint of type ‘combinedTransport’ including the start and destination coordinates of the ferry or rail shuttle connection. The nearest port or station is automatically searched around the two coordinates and the corresponding connection is used on the route.

 

 

The left route above shows a route without a combined transport waypoint using an automatically chosen ferry. The additional combined transport waypoint on the right route allows to choose another ferry connection. Please note that this waypoint will not appear in the response and may not be used as start or destination of the route.

The best thing to start is exploring our new code sample for all available waypoint types including the new one!

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.