GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T14:55:26Z,
for the dataset file:///shared/butler-county.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-01-20
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: 29
  • Routes: 13
  • Shapes: 31
  • Stops: 524
  • Trips: 413

Specification Compliance report

327 notices reported (0 errors, 324 warnings, 3 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 272

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

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

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"24872" 162 501.18486891269157 9 161 501.18486891269157 8
"24872" 167 646.8636793609594 14 166 646.8636793609594 13
"24872" 172 902.905146710749 19 171 902.905146710749 18
"24872" 177 1166.3448283632488 24 176 1166.3448283632488 23
"24872" 182 1362.5092807898209 29 181 1362.5092807898209 28
"24872" 186 1521.5088209796347 33 185 1521.5088209796347 32
"24872" 190 1639.2026184079975 37 189 1639.2026184079975 36
"24872" 194 1800.4160441328863 41 193 1800.4160441328863 40
"24872" 197 1946.6258601092438 44 196 1946.6258601092438 43
"24872" 200 2089.823694967361 47 199 2089.823694967361 46
"24872" 204 2258.472003120118 51 203 2258.472003120118 50
"24872" 207 2404.496203224463 54 206 2404.496203224463 53
"24872" 211 2596.5658646613633 58 210 2596.5658646613633 57
"24872" 215 2741.3235272616234 62 214 2741.3235272616234 61
"24872" 241 4529.807646034434 88 240 4529.807646034434 87
"24872" 249 4859.945951340173 96 248 4859.945951340173 95
"24872" 256 5165.70247417046 103 255 5165.70247417046 102
"24872" 265 5618.089543394059 112 264 5618.089543394059 111
"24872" 279 6281.381349131216 126 278 6281.381349131216 125
"24872" 282 6367.654522027706 129 281 6367.654522027706 128
"24872" 290 6731.70141150938 137 289 6731.70141150938 136
"24872" 293 6808.568123548019 140 292 6808.568123548019 139
"24872" 299 7063.97808536705 146 298 7063.97808536705 145
"24872" 304 7320.224856181734 151 303 7320.224856181734 150
"24872" 310 7727.786749992639 157 309 7727.786749992639 156
"24872" 315 7980.709200711554 162 314 7980.709200711554 161
"24872" 325 8553.901991229193 172 324 8553.901991229193 171
"24872" 363 10530.19032235914 210 362 10530.19032235914 209
"24872" 367 10794.198194514714 214 366 10794.198194514714 213
"24872" 378 11576.074377963996 225 377 11576.074377963996 224
"24872" 381 11707.597452265336 228 380 11707.597452265336 227
"24872" 384 11807.0684175971 231 383 11807.0684175971 230
"24872" 388 12011.677084160376 235 387 12011.677084160376 234
"24872" 391 12116.628331499407 238 390 12116.628331499407 237
"24872" 395 12278.685218796849 242 394 12278.685218796849 241
"24872" 399 12443.1845417453 246 398 12443.1845417453 245
"29604" 7087 6841.847582614496 60 7086 6841.847582614496 59
"29604" 7098 7279.502566396527 71 7097 7279.502566396527 70
"29604" 7110 7722.050530432571 83 7109 7722.050530432571 82
"29604" 7133 8736.987125732241 106 7132 8736.987125732241 105
"29604" 7170 10859.141288994584 143 7169 10859.141288994584 142
"29604" 7191 14342.91460862164 164 7190 14342.91460862164 163
"29604" 7244 17035.999533083046 217 7243 17035.999533083046 216
"29604" 7307 19962.331984189776 280 7306 19962.331984189776 279
"29604" 7446 27257.443998386334 419 7445 27257.443998386334 418
"29604" 7555 36131.91148588655 528 7554 36131.91148588655 527
"29604" 7559 36306.51869168284 532 7558 36306.51869168284 531
"29967" 8743 11886.862202749327 176 8742 11886.862202749327 175
"29967" 8913 20351.341789514187 346 8912 20351.341789514187 345
"29967" 8938 21412.80230521286 371 8937 21412.80230521286 370
leading_or_trailing_whitespaces WARNING 2

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" 7 "route_short_name" "R3 "
"routes.txt" 8 "route_short_name" "R6 "
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 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" "TJ MAX" 485
route_color_contrast WARNING 2

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"5635" 5 "#D4DB12" "#FFFFFF"
"6753" 13 "#FCD900" "#FFFFFF"
route_long_name_contains_short_name WARNING 7

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`.
"5635" 5 "R1" "R1 - Hamilton/Middletown Shuttle"
"5638" 7 "R3" "R3 - Oxford-Forest Park Connector"
"5640" 8 "R6" "R6 - Job Connector"
"6750" 11 "O1" "O1"
"6752" 12 "O2" "O2"
"6753" 13 "O3" "O3"
"6754" 14 "O4" "O4"
same_name_and_description_for_route WARNING 9

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`.
5 "5635" "R1 - Hamilton/Middletown Shuttle" "route_long_name"
7 "5638" "R3 - Oxford-Forest Park Connector" "route_long_name"
8 "5640" "R6 - Job Connector" "route_long_name"
9 "6067" "CincyLink" "route_long_name"
10 "6734" "CincyLink Express" "route_long_name"
11 "6750" "O1" "route_short_name"
12 "6752" "O2" "route_short_name"
13 "6753" "O3" "route_short_name"
14 "6754" "O4" "route_short_name"
stop_without_stop_time WARNING 1

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.
45 "11186807" "Chestnut Street Station"
trip_distance_exceeds_shape_distance_below_threshold WARNING 28

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.
"SaIO3O3 IB1220" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1305" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1350" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1435" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1520" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1605" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1650" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1735" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1820" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1905" "29960" 6542.019635609058 6542.01097183993 0.0
"SaIO3O3 IB1950" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB0720" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB0805" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB0850" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB0935" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1020" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1105" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1150" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1235" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1320" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1405" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1450" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1535" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1620" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1705" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1750" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1835" "29960" 6542.019635609058 6542.01097183993 0.0
"WkIO3O3 IB1920" "29960" 6542.019635609058 6542.01097183993 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"