Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan via visit stations does not work when the stations are on my normal reasonable route #6360

Open
miklcct opened this issue Jan 3, 2025 · 1 comment

Comments

@miklcct
Copy link
Contributor

miklcct commented Jan 3, 2025

NOTE: this issue system is intended for reporting bugs and tracking progress in software
development. For all other usage and software development questions or discussion, please post a
question in our chat room: https://gitter.im/opentripplanner/OpenTripPlanner.

Expected behavior

It return journeys which changes at the specified station.

Observed behavior

It return journeys which merely pass through, or even without passing through, the specified station.

Version of OTP used (exact commit hash or JAR name)

2.7.0-SNAPSHOT

Data sets in use (links to GTFS and OSM PBF files)

London trains and tubes

Command line used to start OTP

Router config and graph build config JSON

ConsiderPatternsForDirectTransfers is on
TransferConstraints is off

Steps to reproduce the problem

Plan a journey from London Fields to Willesden Green.

There are two normal routes:
Weaver to Liverpool Street, Metropolitan to Finchley Road and Jubilee to Willesden Green
Walk to Hackney Central, Mildmay to West Hampstead (Overground), walk to West Hampstead (Underground), Jubilee to Willesden Green

I add a visit point at Finchley Road & Frognal.
The expected result is to alight Mildmay at Finchley Road & Frognal, walk to Finchley Road and take the Jubilee, but the journey planner still tells me to change at West Hampstead.

I add a visit point at Finchley Road (Underground) instead of the above, the expected result is to only return the routes using the Metropolitan line by changing there, but some of the results still tell me to take the Mildmay to West Hampstead, which doesn't even pass through the station I want to visit.

Note that this problem does not appear if the normal reasonable routes do not pass through the stations I want to visit. The problem only appears if I want to force the change points to be different from the normal one. In the Mildmay - Jubilee example, the normal change point is West Hampstead but it is also possible at Finchley Road or Kilburn / Brondesbury.

Details to be added later

@miklcct miklcct changed the title Plan via visit location does not work Plan via visit stations does not work when the stations are on my normal reasonable route Jan 3, 2025
@miklcct
Copy link
Contributor Author

miklcct commented Jan 3, 2025

I am now trying to plan a journey from Wembley Park to Aylesbury. The normal route is to change at Harrow on the Hill for Chiltern Railways. Therefore it will tell me to take the latest available Metropolitan line train (which may head elsewhere than Amersham) to change at Harrow on the Hill, as the Metropolitan is less frequent beyond Harrow on the Hill, and Chiltern Railways is faster than Metropolitan between Harrow on the Hill and Amersham.

Screenshot_20250103-213919.png

Screenshot_20250103-213553.png

Screenshot_20250103-213609.png

However, I want to force a change at Amersham (because I know that it is much cheaper to use my Oyster card all the way to Amersham, and I have to leave the train to touch out there before continuing my journey to the world outside Oyster - the server doesn't have any fare information yet), so I specify Amersham as a visit station. It now correctly tells me to take an earlier Metropolitan line which terminates at Amersham, however, it still tells me to change at Harrow on the Hill, which is clearly wrong.

Screenshot_20250103-213741.png

Screenshot_20250103-213800.png

Screenshot_20250103-213815.png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant