GPS Bus-tracking on the cheap

Step 4 Define a route for your bus of choice

At this point, the system has a good degree of functionality; we could still add some more features like predicting arrival times and simplifying the output information. 

To do this, we'll define a route so that users can know what landmarks are closest to a bus's current position.  We'll also calculate arrival times based on that position.

We want a a five-column comma separated value (CSV) file where each row is a waypoint along the route (see the screenshot below and the attached file for an example -- it should open in Excel or something like Notepad++).  Waypoints are entirely of your choosing (hello, Easter Eggs) and you can add any number of them to the file.  The bus I'm describing takes a linear A to B route one way and then travels B to A on the exact same roads.  The entries for each of my waypoints are as follows: 

title,
latitude,
longitude,
time in minutes to get to A from the waypoint,
time in minutes to get to B from the waypoint. 

Latitude and longitude can be determined with the industrious Simon Willison's www.getlatlon.com.

My time values are only placeholders at the moment; these values could be determined by timing a few rides manually or using a yet-to-be-written logging script for autonomous assistance.

This setup may be expanded in the future to consider buses that travel more complex routes (those routes not of the same-path A-to-B, B-to-A variety).