GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T19:09:37Z,
for the dataset file:///shared/city-norman.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:
2025-11-05
Feed End Date:
N/A

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: 14
  • Routes: 6
  • Shapes: 12
  • Stops: 134
  • Trips: 332

Specification Compliance report

136 notices reported (24 errors, 109 warnings, 3 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 24

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`.
"CLVR6-1966030" "5751266" 1051 396.72032546850306 1 1050 9009.606402289437 0
"CLVR6-2728070" "5751266" 2006 396.72032546850306 1 2005 9009.606402289437 0
"CLVR6-50030" "5751266" 4202 396.72032546850306 1 4201 9009.606402289437 0
"CLVR6-3911070" "5751266" 3064 396.72032546850306 1 3063 9009.606402289437 0
"CLVR6-1009030" "5751266" 3 396.72032546850306 1 2 9009.606402289437 0
"CLVR6-4917030" "5751266" 4123 396.72032546850306 1 4122 9009.606402289437 0
"CLVR6-111030" "5751266" 122 396.72032546850306 1 121 9009.606402289437 0
"CLVR6-1767030" "5751266" 815 396.72032546850306 1 814 9009.606402289437 0
"CLVR6-3614070" "5751266" 2787 396.72032546850306 1 2786 9009.606402289437 0
"CLVR6-2677030" "5751266" 1958 396.72032546850306 1 1957 9009.606402289437 0
"CLVR6-3942030" "5751266" 3115 396.72032546850306 1 3114 9009.606402289437 0
"CLVR6-4781070" "5751266" 3993 396.72032546850306 1 3992 9009.606402289437 0
"CLVR6-4483070" "5751266" 3645 396.72032546850306 1 3644 9009.606402289437 0
"CLVR6-3252070" "5751266" 2461 396.72032546850306 1 2460 9009.606402289437 0
"CLVR6-1138030" "5751266" 169 396.72032546850306 1 168 9009.606402289437 0
"CLVR6-873030" "5751266" 5077 396.72032546850306 1 5076 9009.606402289437 0
"CLVR6-101030" "5751266" 15 396.72032546850306 1 14 9009.606402289437 0
"CLVR6-5724030" "5751266" 4858 396.72032546850306 1 4857 9009.606402289437 0
"CLVR6-113070" "5751266" 157 396.72032546850306 1 156 9009.606402289437 0
"CLVR6-452070" "5751266" 3676 396.72032546850306 1 3675 9009.606402289437 0
"CLVR6-119030" "5751266" 219 396.72032546850306 1 218 9009.606402289437 0
"CLVR6-511030" "5751266" 4314 396.72032546850306 1 4313 9009.606402289437 0
"CLVR6-5067030" "5751266" 4289 396.72032546850306 1 4288 9009.606402289437 0
"CLVR6-550070" "5751266" 4692 396.72032546850306 1 4691 9009.606402289437 0
leading_or_trailing_whitespaces WARNING 5

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.
"stops.txt" 42 "stop_name" "36th NW/Havenbrook "
"stops.txt" 108 "stop_name" "Main/36th NW "
"stops.txt" 115 "stop_name" "Lindsey/McGee "
"stops.txt" 133 "stop_name" "University/Symmes st "
"routes.txt" 4 "route_long_name" "121 - Westheimer Airport "
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 58

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 58 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.
"stops.txt" "stop_name" "N PORTER AVE @ E MOSIER ST" 2
"stops.txt" "stop_name" "N PORTER AVE @ E HUGHBERT ST" 3
"stops.txt" "stop_name" "WEBSTER @ MAIN" 17
"stops.txt" "stop_name" "TRIAD VILLAGE DR @ K9 ST" 49
"stops.txt" "stop_name" "N SERVICE RD @ NE 27TH ST" 58
"stops.txt" "stop_name" "24th/HEMPHILL IB" 76
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 10
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 14
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 26
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 35
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 44
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 52
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 59
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 63
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 66
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 69
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 70
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 82
"trips.txt" "trip_headsign" "SOCIAL SECURITY" 87
"trips.txt" "trip_headsign" "SOCIAL SECURITY" 97
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 125
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 129
"trips.txt" "trip_headsign" "SOCIAL SECURITY" 130
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 133
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 141
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 149
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 150
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 153
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 159
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 160
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 166
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 168
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 181
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 207
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 219
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 224
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 233
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 239
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 253
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 258
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 264
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 267
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 276
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 282
"trips.txt" "trip_headsign" "WESTHEIMER AIRPORT" 283
"trips.txt" "trip_headsign" "SOCIAL SECURITY" 286
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 287
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 290
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 295
"trips.txt" "trip_headsign" "12 NE/ROCK CREEK RD" 296
route_long_name_contains_short_name WARNING 6

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`.
"6244" 2 "122" "122 - 12 NE/Rock Creek Rd"
"6250" 3 "112" "112 - W Lindsey/36 NW"
"6252" 4 "121" "121 - Westheimer Airport"
"6253" 5 "144" "144 - Social Security Express"
"6913" 6 "111" "111 - E Lindsey/Alameda"
"6915" 7 "110" "110 - Main St/24 NW"
stop_too_far_from_shape_using_user_distance WARNING 11

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.
2 "29295" "CLVR6-1009030" 2 "5751265" "Halley/Lexington - YMCA" [35.221362,-97.438854] 2972.8867134938814
2 "29295" "CLVR6-1009030" 3 "5751266" "Westheimer Terminal" [35.221362,-97.438854] 3293.594504160445
2 "29295" "CLVR6-1009030" 4 "5751085" "Goddard/Flood" [35.221362,-97.438854] 3487.8307112343373
2 "29295" "CLVR6-1009030" 5 "5751086" "Rock Creek/Industrial Blvd" [35.221362,-97.438854] 3408.792744354934
2 "29295" "CLVR6-1009030" 6 "5751087" "Rock Creek/Research Park" [35.221362,-97.438854] 3151.677973384897
2 "29295" "CLVR6-1009030" 7 "5751088" "Stebbeman/Rock Creek" [35.221362,-97.438854] 2975.7314644133808
2 "29295" "CLVR6-1009030" 8 "5751089" "Stubbeman/Lexington - Norman North High School" [35.221362,-97.438854] 2454.4126006757974
2 "29295" "CLVR6-1009030" 9 "5751090" "Stubbeman/Ridge Rd" [35.221362,-97.438854] 1888.9348057899256
2 "29295" "CLVR6-1009030" 10 "11463367" "N PORTER AVE @ E MOSIER ST" [35.221362,-97.438854] 1213.645296606719
2 "29295" "CLVR6-1009030" 11 "9152122" "Porter ave @ Frank st" [35.221362,-97.438854] 765.5137155790715
2 "29295" "CLVR6-1009030" 12 "11463368" "N PORTER AVE @ E HUGHBERT ST" [35.221362,-97.438854] 712.5952649910498
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.
127 "9152121" "Stubbeman/Terry"
trip_distance_exceeds_shape_distance_below_threshold WARNING 26

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.
"CLVR6-1009030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-101030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-111030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-113070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-1138030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-119030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-1767030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-1966030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-2312030" "22801" 21159.23227194918 21159.210074937368 0.0
"CLVR6-2677030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-2728070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-3252070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-3614070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-3911070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-3942030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-4483070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-452070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-4781070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-4917030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-50030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-5067030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-511030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-5281030" "22801" 21159.23227194918 21159.210074937368 0.0
"CLVR6-550070" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-5724030" "29295" 11998.6086150353 6105.21698188442 0.0
"CLVR6-873030" "29295" 11998.6086150353 6105.21698188442 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"