PTV Group - Logistics Forum

Hi,
we use xRoute1 without special settings for break rules and rest rules.
With long routes (longer than one week) we have sometimes strange results with weeklyRestPeriod.
e.g.
Tour with 82 stations starts on Monday, 28.11.2022 and ends on Tuesday, 13.12.2022. Operatingintervalls are set 7:00 to 16:00 o'clock.
First weeklyRestPeriod (162000) occurs at service point between 01.12.2022 and 03.12.2022.
Second and last weeklyRestPeriod (162000) occurs at service point between 06.12.2022 and 08.12.2022.

For test purposes we reduced OperatingIntervalls to 12:00 to 16:00 o'clock. weeklyRestPeriods seems to be more plausible for same tour this time.
Tour starts on Monday, 28.11.2022 and ends on Thursday, 29.12.2022.
First weeklyRestPeriod (162000) occurs on road between 03.12.2022 and 05.12.2022.
Second weeklyRestPeriod (169200) occurs at service point between 11.12.2022 and 13.12.2022.
Third weeklyRestPeriod (162000) occurs on road between 18.12.2022 and 20.12.2022.
Fourth and last weeklyRestPeriod (162000) occurs on road between 26.12.2022 and 28.12.2022.

1) What could be the reason for weeklyRestPeriods of the first example?
2) Is there a way to get a route calculation completely without daily and weeklyRestPeriods?

Hi Chris,

could you please provide the complete request/response of your calculateAdvncedTour transaction?
Worst case 1:1 to me = bernd.welter@ptvgroup.com

If you don't want to consider the rules you could

• either switch to xroute1.calculateExtendedRoute
• or use xroute1.calculateAdvancedTour with some TourOptions being disabled

Does this answer part 2?
Bernd

We discussed this topic internally...

• Situation: In theory there are at least two potential "solutions" and unfortunately the current xRoute1 implementation leads to the one you don't prefer
• Perception: This is not seen as a bug but as a "potential feature improvement" and as xRoute1 is feature frozen we won't apply this anymore in xRoute1
• Future: There is now some awareness in the product management / product owners and they will check whether and how we approach this situation in the xServer2 and PTV Developer

Best regards,
Bernd

PS: the underlying "task" in the bugtracking system will be closed