GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-06-11T17:39:56Z,
for the dataset file:///shared/cities-area-transit2_46412de7.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2026-04-23
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: 21
  • Routes: 16
  • Shapes: 15
  • Stops: 218
  • Trips: 365

Specification Compliance report

324 notices reported (26 errors, 295 warnings, 3 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 26

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

tripId (?) The id of the faulty trip. stopId (?) The id of the faulty stop. csvRowNumber (?) The row number from `stop_times.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. stopSequence (?) The faulty record's `stop_times.stop_sequence`. prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time. prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"36MF-21" "3981810" 2831 887.6461685641451 2 2830 887.6461685641451 1
"36MF-23" "3981810" 2879 887.6461685641451 2 2878 887.6461685641451 1
"36MF-11" "3981810" 2564 887.6461685641451 2 2563 887.6461685641451 1
"36MF-13" "3981810" 2612 887.6461685641451 2 2611 887.6461685641451 1
"36MF-15" "3981810" 2660 887.6461685641451 2 2659 887.6461685641451 1
"36MF-17" "3981810" 2708 887.6461685641451 2 2707 887.6461685641451 1
"36MF-19" "3981810" 2756 887.6461685641451 2 2755 887.6461685641451 1
"6SAT-18" "3981810" 4823 887.6461685641451 2 4822 887.6461685641451 1
"6SAT-14" "3981810" 4781 887.6461685641451 2 4780 887.6461685641451 1
"6SAT-16" "3981810" 4802 887.6461685641451 2 4801 887.6461685641451 1
"6SAT-20" "3981810" 4865 887.6461685641451 2 4864 887.6461685641451 1
"6SAT-10" "3981810" 4739 887.6461685641451 2 4738 887.6461685641451 1
"6SAT-12" "3981810" 4760 887.6461685641451 2 4759 887.6461685641451 1
"6SAT-4" "3981810" 4886 887.6461685641451 2 4885 887.6461685641451 1
"6SAT-2" "3981810" 4844 887.6461685641451 2 4843 887.6461685641451 1
"6SAT-8" "3981810" 4928 887.6461685641451 2 4927 887.6461685641451 1
"6SAT-6" "3981810" 4907 887.6461685641451 2 4906 887.6461685641451 1
"36MF-5" "3981810" 2948 887.6461685641451 2 2947 887.6461685641451 1
"36MF-7" "3981810" 2996 887.6461685641451 2 2995 887.6461685641451 1
"36MF-1" "3981810" 2516 887.6461685641451 2 2515 887.6461685641451 1
"36MF-3" "3981810" 2900 887.6461685641451 2 2899 887.6461685641451 1
"36MF-9" "3981810" 3044 887.6461685641451 2 3043 887.6461685641451 1
"623-2" "3981810" 4675 887.6461685641451 2 4674 887.6461685641451 1
"623-4" "3981810" 4691 887.6461685641451 2 4690 887.6461685641451 1
"623-6" "3981810" 4707 887.6461685641451 2 4706 887.6461685641451 1
"623-8" "3981810" 4723 887.6461685641451 2 4722 887.6461685641451 1
leading_or_trailing_whitespaces WARNING 4

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"routes.txt" 3 "route_short_name" "Route 7 "
"routes.txt" 10 "route_short_name" "Route 8 "
"routes.txt" 11 "route_short_name" "Route 9 "
"routes.txt" 13 "route_short_name" "Route 2 "
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 256

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 256 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" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 2
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 3
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 4
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 5
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 6
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 7
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 8
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 9
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 10
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 11
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 12
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 13
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 14
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 15
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 16
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 17
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 18
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 19
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 20
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 21
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 22
"trips.txt" "trip_headsign" "ROUTE 10 CHOICE HEALTH & FITNESS WALMART DOWNTOWN" 23
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 24
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 25
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 26
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 27
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 28
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 29
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 30
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 31
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 32
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 33
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 34
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 35
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 36
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 37
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 38
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 39
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 40
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 41
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 42
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 43
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 44
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 45
"trips.txt" "trip_headsign" "RED ROUTE 2 MIDTOWN DOWNTOWN 20TH ST HUGO'S" 46
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 47
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 48
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 49
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 50
"trips.txt" "trip_headsign" "ROUTE 1 UND CAMPUS STANFORD CENTER DOWNTOWN" 51
route_long_name_contains_short_name WARNING 14

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`.
"3971" 2 "Route 6" "Route 6"
"3972" 3 "Route 7" "Route 7"
"3973" 4 "Route 10" "Route 10"
"3976" 5 "Route 5" "Route 5"
"3981" 8 "Route 3" "Route 3"
"3982" 9 "Route 4" "Route 4"
"3983" 10 "Route 8" "Route 8"
"3984" 11 "Route 9" "Route 9"
"3987" 12 "Route 1" "Route 1"
"3988" 13 "Route 2" "Route 2"
"4947" 14 "UND Red Route" "UND Red Route"
"4949" 15 "UND Blue Route" "UND Blue Route"
"4950" 16 "UND Purple Route" "UND Purple Route"
"4983" 17 "UND Night Route" "UND Night Route"
route_short_name_too_long WARNING 4

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"4947" 14 "UND Red Route"
"4949" 15 "UND Blue Route"
"4950" 16 "UND Purple Route"
"4983" 17 "UND Night Route"
same_name_and_description_for_route WARNING 15

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 "3971" "Route 6" "route_short_name"
3 "3972" "Route 7" "route_short_name"
4 "3973" "Route 10" "route_short_name"
5 "3976" "Route 5" "route_short_name"
6 "3977" "Route 22" "route_long_name"
8 "3981" "Route 3" "route_short_name"
9 "3982" "Route 4" "route_short_name"
10 "3983" "Route 8" "route_short_name"
11 "3984" "Route 9" "route_short_name"
12 "3987" "Route 1" "route_short_name"
13 "3988" "Route 2" "route_short_name"
14 "4947" "UND Red Route" "route_short_name"
15 "4949" "UND Blue Route" "route_short_name"
16 "4950" "UND Purple Route" "route_short_name"
17 "4983" "UND Night Route" "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"