GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T02:15:15Z,
for the dataset file:///shared/john_f8dc2e83.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Strategic Mapping Inc.
Publisher URL:
http://www.mapstrat.com
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-04-13
Feed End Date:
2027-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 45
  • Routes: 15
  • Shapes: 36
  • Stops: 615
  • Trips: 1740

Specification Compliance report

1043 notices reported (0 errors, 1043 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 3

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "72"
3 "71"
4 "70"
fast_travel_between_consecutive_stops WARNING 4

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
1737 "18377" "11" 346.2556481389272 5.770927468982119 75096 7 "424" "Crown St. & Hanover St." "16:09:00" 75097 8 "11513" "1050 Rothesay Road" "16:09:00"
1741 "19626" "11" 346.2556481389272 5.770927468982119 75204 7 "424" "Crown St. & Hanover St." "16:09:00" 75205 8 "11513" "1050 Rothesay Road" "16:09:00"
1734 "18378" "11" 346.2556481389272 5.770927468982119 75015 7 "424" "Crown St. & Hanover St." "17:19:00" 75016 8 "11513" "1050 Rothesay Road" "17:19:00"
1738 "19627" "11" 346.2556481389272 5.770927468982119 75123 7 "424" "Crown St. & Hanover St." "17:19:00" 75124 8 "11513" "1050 Rothesay Road" "17:19:00"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
mixed_case_recommended_field WARNING 1030

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 1030 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" "1W - LANCASTER CROSSING" 7
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 8
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 9
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 10
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 11
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 15
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 16
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 18
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 19
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 23
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 24
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 26
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 45
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 46
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 47
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 48
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 49
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 50
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 51
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 52
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 53
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 54
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 55
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 56
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 61
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 62
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 65
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 66
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 67
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 68
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 69
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 70
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 71
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 74
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 75
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 76
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 79
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 81
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 83
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 84
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 85
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 86
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 106
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 107
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 108
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 109
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 117
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 118
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 119
"trips.txt" "trip_headsign" "1W - LANCASTER CROSSING" 120
same_name_and_description_for_route WARNING 5

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 "13" "MARTINON" "route_long_name"
9 "4" "CRESCENT VALLEY" "route_long_name"
10 "15" "NORTH END" "route_long_name"
12 "1" "FOREST GLEN" "route_long_name"
16 "11" "KV COMEX" "route_long_name"