Leipzig Tram Delays

Info Contact

Data Availability

Count of available data points over the last 365 days

Highscores

Data of current delays of the last 12h.
This data is updated every 24 hours, around 3:00 UTC+2! For further details check the Info on top!

Datapoints: 0 Avg. Delay (min): 0.0

Worst Line: Null Worst District: Null Worst Stop: Null

Local Delays

Local delays for different spatial and time resolution.
This data is updated every 24 hours, around 3:00 UTC+2! Some individual stops or district may not appear on the map due to the random sampling methodology. For further details check the Info on top!
Stops Districts
last Day last Week last Month last Year

Overall Averages

Averaged delays for different temporal partitioning.
Hourly Daily Weekly Monthly Quarter

Specific Line

Avereage Delay per Tram Line over the last Month
1 2 3 4 7 8 9 10 11 12 14 15 16
×

Methodological Information

General

The data in this dashboard is acquired via automated browser-based requests of the INSA web app. The corresponding robots.txt allows to do so. But for feasibility reasons the amount of requests, thus the amount of information sampled each day is limited to a reasonable size. This means that the time and location coverage of the data is incomplete. Thus, the results presented in the dashboard should be treated with the neccessary caution.

Queries

The process of retrieving the data is as follows: For each query a connection to the website, yielding the timetable information, is established. Each query chooses one of the tram stops in the city, where stops are chosen uniformely at random to provide an even spatial coverage of the data. The departures information is then requested with the corresponding stop, which yields a list of upcoming departures from that stop or station. These are ordered by their departure time, taking into account the current estimated delay. The dashboard currently only takes includes tram departures. The current date and time of query, delay, scheduled time, tram line number and station name then get extracted and stored in a database which provides efficient and parallel write-read access.

Restrictions

Between 1.30 and 4.30 local time no data is collected. Most of the trams are not operating during this time. The presented data is filtered based on the creteria which the user can input in the corresponding dropdown menus. In some queries to the insa app no delay information is present, these are filtered out. Further, to provide reasonable precision of the results, a maximum time window of 3 minutes between the time of the query and the scheduled time of the tram is allowed, under the assumption that the closer the scheduled departure is to the time of query the more precise the delay information is. Regarding the delay percentages a tram is considered delayed if there is more than 1 minute delay, which may seem strict, but given that most people have to change to another tram or bus to reach their destination, this is a pragmatic choice.

Future Plans

  • speed up db queries
  • improve UI
  • add field for percentage of delayed rides
  • enrich data set with additional information like weather and roadworks
×

Contact

Author

Martin Schirmer

Year

2023/2024

Web

mschirmer.info

×