GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-24T00:26:14Z,
for the dataset file:///shared/wegopublic-transit.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. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts


  • Agencies: 1
  • Blocks: 261
  • Routes: 37
  • Shapes: 331
  • Stops: 1632
  • Trips: 12619

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 19

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "83.0.1"
3 "83.0.2"
4 "83.0.3"
8 "83.1.1"
9 "83.10.1"
10 "83.118.2"
11 "83.120.3"
12 "83.123.3"
13 "83.2.1"
14 "83.3.1"
15 "83.4.1"
16 "83.56.2"
17 "83.61.2"
18 "83.64.2"
19 "83.71.3"
20 "83.72.3"
21 "83.9.1"
22 "83.91.1"
23 "83.92.1"
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 7835

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.

Only the first 50 of 7835 affected records are displayed below.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 2
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 3
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 4
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 5
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 6
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 7
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 8
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 9
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 10
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 11
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 12
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 13
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 14
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 15
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 16
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 17
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 18
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 19
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 20
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 21
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 22
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 23
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 24
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 25
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 26
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 27
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 28
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 29
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 30
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 31
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 32
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 33
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 34
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 35
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 36
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 37
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 38
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 39
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 40
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 41
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 42
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 43
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 44
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 45
"trips.txt" "trip_headsign" "NORTH NASHVILLE VIA BUENA VISTA" 46
"trips.txt" "trip_headsign" "DOWNTOWN VIA BUENA VISTA" 47
"trips.txt" "trip_headsign" "DOWNTOWN VIA BUENA VISTA" 48
"trips.txt" "trip_headsign" "DOWNTOWN VIA BUENA VISTA" 49
"trips.txt" "trip_headsign" "DOWNTOWN VIA BUENA VISTA" 50
"trips.txt" "trip_headsign" "DOWNTOWN VIA BUENA VISTA" 51
stop_too_far_from_shape_using_user_distance WARNING 5

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

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. geoDistanceToShape (?) Distance from stop to shape.
835 "18770" "355643" 26910 "CXOWTBRG" "WHITE BRIDGE STATION OUTBOUND" [36.149058999999994,-86.85792] 138.66734513062306
835 "18770" "355643" 26911 "WHICHASF" "WHITE BRIDGE PIKE & CHARLOTTE SHONE" [36.15071,-86.857859] 171.04814989200713
2705 "18883" "359756" 89336 "MCSLB" "LEBANON STATION" [36.211310000000005,-86.29583] 153.06436330757427
6978 "19144" "369960" 234950 "WHICHASF" "WHITE BRIDGE PIKE & CHARLOTTE SHONE" [36.15071,-86.857859] 171.04814989200713
8884 "19271" "374358" 298772 "MCSLB" "LEBANON STATION" [36.211310000000005,-86.29583] 153.06436330757427
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.
835 "18770" "355643" 26911 "WHICHASF" "WHITE BRIDGE PIKE & CHARLOTTE SHONE" [36.1491790000639,-86.85792] 26910 "CXOWTBRG" "WHITE BRIDGE STATION OUTBOUND" [36.149985396032754,-86.85792658929843]
unused_shape WARNING 14

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"19101" 82427
"19103" 83608
"19128" 91788
"19129" 92175
"19133" 94038
"19165" 104200
"19168" 105159
"19209" 116336
"19212" 117988
"19252" 135407
"19254" 137271
"19260" 142164
"19262" 144105
"19274" 152902