Shown below is the default KPI for measuring Distance run, if no customisation has been requested.
The Distance run KPI measures the number of miles (or kilometres) operated (actual distance) relative to those scheduled to be run (scheduled distance).
Mosaiq Insights calculates distance as the distance between stops, utilising the shape_dist_traveled field from your stop_times.txt or a shapes.txt GTFS file.
-
Scheduled distance is the distance between the first and last scheduled stops for a trip. In the example above, the scheduled distance is measured as the distance between stop A through to E (400m total).
-
Actual distance is the distance between the first observed stop and the last observed stop for a trip. The Distance run KPI tells you how much of the scheduled route was covered based on the stops we can confirm the bus reached, not the physical GPS path the vehicle took between stops. In the example above, the vehicle was not observed at stop A and E, therefore the actual distance is calculated as the shape distance from B through to D (200m total).
All distance metrics are calculated at the journey level and then rolled up to operator, service, and network level.
If you are not providing the shape_dist_traveled field with your GTFS upload, Mosaiq will use a derived shape to calculate the distance between stops. Refer to FAQs for how derived shapes are calculated.