GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:24:25Z,
for the dataset file:///shared/mid-county.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Town & Country Transit
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2025-06-23
Feed End Date:
2026-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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 6
  • Routes: 3
  • Shapes: 20
  • Stops: 35
  • Trips: 74

Specification Compliance report

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

Notice Code Severity Total
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 2

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" "BC3 OB" 35
"stops.txt" "stop_name" "BC3 IB" 36
stop_too_far_from_shape_using_user_distance WARNING 6

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.
35 "124_shp" "t330-b1-sl2" 51 "33" "Valley View" [40.786427999999994,-79.514913] 143.19267390430048
46 "116_shp" "t34D-b3-sl3" 83 "10" "Career Link" [40.81672499999999,-79.48999] 117.04079863690119
46 "116_shp" "t34D-b3-sl3" 84 "33" "Valley View" [40.786427999999994,-79.514913] 143.19267390430048
36 "136_shp" "t3E8-b1-sl2" 148 "33" "Valley View" [40.786427999999994,-79.514913] 143.19267390430048
45 "117_shp" "t320-b3-sl3" 47 "33" "Valley View" [40.786427999999994,-79.514913] 143.19267390430048
42 "115_shp" "t285-b1-sl3" 4 "33" "Valley View" [40.786427999999994,-79.514913] 143.19267390430048