GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T23:11:13Z,
for the dataset file:///shared/concord.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Concord Kannapolis Area Transit

Feed Info

Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2025-11-25
Feed End Date:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 20
  • Routes: 9
  • Shapes: 18
  • Stops: 280
  • Trips: 375

Specification Compliance report

422 notices reported (0 errors, 419 warnings, 3 infos)

Notice Code Severity Total
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 1

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.
"feed_info.txt" 2 "feed_end_date"
mixed_case_recommended_field WARNING 379

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 379 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.
"routes.txt" "route_short_name" "CCX AM" 9
"routes.txt" "route_long_name" "CCX AM" 9
"routes.txt" "route_short_name" "CCX PM" 10
"routes.txt" "route_long_name" "CCX PM" 10
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 2
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 3
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 4
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 5
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 6
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 7
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 8
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 9
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 10
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 11
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 12
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 13
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 14
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 15
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 16
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 17
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 18
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 19
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 20
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 21
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 22
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 23
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 24
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 25
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 26
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 27
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 28
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 29
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 30
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 31
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 32
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 33
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 34
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 35
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 36
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 37
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 38
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 39
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 40
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 41
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 42
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 43
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 44
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 45
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 46
"trips.txt" "trip_headsign" "BLUE ROUTE 1" 47
route_long_name_contains_short_name WARNING 3

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`.
"6732" 7 "RED" "Red Route"
"6748" 9 "CCX AM" "CCX AM"
"6749" 10 "CCX PM" "CCX PM"
same_name_and_description_for_route WARNING 7

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`.
2 "6726" "Blue Route" "route_long_name"
3 "6728" "Brown Route" "route_long_name"
4 "6729" "Green Route" "route_long_name"
5 "6730" "Orange Route" "route_long_name"
6 "6731" "Purple Route" "route_long_name"
7 "6732" "Red Route" "route_long_name"
8 "6733" "Yellow Route" "route_long_name"
stop_without_stop_time WARNING 3

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
41 "10727872" "MLK Jr Ave & Denver St"
42 "10727873" "A.L. Brown High School"
43 "10727874" "MLK Jr Ave & Ridge Ave"
trip_distance_exceeds_shape_distance_below_threshold WARNING 25

trip_distance_exceeds_shape_distance_below_threshold

The distance between the last shape point and last stop point is greater than 0 but less than the 11.1m threshold.

You can see more about this notice here.

tripId (?) The faulty record's trip id. shapeId (?) The faulty record's shape id. maxTripDistanceTraveled (?) The faulty record's trip max distance traveled. maxShapeDistanceTraveled (?) The faulty record's shape max distance traveled. geoDistanceToShape (?) The distance in meters between the shape and the stop.
"Blue 10" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 12" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 14" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 16" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 18" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 2" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 20" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 22" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 24" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 26" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 28" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 4" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 6" "27112" 15228.754954348653 15228.69969483869 0.0
"Blue 8" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-10" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-12" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-14" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-16" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-18" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-2" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-20" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-22" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-4" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-6" "27112" 15228.754954348653 15228.69969483869 0.0
"BluWKND-8" "27112" 15228.754954348653 15228.69969483869 0.0
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"