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, the request for this response is request1):
- Service (at location A)
- Driving (from A to location of change from road to RAIL)
- Waiting (entry-exit the RAIL combined_transport)
- Driving (from location of exit Rail to B)
- Service (at location B).
However, when I change the maximum/minimum speeds in the initial request (see request2 xml attached) to other values, suddenly the tourEventTypes list in the response (see response2 xml file) is missing the 2nd Driving event. In other words it looks like this:
- Service (at location A)
- Driving (from A to location of change from road to RAIL)
- Waiting (entry-exit the RAIL combined_transport)
-
Driving (from location of exit Rail to B) (event missing) - Service (at location B).
Note: it may be that it is not the speeds creating the issue with the missing toureventtype, that is just my experience.Why is this second 'Driving' toureventtype missing? I am counting on it to be there, and cannot figure out why some different speeds would make it disappear.
I attached here as well another request (request3 xml), which is using the same speed profile from the problematic request2, except other A-B addresses (which nevertheless have a combined transport change point between them). But in this case, the response is still ok, the 2nd Waiting tourEventtype still appears in the response (response3 xml attached).
