Skip to content

Walking to Farther Bus Stops #1302

@meyersj

Description

@meyersj

Graph and Config: http://maps5.trimet.org/otp-bugs/osm/

In the new stable version OTP is providing a route that has the user walk to a bus stop that is farther away than necessary. It seems to occur when snapping to a bus stop catty corner from the ideal departure location. This bug does not happen in the old stable version.

Example 1:

When starting trip from StopID 6809, OTP has you walk two blocks north to StopID 6785 instead of going catty corner across the intersection to StopID 6808. If you start from StopID 6808 you get the expected results. It doesn’t seem like it is related to walkReluctance and waitReluctance. Line 8 picks up at StopID 6808 at 10:35 am. When planning a trip from the catty corner stop at 10:30 am you have enough time to walk north two blocks and can catch that bus. However if you plan the trip at 10:33 am you don’t have enough time to make the walk and miss the first bus.

Weekday trip

Incorrect @ 10:30 am (StopID 6809): http://maps5.trimet.org/?purl=/osm&submit&fromPlace=45.545289,-122.650503&toPlace=45.571101,-122.649520&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=10:30am

Incorrect @ 10:33 am (StopID 6809): http://maps5.trimet.org/?purl=/osm&submit&fromPlace=45.545289,-122.650503&toPlace=45.571101,-122.649520&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=10:33am

Correct @ 10:33 am (StopID 6808): http://maps5.trimet.org/?purl=/osm&submit&fromPlace=45.545080,-122.650340&toPlace=45.571101,-122.649520&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=10:33am

Correct behavior in old stable(StopID 6809): http://ride.trimet.org/?submit&fromPlace=45.545289,-122.650503&toPlace=45.571101,-122.649520&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=10:30am

farther_bus1

Example 2 (exact same behavior):

When starting at StopID 3584 OTP has you walk two blocks north to StopID 3582 instead of going catty corner across the intersection to StopID 3583. If you start at StopID 3583 you get the expected results.

Weekday trip

Incorrect (StopID 3584): http://maps5.trimet.org/?purl=/osm&submit&fromPlace=45.483051,-122.800408&toPlace=45.491116,-122.801239&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=4:22pm

Correct (StopID 3583): http://maps5.trimet.org/?purl=/osm&submit&fromPlace=45.482796,-122.800237&toPlace=45.491116,-122.801239&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=4:22pm

Correct behavior in old stable (StopID 3584): http://ride.trimet.org/?submit&fromPlace=45.483051,-122.800408&toPlace=45.491116,-122.801239&mode=TRANSIT,WALK&min=QUICK&maxWalkDistance=840&time=4:22pm

farther_bus2

Metadata

Metadata

Assignees

Labels

StaleThis issue is stale, no activity for 90 days. Remove stale label or comment within 30 days.TriMet

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions