The ebb and flow of Melbourne trains

This is cool: it’s a representation of Melbourne’s trains across the day, and from a cursory look, appears to be pretty accurate to the timetable (possibly more so than the actual trains!).

Ebb and Flow of Melbourne Trains by Flink Labs from Flink Labs on Vimeo.

From a mob called Flink Labs, who explain how they did it on their web site.

One niggle: It stops at midnight. The trains don’t. Even on weeknights the last of them reaches its destination at about 1am.

If you enjoyed this post, please consider leaving a comment. You can subscribe via feed reader RSS, or subscribe by email. You can also Follow me on Twitter, or Like the blog on Facebook.

10 Replies to “The ebb and flow of Melbourne trains”

  1. I have seen something similiar that shows the daily flights within American airspace as well as transatlantic flights coming to and leaving from the US.

  2. That is awesome. However, a graph is needed next to it to represent the number of cancelled services across the day. That might give it some perspective!

  3. Thanks for the wonderful comments. This is an initial piece with this data and we’d ideally like to take this to the next level and show realtime data or maybe the previous days data with cancellations and late trains indicated so everyone can get an idea of how the system is operating.

    Again thanks and if you have any suggestions please email us at hello@flinklabs.com

    Ben Hosken
    Founder
    Flink Labs

  4. One question: What’s the deal with the line just above the middle on the right that appears to yo-yo the last three stops?

    Very nice, I’m not sure what use it is without usage numbers from embark to disembark.

    Also, when will you be applying this technology to Atlanta non-PT traffic?

  5. Yes you’re right, it looks like a bug on the Belgrave line. It’s as if the train to Belgrave gets there too fast, then jumps back and arrives again at the correct time (most hours x:26 and x:56).

    Sorry, but what’s Atlanta got to do with anything?? (Anyway that’d be a question for the makers.)

  6. The problem was that we had located Upper Ferntree Gully station in the wrong place. So the system through the train line went out then back on itself. We’ve fixed the station location and we’ll republish the visualisation.

    Thanks again for spotting it.

Comments are closed.