Metrolink Tracker uses data provided by TfGM to locate trams on the network and predict their arrival times at each station using previously observed transit times. This allows for more accurate arrival predictions of more trams at each stop than has previously been available.
No. This website and its developer are in no way connected to or endorsed by Metrolink or TfGM. But we do use data provided freely by TfGM.
Unfortunately, the data provided by TfGM isn't 100% accurate. We use the same data that is used to drive the displays on the platforms. We have to infer a lot from this data. Sometimes trams drop off Metrolink's radar. If that happens, it drops off of our data too. This also sometimes happen when we infer tram progress incorrectly from the data TfGM provides.
Again, this is because the data provided by TfGM isn't 100% accurate and can happen for a number for reasons. Firstly, it seems that Metrolink's systems sometimes detects trams twice. This happens particularly often with double trams showing up on displays for a split second as a double tram following a single tram. We try detect and correct this where possible. But where a tram is directly behind another to the same destination, we might accidentally remove a real tram. Sorry about that!
In order to clear up cases where we've inferred tram locations incorrectly, we get rid of trams that are taking too long to get to the next stop and look like false readings in our software. If there are disruptions and trams stop moving on part or all of the network for an extended period, they might hit this timeout and drop off of our lists. They should re-appear when things start moving again and they reach the next stop.
TfGM makes the data that drives the displays at the tram stops available for free to developers that want to use it (Thank you, TfGM!). We use this data to estimate which stops trams are between or at.
We track when each tram arrives/departs a station. We can do this to the nearest 10secs which is the update rate of the data we get from TfGM. We use this to keep a running average of dwell times at stops and transit times between stops. This running average gets us a little bit more accurate than the displays at the stops and allows our estimates to adapt to traffic or temporary speed restrictions where Metrolink's predictions don't.
Unfortunately, TfGM don't provide live data for which route trams are taking through the city. So we take an educated guess based on which destinations trams are currently heading to via each route. If trams suddenly move to the other City Crossing because of disruptions or if we don't get the data to make the right guess then we might get it wrong on the odd occasion. Sorry ☹.
I change trams at Cornbrook on my daily commute. When I stand on the "outbound" platform, trams can be going to East Didsbury, Manchester Airport, Altrincham, MediaCityUK, Eccles and sometimes even Trafford Bar. But there's only 3 spaces on the display for trams. You're not able to see the next tram to all of the possible destinations. I wanted to be able to see the next few trams to each destination so I put some of my spare time into making a website that does just that.
I also get fed up of some stops saying trams were due in 4mins on the Metrolink app and stop displays then jumping strait to arriving...
Cool! If it's not one of the known ones above, please let me know on GitHub
Maybe. I can't guarantee it given this is something I created and maintain in my spare time. But you can always let me know what features you'd like to see on GitHub
Sure! But please run your own copy on your own server. The API is available on Github.