GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T15:31:22Z,
for the dataset file:///shared/calvert-county.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
MTI UMD
Publisher URL:
https://mti.umd.edu/
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2019-08-26
Feed End Date:
2021-08-26

Files included


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

Counts


  • Agencies: 1
  • Blocks: 16
  • Routes: 8
  • Shapes: 48
  • Stops: 137
  • Trips: 145

Specification Compliance report

349 notices reported (184 errors, 164 warnings, 1 infos)

Notice Code Severity Total
stop_time_timepoint_without_times ERROR 184

stop_time_timepoint_without_times

arrival_time or departure_time not specified for timepoint.

Any records with stop_times.timepoint set to 1 must define a value for stop_times.arrival_time and stop_times.departure_time fields.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id. stopSequence (?) The faulty record's `stops.stop_sequence`. specifiedField (?) Either `departure_time` or `arrival_time`.
6 "3315673" 4 "arrival_time"
6 "3315673" 4 "departure_time"
19 "3315662" 1 "arrival_time"
19 "3315662" 1 "departure_time"
76 "3315671" 3 "arrival_time"
76 "3315671" 3 "departure_time"
84 "3315672" 3 "arrival_time"
84 "3315672" 3 "departure_time"
96 "3315674" 6 "arrival_time"
96 "3315674" 6 "departure_time"
108 "3315675" 6 "arrival_time"
108 "3315675" 6 "departure_time"
120 "3315676" 6 "arrival_time"
120 "3315676" 6 "departure_time"
144 "3315678" 6 "arrival_time"
144 "3315678" 6 "departure_time"
156 "3315679" 6 "arrival_time"
156 "3315679" 6 "departure_time"
168 "3315680" 6 "arrival_time"
168 "3315680" 6 "departure_time"
180 "3315681" 6 "arrival_time"
180 "3315681" 6 "departure_time"
192 "3315682" 6 "arrival_time"
192 "3315682" 6 "departure_time"
216 "3315684" 6 "arrival_time"
216 "3315684" 6 "departure_time"
240 "3315686" 6 "arrival_time"
240 "3315686" 6 "departure_time"
264 "3315696" 6 "arrival_time"
264 "3315696" 6 "departure_time"
288 "3315698" 6 "arrival_time"
288 "3315698" 6 "departure_time"
312 "3315701" 6 "arrival_time"
312 "3315701" 6 "departure_time"
333 "3315687" 3 "arrival_time"
333 "3315687" 3 "departure_time"
342 "3315688" 3 "arrival_time"
342 "3315688" 3 "departure_time"
351 "3315689" 3 "arrival_time"
351 "3315689" 3 "departure_time"
360 "3315690" 3 "arrival_time"
360 "3315690" 3 "departure_time"
369 "3315692" 3 "arrival_time"
369 "3315692" 3 "departure_time"
956 "4948945" 5 "arrival_time"
956 "4948945" 5 "departure_time"
963 "4948945" 12 "arrival_time"
963 "4948945" 12 "departure_time"
964 "4948945" 13 "arrival_time"
964 "4948945" 13 "departure_time"
expired_calendar WARNING 5

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 "68130"
3 "68131"
4 "68132"
5 "68134"
6 "68133"
fast_travel_between_far_stops WARNING 3

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

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.
97 "3315759" "6" 179.4911851921332 11.96607901280888 1072 7 "103" "Ross Rd. and Broomes Island Rd." "10:30:00" 1075 10 "105" "Broomes Island Rd. and Grays Rd." "10:33:00"
100 "3315762" "6" 172.37209520377607 11.491473013585072 1116 4 "103" "Ross Rd. and Broomes Island Rd." "15:06:00" 1118 6 "105" "Broomes Island Rd. and Grays Rd." "15:09:00"
99 "3315761" "6" 329.5196031878876 10.983986772929585 1098 4 "91" "Broomes Island Rd. and Williams Wharf Rd." "13:33:00" 1101 7 "94" "Ross Rd." "13:34:00"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260123" "20210826" "20260130"
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
missing_recommended_field WARNING 8

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.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
mixed_case_recommended_field WARNING 144

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 144 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_short_name" "white-1" 2
"trips.txt" "trip_short_name" "white-1" 3
"trips.txt" "trip_short_name" "white-1" 4
"trips.txt" "trip_short_name" "white-1" 5
"trips.txt" "trip_short_name" "white-1" 6
"trips.txt" "trip_short_name" "white-1" 7
"trips.txt" "trip_short_name" "white-1" 8
"trips.txt" "trip_short_name" "white-1" 9
"trips.txt" "trip_short_name" "white-1" 10
"trips.txt" "trip_short_name" "white-1" 11
"trips.txt" "trip_short_name" "white-1" 12
"trips.txt" "trip_short_name" "white-1" 13
"trips.txt" "trip_short_name" "white-1" 14
"trips.txt" "trip_short_name" "white-1" 15
"trips.txt" "trip_short_name" "white-1" 16
"trips.txt" "trip_short_name" "white-1" 17
"trips.txt" "trip_short_name" "white-1" 18
"trips.txt" "trip_short_name" "white-1" 19
"trips.txt" "trip_short_name" "white-1" 20
"trips.txt" "trip_short_name" "white-1" 21
"trips.txt" "trip_short_name" "whtie-1" 22
"trips.txt" "trip_short_name" "white-1" 23
"trips.txt" "trip_short_name" "white-1" 24
"trips.txt" "trip_short_name" "white-1" 25
"trips.txt" "trip_short_name" "white-1" 26
"trips.txt" "trip_short_name" "white-1" 27
"trips.txt" "trip_short_name" "white-1" 28
"trips.txt" "trip_short_name" "white-1" 29
"trips.txt" "trip_short_name" "white-1" 30
"trips.txt" "trip_short_name" "white-1" 31
"trips.txt" "trip_short_name" "white-2" 32
"trips.txt" "trip_short_name" "white-2" 33
"trips.txt" "trip_short_name" "white-2" 34
"trips.txt" "trip_short_name" "white-1" 35
"trips.txt" "trip_short_name" "white-1" 36
"trips.txt" "trip_short_name" "white-1" 37
"trips.txt" "trip_short_name" "white-1" 38
"trips.txt" "trip_short_name" "white-2" 39
"trips.txt" "trip_short_name" "white-2" 40
"trips.txt" "trip_short_name" "white-2" 41
"trips.txt" "trip_short_name" "green-2" 42
"trips.txt" "trip_short_name" "green-2" 43
"trips.txt" "trip_short_name" "green-2" 44
"trips.txt" "trip_short_name" "green-2" 45
"trips.txt" "trip_short_name" "green-2" 46
"trips.txt" "trip_short_name" "green-2" 47
"trips.txt" "trip_short_name" "green-2" 48
"trips.txt" "trip_short_name" "green-1" 49
"trips.txt" "trip_short_name" "green-2" 50
"trips.txt" "trip_short_name" "green-2" 51
stop_too_far_from_shape WARNING 1

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.
49 "Green_S2_IB 169862" "3315711" 476 "4" "College of Southern Maryland" [38.53362,-76.59986] 683.7176238237796
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260123" "20190401" "20210726"
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"trips.txt" "block_name" 11