PTV Logistics Product Forum

I'd rather like to know if it is possible to have the request stored for 3days or even more?

Is there any maximum how long we can store the request?

Hi,

We are currently working on some processes which are developed to use the calculateRoute request against xServer2, and we’ve noticed a significant difference in execution time depending on whether feature layers are enabled.
For a route with +/-19 tour stops, the overall processing time is ...

Hi,
I have a simple question to ask, which is:
Where am I supposed to get the fastest info about security related news?

It would be helpful in order to be more proactive with our setup and keep things patched in a timely manner.

Hi Marko,

I have not checked everything in detail, but here are some quick comments that hopefully help a bit:

On a more unrelated note: Since xServer 2.37 xRoute will also report TOUR_EVENTs of type "DRIVING" after each non-driving TOUR_EVENT (after BREAK and SERVICE events). Keep that in mind ...

Hi there,

if you want to determine traveltime and distance between waypoints you could look into the "legs":
com.ptvgroup.xserver.xroute.Leg
7 waypoints (triangles) 6 legs many tour events

legs.pnglegs2.png

Isn't that sufficient?

Bernd


Hi Bernd,

The legs object do not contain all the ...

I have a question about how to correctly determine the time and distance between waypoints in the xRoute response.

In our product, we initially used calculateRoute without breaks, relying on the RouteResponse/waypoints property to obtain the required data (time and distance between waypoints ...

Stephan Ruppert confirmed, that the parameter "consumption type" is important for declaration, on what base the result is calculated on. But it does not directly impact the result. → All clear now, that is how I assumed it works, when I called it "for documentation purposes".

Thread can be closed.

Thanks Bernd, I understood the idea and difference of the different consumption types. But not the purpose of the real parameters, as they don't impact the result in any way, IMHO. The fuel consumption itself impacts the calculation. Therefore my question: I assume the consumption type is just for ...

Thanks Joost, yes we're using xS 2.

ok, much clearer, do I get correctly, we have 2 options to hand-over fuel consumption:

1. RouteRequest.requestProfile.vehicleProfile.engine.fuelConsumption
→ for type "Vehicle consumption"
2. RouteRequest.routeOptions.effectiveFuelConsumption
→ for type ...