Many transit agencies subscribe to the idea of "Open Data", publishing bundles of information on the system. These feeds contain data on stops, routes, arrival times, fare information, headways, and other pieces of useful data. Even more interestingly, these feeds often have buried within them the ability to access vehicle GPS data, which provides the ability to find out where a transit agency's vehicles are in near-realtime (limited by the speed at which these location queries can be returned).
Developers have long used feeds published by transit agencies for trip planning applications, which are useful in the extent that they can tell you when you need to be at your stop to get to your destination. However, this information source has always contained within it the potential for much more emancipatory uses. Recall Nate Wessel's guest post here on the shortfalls of Google Transit.
Recently, an innovative new use of this technology has begun to be deployed. In Portland, Seattle, London, San Francisco, and perhaps elsewhere, developers have taken the data provided by transit agencies and done something revolutionary: drawn maps of where all the transit vehicles are at any time.
Obviously the image above is a still from a map whose utility depends upon its continual movement- I encourage you to visit the site to see for yourself. A consistent symbology seems to be emerging, where two colors represent inbound and outbound service – in this case red is going out, and blue in – with separate colors representing the different technologies present on the map.
Browniefed over at github explains how this all works:
Buses are using short wave radios to transmit there position. They currently send updates every 30 seconds, and TriMet sees the update about 3 seconds later. Each bus gets a turn sending it's position and works like a tolken ring network. Previously it took 90 – 130 seconds and if a bus missed it's turn then it would be double that time (meaning for 1-5 minutes they would not know the position of a bus)
Buses do not actually send GPS coordinates back, what they do send is distance traveled along their trip. They do use GPS but primarily they are using the odometer for tracking position. There is also a door sensor, to verify that a bus is at a stop. There are all sorts of calibration issues with the odometer and drivers have reported that the vehicle is not updating its schedule adherence until the door opens.
So this is cool, but is it useful? How does having access to the realtime position data improve the user relationship with the transit system? These maps don't give any indication of how soon a bus is coming, or how long you will have to wait for it. They don't tell you where the bus is going, beyond showing the position of the next bus up the line. Of course there is no way to determine the time interval between your stop and the position of the bus icon. As a trip planning tool, live bus maps are next to useless.
However, as a method of communicating the shape of the entire network, live bus mapping does something very interesting. It translates frequency into a very simple unit- number of buses. A map reader can see very easily which parts of the city have a lot of buses, and which have few; which places have overlapping services or an interlocking grid, and which are provided only infrequent lifeline routes. Perhaps this technology could someday be integrated or displayed alongside isochrone visualizations as part of a map of the freedom of mobility afforded by a system, but to my eyes, for the moment this is a very technically accomplished curiosity.
Jarrett, have you seen the live map for the Raleigh/Durham area in North Carolina? http://triangle.transloc.com/
Not only does it show the live position of buses (for 7 different transit systems!), it also shows arrival predictions at all of the stops (which are searchable). Doesn’t show frequency of each route yet, but it’s a pretty useful tool.
As for live maps (even without the arrival predictions) not providing an indication of when the next bus is coming, I disagree. You might not be able to tell the first time you use a bus, but once you know the city/route pretty well, you can get a pretty good sense of when the bus will arrive. I often don’t even need to look at the predicted arrival to know when I need to leave my house or a coffee shop to catch the bus. And that’s very useful to me.
A while back, I created a playback of a day’s worth of selected MBTA bus data, it’s not live but just a way of getting a visualization of the shape of the network.
Here is the live map for the commuter trains in Munich, Germany (not including subway and tram lines, sadly): http://s-bahn-muenchen.hafas.de/bin/help.exe/dn?tpl=livefahrplan
The visualization is not that useful, but what is useful is that this way real-time data about delays is published. (Click on a station to see current estimated arrival times for the next trains).
Which is useful because often a 2-minute delay means I can still catch my connecting subway train, but a 4-minute delay means I’d better use an alternative bus rout.
You can also try iPhone app from Société de transport de Laval “STL Synchro” were you can watch where your incoming bus is in real time. Really usefull when you plan to transfert to another bus line.
It is definitely useful for planning if you have a couple of options for your trip, but which one is best depends on which bus is nearest. I often can take the 17 or the 8 for a trip, so a map that shows which is closer instead of requiring me to make two arrival time queries that I then have to compare mentally is very useful. Likewise, if I need to make a transfer but can choose which stop, the visual convergence of the buses can suggest an option (though you need a mobile version for that).
You do need to be a bit familiar with the system, but many people are sufficiently familiar for that.
Nice picture, but it looks like a Blue Line train is swimming across the Willamette River. 🙂 (For those unfamiliar with Portland, the Steel Bridge, on which MAX trains cross the river, is cropped out of the shot just to the north…)
OTOH, a cropped picture can’t explain what the #6 bus is doing in the middle of the river…. 🙂
Thanks, Erik, for the TransLoc shout out.
Jarret, if you’d like to learn more about TransLoc and our Open API give me a shout. api.transloc.com.