xServer 2.23 released

[Bernd Welter]

Here's another release of our xServer v2.23. Most obvious news:

• we polished the toll calculation which enables you to consume all toll contributions in the requested currency
• we reinvented an experimental approach to consider fuel costs in the cost optimized routing
• my buddies in our IMEA office benefit from the additional arabic and hebrew visualization

  

  Screenshot from the xmap rendering showcase shows hebrew labels

  

  Screenshot from the xmap rendering showcase shows arabic labels

Dear xServer Stakeholders,

the PTV xServer 2.23 is released! And these are the highlights:

o xMap: Support for Arabic and Hebrew languages for geographic names
o xMatch/xRoute: Retrieve the ID for each segment of the map provider (experimental)
o xRoute: Retrieve the segments within a reachable area
o xRoute: Return the toll amount in the requested currency
o xRoute: Consider the cost per energy unit and report them (experimental)
o xTour: Specify the sequence of customer stops within a trip
o xTour: Specify multiple driver break intervals with different break durations
o xTour: Specify the maximum number of customer stops that may be served by the vehicle within a tour
o xTour: Specify additional planning objectives like minimizing the total time and distance

Due to several bug fixes the format of high-performance routing networks has changed. Please recalculate all of them. Moreover when running on Linux PTV xServer now requires Ubuntu 20.04 LTS instead of Ubuntu 16.04 LTS.

The on-premise solution can be found here:

o Developer Zone (login required)

The cloud solution PTV xServer internet will be updated according to this plan:

o 28.06.21: Productive system hosted in Australia
o 05.07.21: Productive system hosted in Europa
o 06.07.21: Productive system hosted in US

Regards, your transportation services teams

[Bernd Welter]

Here's another example of a new xTour parameter:

PlanToursOptions -> TweaksToObjective -> minimizeNumberOfTours

If this parameter is set to true, the algorithm plans as many orders as possible using as few vehicles as possible, even though the costs, for example driving time or distance, of the whole plan might increase. If this parameter is set to false, the algorithm plans as many orders as possible so that the total cost is minimized. Therefore it is likely that the number of tours will be higher compared to the result when this parameter is set to false.

And a little example:

TRUE: The optimizer decides to have one long tour which serves all orders from the Depot in Dortmund.

But with the new parameter value set to FALSE the optimizer decides to have more than one tour which reduces the total distance

Best regards,
Bernd