Expected behavior
It is possible to transfer between stops with directional GTFS pathways.
Observed behavior
Transferring is not possible or takes unrealistically long times.
If OptimizeTransfers is disabled then there is a 23 minute walk instead of a few minute transfer, since the subway is alighted a stop earlier to transfer to the bus.
If OptimizeTransfers is enabled then the correct transfer is used, but there is an unexpected 20 minute wait while both trips have less then 10 minute frequencies. This is presumably because the transfer was replaced with the better one.
The correct transfer is not found because it is currently assumed that transfers are symmetric, which is not true (in our case due to directional pathways). If the transfers are reversed/symmetric, then the correct path is found.
Version of OTP used (exact commit hash or JAR name)
dev-2.x - 66de53b
Expected behavior
It is possible to transfer between stops with directional GTFS pathways.
Observed behavior
Transferring is not possible or takes unrealistically long times.
If
OptimizeTransfersis disabled then there is a 23 minute walk instead of a few minute transfer, since the subway is alighted a stop earlier to transfer to the bus.If
OptimizeTransfersis enabled then the correct transfer is used, but there is an unexpected 20 minute wait while both trips have less then 10 minute frequencies. This is presumably because the transfer was replaced with the better one.The correct transfer is not found because it is currently assumed that transfers are symmetric, which is not true (in our case due to directional pathways). If the transfers are reversed/symmetric, then the correct path is found.
Version of OTP used (exact commit hash or JAR name)
dev-2.x- 66de53b