Why am I seeing duplicate trips in the Run Times module?


When using the Run Times module, there may be some cases in which you will see trips that appear to be duplicate – sharing the same starting time. This article explains why that may be the case, and how to prevent this (if desired). 


Why "duplicate" trips?

Within the Analysis tab of the Run Times module, each row of the graphs you're viewing represent a unique Trip ID, as defined in the GTFS data file. 

This means that if there are identical trips with different Trip IDs, they will be separated into distinct rows.

For example, in the image below, there are six different rows for trips departing at 8:07. This is because the GTFS data for this agency had different IDs for the same trips on different days of the week and throughout the period of time that was selected for this report. 





How to prevent "duplicate" trips (identical start times)? 

Preventing the Run Times graphs from showing trips with duplicate start times may require changing the date and time range filters:

  • Change days of week:  try selecting only weekdays – or a certain day/days of the week – to filter out trips that have the same start time but are part of a weekend/weekday service. 
  • Change date range: narrowing your date range may filter out "older" trips with identical start times from the chart.

To prevent these issues in the future, you might consider updating the GTFS data to give trips with the same start time the same trip ID (which may in turn require adjusting GTFS services and calendars). 

0 out of 0 found this helpful



Please sign in to leave a comment.