PTV Logistics Product Forum

I'm guessing you are using xServer 2, let me know if I'm wrong.

The RouteRequest.requestProfile.vehicleProfile.engine.fuelConsumption and RouteRequest.requestProfile.vehicleProfile.engine.electricityConsumption are only intended for the "Vehicle consumption" calculation. The fuel consumption for ...

Are SVPs positions valid input for the track matching?

For a usable output it depends how dense the SVP's are. If they are to spread out from each other you will get a lot of broken paths. In that case you are better off with a regular routing and use manipulate waypoints for the SVP's.

Hello Arjan,

You where probably running the TLNplanner edition of the Europe map before and now have a stock edition installed. Please conacnt you support contact to get a TLNplanner edition of the map.

With Regards,
Joost

A route violation means that the route is not possible to be driven by the vehicle. The dima can't hold route violation details and therefor they are not available for xTour to give back. If you want to know the details you need to recalculate the violated leg with xRoute. Hint: route violation ...

Create a fake Demand with max. priority and with an equipment that only that technician has.

This is what i recommend to my customers and it works pretty good.

There is one slight downside to this approach: it will mean that the vehicle in question will always be planned in. So for a day where ...

Admin Edit by Bernd (6.10.2023): Joost's statement below is not correct.
Therefore we decided to map all prices in DF5 to the "CO2-class 1” in xServer1.
Details are explained in this succeeding post .


=======
Joost:

What does that mean exactly for on premise xRoute 1.x?
Does PTV provide a ...

Main difference is the size of the dima. xRoute does not support large dima's. The limit is iirc 750 x 750 for xRoute.

In xServer 2 xRoute no longer has a matrix call. We decided that maintain dima functions on 2 locations is not usefull. Instead we did support easy dima access for smaller dima's ...

Mixing them is possible out of the box. So there is another reason why the order remained unplanned. This can be figured out with the findChangeTourProposal.

Note: since i do not know you parameters for building the dima I'm using Direct Distance in the rest of my explanation.

First of all: store ...

A couple of versions ago detailed toll became the standard for xServer 2. So atm the parameter is not used to enabled detailed toll, but rather disable it by explicitly setting it to false. Because of this we are keeping this parameter experimental.

Therefore I'd recommend to use a routed distance matrix ( ExistingDistanceMatrix ) which is based on the built in fallback to geometric distance. For this you could apply a routing profile which "fails by design", e.g. by setting a ridiculous geographic restriction (meaningless bounding rectangle ...