I have been playing with this issue some more, with different scenarios, and got the same strange behavior, but even with same speeds, just a different address as destination. So I wonder if it is rather an issue of geography of some sorts.
I did identify a scenario where in the xroute response ...
Search found 8 matches
- Thu Apr 30, 2026 2:02 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: #6506 : DRIVING event is not displayed after WAITING in certain scenario
- Replies: 2
- Views: 1589
- Fri Apr 24, 2026 9:15 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: #6506 : DRIVING event is not displayed after WAITING in certain scenario
- Replies: 2
- Views: 1589
#6506 : DRIVING event is not displayed after WAITING in certain scenario
Hello,
I have the following situation.
Driving from A > B, between A and B there is a changed in the combined transport (RAIL), which automatically generates a WAITING tourEventType between A and B.
So basically the tourEventTypes in the response are like this (see response1 xml file attached ...
I have the following situation.
Driving from A > B, between A and B there is a changed in the combined transport (RAIL), which automatically generates a WAITING tourEventType between A and B.
So basically the tourEventTypes in the response are like this (see response1 xml file attached ...
- Tue Feb 17, 2026 1:08 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: 'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)
- Replies: 3
- Views: 42942
Re: 'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)
Hello Joost,
Thanks for the quick reply. If I understand you correctly, the 'Wait' is actually the duration of the 'combined_transport', in this case 'rail' as the only means of transport to actually get to the address, which could not be classified as 'driving'.
Additional questions, please:
(1 ...
Thanks for the quick reply. If I understand you correctly, the 'Wait' is actually the duration of the 'combined_transport', in this case 'rail' as the only means of transport to actually get to the address, which could not be classified as 'driving'.
Additional questions, please:
(1 ...
- Tue Feb 17, 2026 12:12 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: 'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)
- Replies: 3
- Views: 42942
'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)
Hello,
I have the following issue: I am running an xroute for a roundtrip, going from one start address to 2 addresses, and then coming back (see attached reques and response).
I am not 100% sure, but it looks like the issue I am having only happens when the PTV_TrafficIncidents layer is enabled ...
I have the following issue: I am running an xroute for a roundtrip, going from one start address to 2 addresses, and then coming back (see attached reques and response).
I am not 100% sure, but it looks like the issue I am having only happens when the PTV_TrafficIncidents layer is enabled ...
- Wed Oct 08, 2025 1:42 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingHours
- Replies: 8
- Views: 49731
Re: In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingH
Based on the new info regarding rules, in order to test whether maximumTravelTimeBetweenDailyRests was considered correctly, I set my case up like this:
maximumDrivingTimeBetweenDailyRests = 7200
maximumTravelTimeBetwenDailyRests = 3600
dailyRestTime = 10800
so that 7200 ≤ 3600 + 10800
then ...
maximumDrivingTimeBetweenDailyRests = 7200
maximumTravelTimeBetwenDailyRests = 3600
dailyRestTime = 10800
so that 7200 ≤ 3600 + 10800
then ...
- Mon Oct 06, 2025 11:54 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingHours
- Replies: 8
- Views: 49731
Re: In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingH
Hi Bernd,
Thanks for the feedback. It would be great for this to be fixed as soon as possible.
Yes, I agree with your dev that if maximumDrivingTimeBetweenBreaks>=maximumWorkingTimeBetweenBreaks, then maximumDrivingTime BetweenBreaks should be ignored, because it will never happen.
But ideally ...
Thanks for the feedback. It would be great for this to be fixed as soon as possible.
Yes, I agree with your dev that if maximumDrivingTimeBetweenBreaks>=maximumWorkingTimeBetweenBreaks, then maximumDrivingTime BetweenBreaks should be ignored, because it will never happen.
But ideally ...
- Wed Oct 01, 2025 9:27 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingHours
- Replies: 8
- Views: 49731
In xRoute request, it seems like maximumWorkingTimeBetweenBreaks parameter is not considered in configurableWorkingHours
In the sample xml file attached, containing a xRoute request, in the tourRestrictions, configurableWorkingHours are added.
Regardless of the value that I set for the maximumWorkingTimeBetweenBreaks, no tour events of type Break are inserted (in the sample, it is set as low as 3600).
But as I look ...
Regardless of the value that I set for the maximumWorkingTimeBetweenBreaks, no tour events of type Break are inserted (in the sample, it is set as low as 3600).
But as I look ...
- Fri Feb 14, 2025 2:04 pm
- Forum: PTV xTourServer / DEV.RouteOptimization / DEV.SequenceOptimization
- Topic: Usage of FIRST_CUSTOMER_STOP and LAST_CUSTOMER_STOP
- Replies: 1
- Views: 69842
Usage of FIRST_CUSTOMER_STOP and LAST_CUSTOMER_STOP
Hello Bernd,
Been trying to see if this FIRST_CUSTOMER_STOP (or LAST_CUSTOMER_STOP) is the right property that we need to implement to achieve the following xTour planning result, and can't quite figure it out:
Basic case:
Pickup 3 orders at same address (vehicle depot)
Delivery each order at ...
Been trying to see if this FIRST_CUSTOMER_STOP (or LAST_CUSTOMER_STOP) is the right property that we need to implement to achieve the following xTour planning result, and can't quite figure it out:
Basic case:
Pickup 3 orders at same address (vehicle depot)
Delivery each order at ...