lauraaubin / traveller Goto Github PK

i.e, 🚍5 arriving in 5 minutes then on inspect, Heading home.

Also, could specify the direction of the bus: 7 St Laurent going home

This can be used publicly and will be published with this project when completed.

For example, if we are looking at the 104 that stops at St-Laurent 3025, then we get responses for both directions it runs.

We should know the difference between busses that are "expected" to arrive, and those actually on the way. The API just returns a value for AdjustedScheduledTime.

When a bus is scheduled to arrive and it starts very close, it is very likely that this scheduled time is correct. For example, if the bus starts 2 stops before and is scheduled to arrive in 6 minutes, then it is safe to assume that this bus will spawn very shortly and arrive on time.

Lets make it so that we can estimate when a scheduled time has a higher probability of being correct.

i.e, the bus route 5 from Elgin and busses that start at Carleton

If a bus is on GPS but comes after a scheduled time, the GPS bus is not being recognized. For example,

• Bus in 8 minutes on schedule
• Bus in 20 minutes on GPS
• Bus in 35 minutes on schedule

The API returns -1, 0.94, -1 for the ordering of these busses. Since we are only looking at the first API response, we are only reading the first scheduled bus and not checking if there is even one on GPS.

Possible solution

Should look into parsing the whole XML response instead of just the first entry.

Whiteboarding

If there are NO GPS busses, return the first entry.
If there is A GPS bus in the set of three, return the first GPS bus entry.
If they are ALL GPS, return the first entry.

Current implementation: only returning the first entry no matter what.

What is changed: account for the middle case when there is a GPS bus in a collection of other scheduled busses.

Why is it important to keep track of the other cases? When implementing this fix, make sure not to break the current implementation.

Eliminate hardcoding the script and create a form that gathers necessary information from the user.

Information includes, and is not limited to:

• OC Transpo API ID and key
• Weekly schedule or link to Google calendar
• Manual way of checking bus activity

Determine where you are relative to your daily schedule and provide updated bus tracking based on relative bus stops and general direction of next travel.

i.e, if I am at work, provide bus plans for going home. If I go to Carleton, provide bus plans for going back to work or home depending on the time of day.

Where am I going?

• Sync with Google calendar
• Write up a schedule within the plugin

What bus do I want to take?

• Google API for best directions
• Write up a schedule that includes busses