GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T16:42:08Z,
for the dataset file:///shared/linktransit_c455034e.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2026-06-14
Feed End Date:
2027-07-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_attributes.txt
  4. calendar_dates.txt
  5. directions.txt
  6. feed_info.txt
  7. realtime_routes.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 10
  • Routes: 5
  • Shapes: 10
  • Stops: 200
  • Trips: 163

Specification Compliance report

173 notices reported (0 errors, 170 warnings, 3 infos)

Notice Code Severity Total
mixed_case_recommended_field WARNING 164

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 164 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.
"agency.txt" "agency_name" "LINK TRANSIT" 2
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 2
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 3
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 4
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 5
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 6
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 7
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 8
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 9
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 10
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 11
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 12
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 13
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 14
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 15
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 16
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 17
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 18
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 19
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 20
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 21
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 22
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 23
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 24
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 25
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 26
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 27
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 28
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 29
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 30
"trips.txt" "trip_headsign" "3 GIBSONVILLE/HARPER SR CTR VIA ELON & CHURCH ST" 31
"trips.txt" "trip_headsign" "3 DOWNTOWN BURLINGTON VIA CHURCH ST & ELON" 32
"trips.txt" "trip_headsign" "1 ALAMANCE REGIONAL MEDICAL CTR VIA S. MEBANE ST" 33
"trips.txt" "trip_headsign" "1 DOWNTOWN BURLINGTON VIA S. MEBANE ST" 34
"trips.txt" "trip_headsign" "4 NORTH PARK LIBRARY 3 VIA W. DAVIS ST" 35
"trips.txt" "trip_headsign" "4 DOWNTOWN BURLINGTON VIA W. DAVIS ST" 36
"trips.txt" "trip_headsign" "2 ALAMANCE COMMUNITY COL 2 VIA MAPLE/HARDEN ST" 37
"trips.txt" "trip_headsign" "2 DOWNTOWN BURLINGTON 2 VIA MAPLE/HARDEN STS" 38
"trips.txt" "trip_headsign" "4 DOWNTOWN BURLINGTON VIA W. DAVIS ST" 39
"trips.txt" "trip_headsign" "2 ALAMANCE COMMUNITY COL 2 VIA MAPLE/HARDEN ST" 40
"trips.txt" "trip_headsign" "2 DOWNTOWN BURLINGTON 2 VIA MAPLE/HARDEN STS" 41
"trips.txt" "trip_headsign" "4 NORTH PARK LIBRARY 3 VIA W. DAVIS ST" 42
"trips.txt" "trip_headsign" "4 DOWNTOWN BURLINGTON VIA W. DAVIS ST" 43
"trips.txt" "trip_headsign" "2 ALAMANCE COMMUNITY COL 2 VIA MAPLE/HARDEN ST" 44
"trips.txt" "trip_headsign" "2 DOWNTOWN BURLINGTON 2 VIA MAPLE/HARDEN STS" 45
"trips.txt" "trip_headsign" "4 NORTH PARK LIBRARY 3 VIA W. DAVIS ST" 46
"trips.txt" "trip_headsign" "4 DOWNTOWN BURLINGTON VIA W. DAVIS ST" 47
"trips.txt" "trip_headsign" "4 NORTH PARK LIBRARY 3 VIA W. DAVIS ST" 48
"trips.txt" "trip_headsign" "4 DOWNTOWN BURLINGTON VIA W. DAVIS ST" 49
"trips.txt" "trip_headsign" "2 ALAMANCE COMMUNITY COL 2 VIA MAPLE/HARDEN ST" 50
route_long_name_contains_short_name WARNING 5

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"5867" 2 "1 Red" "1 Red"
"5881" 3 "2 Orange" "2 Orange"
"5882" 4 "3 Blue" "3 Blue"
"5883" 5 "4 Green" "4 Green"
"5884" 6 "5 Purple" "5 Purple"
same_name_and_description_for_route WARNING 1

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
6 "5884" "5 Purple" "route_short_name"
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"realtime_routes.txt"
"directions.txt"