Unsure if a bug or not, if not, please remove label.
Issue
Why won’t trip planner return a trip using the 62 and 92, even if there is a long wait time (instead returns no trip found)
Trip Parameters
Origin: ID 8616
Destination: ID 9173
Walk: 0.5 mile
Depart 6 AM on a weekday
Notes
• In the area of the destination, Line 92 only runs counter-clockwise.
• Schedules play a large role
For a 62 to 92 trip given the start/end points, one would have to alight the 62 at ID 8625, SW Murray NS Teal, north and walk to the line 92 stop at ID 9208, 14700 Block SW Teal, west. The 62 and 92 are scheduled for the same time at their respective stops in regards to the time of the trip (6:28). The next 92 is at 6:52 AM.
This is occurring in both call.trimet.org and the the new (mod) trip planner...
• Won’t give you any trips with the walk set at 0.5, but will give you a 62 only trip if change walk to 0.55 (basically anything higher than 0.5).
• Changed time to see if could ever get a trip with this transfer, and found one at 4 PM (also had to reduce walk to 0.25 to make it happen).
Changing walk to 0.25 for the originally requested time did not work (no trip found message)
Unsure if a bug or not, if not, please remove label.
Issue Why won’t trip planner return a trip using the 62 and 92, even if there is a long wait time (instead returns no trip found)
Trip Parameters Origin: ID 8616 Destination: ID 9173 Walk: 0.5 mile Depart 6 AM on a weekday
Notes • In the area of the destination, Line 92 only runs counter-clockwise. • Schedules play a large role
This is occurring in both call.trimet.org and the the new (mod) trip planner... • Won’t give you any trips with the walk set at 0.5, but will give you a 62 only trip if change walk to 0.55 (basically anything higher than 0.5). • Changed time to see if could ever get a trip with this transfer, and found one at 4 PM (also had to reduce walk to 0.25 to make it happen).
• Beta Planner links: