Truck attributes consideration

[andrei.koelsnikovich]

Hello,
We are in active phase of migration from xServer1 to Optiflow. A lot of different cases were solved, but for use case with truck attributes I can't find solution. Hope for your support.
Use case, where we have a propblem: 1 order from Route de la Raffinerie 21, Cressier (47.040007 7.033619) to Route de la Chenevière 45, Granges-Paccot (46.821398 7.137604), which we try to deliver with vehicle weight of 20 tons. xServer1 returns error, that this not allowed. However using Optiflow, even by providing maximum heavy Vehicle profile EUR_TRUCK_40T it returns succesfull results. Is this use case solvable?

Thanks for you help.
Best regards,
Andrei Kolesnikovich

[Bernd Welter]

Hi Andrei,

Please send the complete request/response to me (bernd.welter@ptvlogistics.com) and I will return my feedback to you 1:1.
We can also share the generic output with the community afterwards.

Without knowing the details I anticipate that the vehicle profile you used allows violations to appear (afaik this is the default)

If this assumption is correct you can forbid such kind of a result by assigning allowViolations to false.

Bernd

[Bernd Welter]

I made some test with the HERE map 2026.2H and it looks like the delivery location is placed in a "residents only" area.

As I cannot provide more details about this I kindly request you to create a helpdesk ticket so DEV can look into this.
Once the ticket is in place please share it's ID with me.

[Bernd Welter]

Here's some MIRA output:

RESIDENTS_ONLY is a violation type in routing. It applies when a road is flagged as "residents only" and the vehicle profile prohibits these roads.

For predefined profiles (like EUR_TRAILER_TRUCK), the documentation states:

"RESIDENTS_ONLY — This will not happen for the predefined profiles."

This means: Predefined profiles do not produce RESIDENTS_ONLY violations — they are allowed to use these roads by default. Your current scenario with EUR_TRAILER_TRUCK should therefore have no issue with residents-only zones.

If you want to explicitly block residents-only roads
This is where Custom Routing Profiles come in — they can model specific road restrictions, e.g. blocking access to certain roads or areas for particular vehicle types. A custom profile is then specified in the routing.profile field on the vehicle, just like a predefined profile.

Creation: Custom Routing Profiles are created via PTV support.

Summary

Approach	Description
Predefined profiles	Ignore RESIDENTS_ONLY restrictions — no action needed
violations: ALLOW	Allows the router to pass through restricted areas (incl. Residents Only)
violations: DISALLOW	Forbids all violations — route may become longer or impossible
Custom Routing Profile	Tailored road restrictions, created via PTV support

In your case with violations: DISALLOW and EUR_TRAILER_TRUCK: Since the predefined profile does not generate RESIDENTS_ONLY violations in the first place, the route should be calculated without issues. If the destination coordinate is still unreachable, a Custom Routing Profile would be the clean approach.

[andrei.koelsnikovich]

Hi Bernd.
Thanks a lot for all your responses, you are producing them much faster than I am answering on questions.
Since I'm on stabilization of 1st version integration into our software, it's a bit difficult to answer fast.
Last response from MIRA very informative, and for sure custom vehicle profiles are not a topic for first phase of Optiflow integration.

[Bernd Welter]

So for the moment we would have to focus on

• explaining what happens
• evaluate what is possible with standard leverage

Just get back to us with specific requests, also 1:1 if the underlying data should not appear in the forum.

[andrei.koelsnikovich]

I decided to make 1 more test with vehicle attributes. Small note, to understand our integration. We are making request to Optiflow to build sequence of order execution and next we are making request to Decveloper.Routing to build a route. Before we had identical with xTour/xRoute components.

• Here is result of xServer1 over xRoute component, which looks for me valid

  

  x-Route.png (25.85 KiB) Viewed 552 times

• And this is result of routing over Developer.Routing which drives over restricted road.

  

  developer-routing.png (18.84 KiB) Viewed 552 times

Request to Developer.Routing was sent with next parameters: ?profile=EUR_TRUCK_40T&vehicle%5BengineType%5D=COMBUSTION&vehicle%5BfuelType%5D=DIESEL&vehicle%5BelectricityType%5D=NONE&vehicle%5BemissionStandard%5D=EURO_6&vehicle%5BemptyWeight%5D=40000&vehicle%5BloadWeight%5D=40000&vehicle%5BtotalPermittedWeight%5D=40000&vehicle%5Bheight%5D=350&vehicle%5Blength%5D=1500&vehicle%5Bwidth%5D=300&options%5BstartTime%5D=2026-04-01T04%3A00%3A00%2B00%3A00&options%5BtrafficMode%5D=AVERAGE&options%5Blanguage%5D=en&options%5Bcurrency%5D=CHF&options%5BroutingMode%5D=FAST&options%5BspeedFactor%5D=1&emissionOptions%5BcalculationMethods%5D=ISO14083_2023&emissionOptions%5Biso14083EmissionFactorsVersion%5D=VERSION_2&results=ROUTE_ID%2CPOLYLINE
And reauest body: {"waypoints":[{"onRoad":{"latitude":46.83335876464844,"longitude":7.172900199890137}},{"onRoad":{"latitude":46.82181167602539,"longitude":7.182889938354492}}]}
According to response from Optiflow it is planning tour over this road as well. Assumtion based on tour duration and length from response. I can provide both if required.

[Bernd Welter]

Same cause: the segments are restricted to "residentsOnly"...

Screenshot based on xRouteToll2.

Unfortunately you can hardly visualize this with Developer tools - I used xRoute2 to replay this.