'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)

This forum deals with any kind of routing computation whether it is simple A:B-routing, calculation of isochrones, simple matrix computation or nearest search.
Post Reply
marius.vladutoiu
Posts: 6
Joined: Tue Mar 12, 2024 10:30 am

'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)

Post by marius.vladutoiu »

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.
It is true, that the 2 addresses are in a mountain area, where there are some time-dependent restrictions (I can see them when looking at the map).

However, I am not sure how that plays a role in this issue: when the response comes, it contains 2 tourEventTypes 'Wait' of duration exactly 2703 seconds each (this number in itself is strange, since it's 45 minutes and 3 seconds) and always placed between 'Driving' tourEventTypes.

I understand how the 'Driving' events would have such long durations, even if very little distance, because of the TrafficIncidents (time-dependent restrictions) in the area.
But I don't understand the purpose of the 'Wait' events of this strange duration, and their placement in between Driving events.
Can you please help in how to interpret this response?

Marius
Attachments
screenshot to illustrate the question/issue
screenshot to illustrate the question/issue
response.xml
xroute response from raw request runner
(7.59 KiB) Downloaded 2 times
request.xml
xroute request
(4.29 KiB) Downloaded 4 times
Joost
Posts: 318
Joined: Fri Apr 25, 2014 1:46 pm

Re: 'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)

Post by Joost »

The route is taking combined transport during the waiting event. The driver is then not driving and most of the times it can't be used as a break so waiting is the correct event for what is going on.

I figured this out by also ask for the segment back and look for the segment that had the ID reference in it's eventIndeces property and I found:

Code: Select all

{
      "distance": 0,
      "travelTime": 2703,
      "travelSpeed": 0,
      "trafficDelay": 0,
      "violated": false,
      "eventIndices": [
        6
      ],
      "type": "COMBINED_TRANSPORT",
      "combinedTransport": {
        "name": "Furka",
        "type": "RAIL",
        "duration": 2703,
        "start": {
          "name": "Realp",
          "country": "CH",
          "coordinate": {
            "x": 8.5028062755,
            "y": 46.597683661
          }
        },
        "destination": {
          "name": "Obergoms",
          "country": "CH",
          "coordinate": {
            "x": 8.3430719887,
            "y": 46.531307915
          }
        },
        "permissions": {
          "cars": true,
          "vans": true,
          "trucks": true
        }
      }
    },
Joost Claessen
Senior Technical Consultant
PTV Benelux
marius.vladutoiu
Posts: 6
Joined: Tue Mar 12, 2024 10:30 am

Re: 'strange' tourEventTypes 'Wait' in certain response (effect of PTV_TrafficIncidents)

Post by marius.vladutoiu »

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'.

Ok, this I can understand. But then, can you confirm that 'combined_transport' is only related to PTV_TrafficIncidents layer? Because, if I use the same request, but just set the PTV_TrafficIncidents = false, the 'wait' event is not triggered anymore in the response.

Or can you think of any other situation where this 'Wait' event would be inserted? (even though I now understand it's not always 'Waiting' per se, there's just no other event to properly describe it).
Post Reply