With the STLévis/RTC gtfs for the 2023 travel survey, it is not possible to calculate routes from Lévis to Quebec because an arrival node (station Beneva) is not present in the reverseJourneySteps map.
Any route from Lévis to Québec, with alternatives is affected. The fastest path is often found, but with the alternatives set to 'yes', the problem occurs.
Hypothesis:
would asymetric transferable node times make a node accessible in the forward direction, but not in the reverse?
could reverse connections be unsorted so the arrival node is not yet in the list?
Actually, this bug is present since e8764d7748e7485df234b9196a7a63db66a3ef48 (found by bisecting) and happens also in the Montreal region. It did not happen before this commit with the same data.
With the STLévis/RTC gtfs for the 2023 travel survey, it is not possible to calculate routes from Lévis to Quebec because an arrival node (station Beneva) is not present in the reverseJourneySteps map.
Any route from Lévis to Québec, with alternatives is affected. The fastest path is often found, but with the alternatives set to 'yes', the problem occurs.
Hypothesis:
The cache causing the problem can be found here: https://github.com/chairemobilite/trRouting/releases/tag/untagged-17870e5ef2a95525d736
The following request causes the bug: http://localhost:4000/v2/route?origin=-71.26555890211999,46.71776856267837&destination=-71.32651370058815,46.77191936716429&scenario_id=832a1eb7-bdfd-46dc-9614-4e96fea417d4&time_of_trip=54000&time_type=0&alternatives=true&min_waiting_time=180&max_access_travel_time=900&max_egress_travel_time=900&max_transfer_travel_time=600&max_travel_time=10800