GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T22:16:07Z,
for the dataset file:///shared/mountainridestransportationauthoritymrta.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 17
  • Routes: 8
  • Shapes: 8
  • Stops: 172
  • Trips: 155

Specification Compliance report

36 notices reported (12 errors, 24 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 3

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
31 "TL-2068" "TL-107" 32 "TL-2069" "TL-107" "Red_02" "20250114"
32 "TL-2069" "TL-107" 33 "TL-2070" "TL-107" "Red_02" "20250114"
33 "TL-2070" "TL-107" 34 "TL-2071" "TL-107" "Red_02" "20250114"
duplicate_key ERROR 8

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"stop_times.txt" 2604 2605 "trip_id,stop_sequence" "TL-1849,270"
"stop_times.txt" 2647 2648 "trip_id,stop_sequence" "TL-1850,270"
"stop_times.txt" 2690 2691 "trip_id,stop_sequence" "TL-1851,270"
"stop_times.txt" 2733 2734 "trip_id,stop_sequence" "TL-1852,270"
"stop_times.txt" 2776 2777 "trip_id,stop_sequence" "TL-1853,270"
"stop_times.txt" 2819 2820 "trip_id,stop_sequence" "TL-1854,270"
"stop_times.txt" 2862 2863 "trip_id,stop_sequence" "TL-1855,270"
"stop_times.txt" 2905 2906 "trip_id,stop_sequence" "TL-1856,270"
stop_time_with_arrival_before_previous_departure_time ERROR 1

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
4718 4717 "TL-2084" "10:02:00" "10:28:00"
fast_travel_between_far_stops WARNING 8

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.
60 "TL-2123" "TL-17" 1985.631000581268 33.0938500096878 5595 1 "TL-112" "Clover & Gannett" "00:00:00" 5628 400 "TL-42" "Sun Valley - Dollar Circle" "00:00:00"
154 "TL-1915" "TL-3" 150.6368344210708 10.042455628071385 2920 1 "TL-57" "Warm Springs Base Area" "00:00:00" 2949 300 "TL-86" "Elkhorn Rd & Blue Grouse" "00:03:00"
155 "TL-1916" "TL-3" 150.6368344210708 10.042455628071385 2976 1 "TL-57" "Warm Springs Base Area" "00:00:00" 3005 300 "TL-86" "Elkhorn Rd & Blue Grouse" "00:03:00"
46 "TL-2084" "TL-17" 851.1051050735879 14.185085084559798 4715 520 "TL-44" "St Luke’s Hospital" "10:16:00" 4718 550 "TL-118" "Main & Myrtle" "10:02:00"
53 "TL-2092" "TL-17" 1985.631000581268 33.0938500096878 5133 1 "TL-112" "Clover & Gannett" "11:00:00" 5166 400 "TL-42" "Sun Valley - Dollar Circle" "11:00:00"
71 "TL-2141" "TL-17" 1985.631000581268 33.0938500096878 6321 1 "TL-112" "Clover & Gannett" "11:00:00" 6354 400 "TL-42" "Sun Valley - Dollar Circle" "11:00:00"
34 "TL-2071" "TL-10" 613.0840933183554 10.21806822197259 3972 150 "TL-70" "Main & 4th (Wells Fargo-Downtown Ketchum)" "12:40:00" 3991 6000 "TL-82" "Elkhorn Springs" "12:40:00"
54 "TL-2093" "TL-17" 1985.631000581268 33.0938500096878 5199 1 "TL-112" "Clover & Gannett" "14:45:00" 5232 400 "TL-42" "Sun Valley - Dollar Circle" "14:45:00"
missing_recommended_field WARNING 8

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 1

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "2nd & 6th" 88
stop_has_too_many_matches_for_shape WARNING 5

stop_has_too_many_matches_for_shape

Stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt.

This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. matchCount (?) The number of matches for the stop that is referred to.
96 "TL-7" "TL-1636" 426 "TL-137" "Baldy View Circle (Sun Valley Lodge)" [43.695456281136664,-114.35363] 31
96 "TL-7" "TL-1636" 428 "TL-137" "Baldy View Circle (Sun Valley Lodge)" [43.695456281136664,-114.35363] 31
96 "TL-7" "TL-1636" 447 "TL-137" "Baldy View Circle (Sun Valley Lodge)" [43.695456281136664,-114.35363] 31
114 "TL-3" "TL-1816" 858 "TL-75" "Baldy View Circle - Sun Valley Village" [43.69547662261408,-114.35329000000002] 26
114 "TL-3" "TL-1816" 875 "TL-92" "Baldy View Circle - Sun Valley Village" [43.695440000000005,-114.35363] 21
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.
36 "TL-17" "TL-2073" 4012 "TL-113" "Main @ Valley Ctry Store" [43.457640281472905,-114.25779774833848] 4011 "TL-112" "Clover & Gannett" [43.45277,-114.25352000000001]