GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T17:53:52Z,
for the dataset file:///shared/mrtagtfs.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2023-01-16
Feed End Date:
2026-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. feed_info.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 11
  • Routes: 3
  • Shapes: 3
  • Stops: 92
  • Trips: 51

Specification Compliance report

4 notices reported (0 errors, 4 warnings, 0 infos)

Notice Code Severity Total
fast_travel_between_far_stops WARNING 3

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
38 "103412-1543" "103412-4" 188.74743407278498 31.4579056787975 1424 32 "103412-42" "Sun Valley - Dollar Circle" "12:50:00" 1455 63 "103412-135" "Main @ SV Bronze" "12:59:00"
51 "103412-1558" "103412-4" 1924.2774253094678 32.071290421824465 2224 0 "103412-112" "Clover & Gannett" "14:45:00" 2256 32 "103412-42" "Sun Valley - Dollar Circle" "14:45:00"
12 "103412-1383" "103412-4" 3284.7773665050854 54.74628944175142 432 0 "103412-112" "Clover & Gannett" "00:00:00" 479 47 "103412-24" "River & Bullion (Park and Ride) (Sb)" "00:00:00"
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
11 "103412-11" "103412-952" 419 "103412-13" "Airport (North entrance to airport)" [43.5070237607708,-114.3030418798942] 418 "103412-11" "Airport Way (South of Hailey Post Office)" [43.51185930203887,-114.30656879113555]