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.
They are used during the dima build up phase. They are not used during the planning phase.
For example the totalPermittedWeight is used to determine is the vehicle is a car or a truck and thus if during the routing blocking for cars or trucks should be taken into account. If you also configure the profile to load a RoadEditor Layer like our TruckAttributes set ,the dimensions will also be used to check against specific blocking which are conditional on them like for example "blocked for vehicles higher them xxx cm".
to be a bit more offensive than Joost:
You have to take care to activate the additional data resources such as feature layers or RoadEditor layers.
Otherwise the properties you mentioned won't be taken into account. And in fact I already faced several customers who spent a lot of time in proper configuration of properties but didn't activate the data. So they computed tours without the necessary detours and used streets that were forbidden. Especially with xTour this is difficult to see because quite often the routes aren't visualized.
This snippet contains - activation of the traditional TruckAttributes - activation of the state-of-the-art feature layer TruckAttributes - the physical dimensions and further relevant properties of the vehicle and so on This example is based on a case where the customer wanted to be sure not to use mountain passes where trailers are forbidden.
Best regards 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...