This forum deals with any kind of trip optimization based on xTour1, xTour2 and the Developer APIs "RouteOptimization" and "SequenceOptimization". No matter whether it is automatic planning or manual dispatching, refering to transport orders or service planning.
Attention: this does not refer to PTV Optiflow SaaS and PTV Developer RouteOptimization Optiflow.
in the Optimization APIs the flexibility of the underlying routing matrices is usually limited:
Users can choose the vehicle profile from a given set of available standard profiles which all support high performance routing for fastest dima calculation.
Therefore overriding vehicle properties such as physical dimensions or emission classes is not possible (at least of now) in the standard cloud services.
In the Route Optimization OPTIFLOW API you can benefit from the vehicle's traffic mode if your base profile supports it.
In the VRP Solver based APIs "PTV Route Optimization" and "PTV Sequence Optimization API" (both in maintenance mode!) the profiles are based on static, time-independent graphs. Therefore these two APIs do not support time dependency on the same level as the OPTIFLOW API does.
Please get back to us 1:1 so we might discuss how to get best quality for your users requirements.
Bernd
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...