PTV Group - Logistics Forum

• 4 waypoints, each with 3600 seconds service duration.
• No break- and rest rules (not relevant for the story)

• First remark: the subsequence of "TourEvent/Service" and "Waypoint" is
  • For the last waypoint the waypoint is listed AFTER the corresponding service.
  • For all other waypoints the Service appears in the array AFTER the Waypoint.
  That's documented in TechnicalConcept.RouteEvents
• But what I don't get: Why is the last service event's "startsAt" given with a value BEFORE the arrival? Or is the definition of the last waypoint's event more like a "the last thing that happens on a route is the last waypoint" and therefore the "Arrival time" is supposed to be derived via "LastWaypoint.StartsAt - LastService.Duration"?
• Sidenode: the node index of the last waypoint event and it's service event are different. Shouldn't they be equal?

But what I don't get: Why is the last service event's "startsAt" given with a value BEFORE the arrival? Or is the definition of the last waypoint's event more like a "the last thing that happens on a route is the last waypoint" and therefore the "Arrival time" is supposed to be derived via "LastWaypoint.StartsAt - LastService.Duration"?

Sidenode: the node index of the last waypoint event and it's service event are different. Shouldn't they be equal?

• Check also the technical concept on result lists. Although not explicitly written, you can see in the graphic that the last waypoint is the end of the route.
• A service time produces a segment of type NOT_DRIVING. Therefore it is normal that the node index of the last service event and the node index of the last waypoint event do not match.
• Keep in mind that there could also be tour events of type break, rest or waiting before the last service. So the arrival would then be before all tour events at the same location as the last waypoint. (Of course that depends on your interpretation of arrival.)
• In PTV Developers Routing API the events are modeled differently. Waypoint and Schedule events will be present in the same event, but the schedule event is not necessarily of type SERVICE as there can be breaks, rests or waiting events upon arrival. Those will be contained in additional events. Likewise, the ETA given in the ETA response marks the time of arrival at the waypoint before any schedule events.