Hi all, potentially a bit of a weird issue I’ve noticed while using the Journey API today,
It’s the first time I’m properly using it - so there may be something I’m missing here, but it seems like if I use the flag useMultiModal
in my request, the journey options back all ignore the ‘via’ field in my request. This happens when I use that flag, and with any overrideMultiModalScenario
number.
Can see this happening with the following urls (the via is around woolwich station)
Non multi modal: https://api.tfl.gov.uk/Journey/JourneyResults/51.53057,-0.01748/to/51.428368425112424,-0.16769341302498017?nationalSearch=false&date=20240127&time=1300&timeIs=departing&routeBetweenEntrances=true&useMultiModalCall=false&via=51.4912883708253,%200.0702215019660749 - time is 92 mins and if you look through steps you can see woolwich
Using multi modal:
https://api.tfl.gov.uk/Journey/JourneyResults/51.53057,-0.01748/to/51.428368425112424,-0.16769341302498017?nationalSearch=false&date=20240127&time=1300&timeIs=departing&routeBetweenEntrances=true&useMultiModalCall=true&via=51.4912883708253,%200.0702215019660749 - time is 52 mins and no Woolwich in sight
Anyone know if there is there a reason for this or is this an API issue?
Also, the overrideMultiModalScenario
and includeAlternativeScenarios
params don’t seem to be in the API docs
Thanks!