Helsinki Transit Live
Real-time locations of Helsinki Region Transport (HSL) public transport vehicles.
The realtime data comes from the Digitransit HSL MQTT API, which is a "work in progress", "very likely to change in the near future" and "there might be mysterious bugs lurking in the data". At least some of the tram numbers are wrong, so if you use trams, you might want to check them all on the filters page.
The line filter page in Helsinki Transit Live lists all HSL lines, but realtime data is actually available only for an unknown part of them. New HSL ticket and information systems (to be updated late 2016?) will improve both the coverage and the update frequency of realtime data. See the web interface for a look at the current coverage.
Source code and issue tracker are available at GitHub. Discussion at TMO.
Screenshots:
Category:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 harbour-helsinki-transit-live-1.4-1.noarch.rpm | 200.57 KB | 04/08/2016 - 21:53 |
| harbour-helsinki-transit-live-1.4.205-1.noarch.rpm | 200.58 KB | 30/11/2016 - 23:40 |
| harbour-helsinki-transit-live-1.4.210-1.noarch.rpm | 201.03 KB | 16/02/2017 - 00:40 |
| harbour-helsinki-transit-live-1.5-1.noarch.rpm | 201.88 KB | 01/11/2017 - 23:12 |
| harbour-helsinki-transit-live-1.6-1.noarch.rpm | 203.54 KB | 17/06/2018 - 18:08 |
Comments
AnttiT
Fri, 2016/04/22 - 22:48
Permalink
Am I the only one not seeing any vehicles after the latest update? Even the settings page ends up into a never ending loading. All I see is a map.
otsaloma
Tue, 2016/04/26 - 23:07
Permalink
API works again. Connection errors handled more gracefully in version 1.3.1.
otsaloma
Fri, 2016/04/22 - 23:26
Permalink
That new API seems to currently return "ConnectionRefusedError: [Errno 111] Connection refused". There's no proper error handling in Helsinki Transit Live yet, because I haven't used MQTT before and I don't know what kinds of errors can happen. Now that I see this error, I'll add some kind of error handling. The API remains unstable though, no guarantees about anything.
AnttiT
Tue, 2016/01/26 - 09:27
Permalink
How can I access the settings of the app?
otsaloma
Tue, 2016/01/26 - 22:00
Permalink
There are no settings. What would you want to set?
AnttiT
Sat, 2016/01/30 - 21:58
Permalink
Somehow I thought the app would be able show also busses, and therefore was looking for a setting to choose the vehicle type.
otsaloma
Sat, 2016/01/30 - 23:18
Permalink
Currently we're using the HSL Live API, which only shown trams and metro. It's the same as the official web interface: http://live.mattersoft.fi/hklkartta/
New APIs are coming in 2016, which should show buses and trains as well (at least some of them), but it's not yet documented or stable. There's a demo website available, which uses some development version of the upcoming API: http://dev.hsl.fi/live/
AnttiT
Mon, 2016/02/01 - 23:10
Permalink
So Jollaopas uses some other API, then?
otsaloma
Mon, 2016/02/01 - 23:24
Permalink
Based on a quick look at the source code it uses http://dev.hsl.fi/siriaccess/vm/json i.e. the SIRI VM JSON API, which is as the URL implies a development API, which might not be ready for production use. I can't find any documentation for that and at dev.hsl.fi they also list an MQTT API for vehicle locations -- I don't know which, if either of those, is the one that's going to be the final production API.
Marchusch
Sun, 2015/05/10 - 20:22
Permalink
Simple, straightforward and works well, just the way I like it. Could use options for selecting which lines to show and maybe for displaying their routes and stops etc. Also, tram lines 2 and 3 seem to get mixed up but I can imagine it's tricky since the number changes halfway round the loop. All in all very nice!
otsaloma
Sun, 2015/05/10 - 20:48
Permalink
HSL seems to have a new API in the works for vehicle locations, which would show also buses and trains (see Live map). Once that's stable, documented and ready for use, I'll consider adding features, since they make more sense when there's more stuff to show.
That occasional tram 2/3 confusion is in the data provided by the API. There's also sometimes some trams missing, which is probably a bigger problem.