GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-16T20:21:17Z,
for the dataset file:///shared/tcat-ny-us.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Tompkins Consolidated Area Transit Inc

Feed Info

Publisher Name:
Tompkins Consolidated Area Transit Inc
Publisher URL:
http://tcatbus.com/
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-01-13
Feed End Date:
2026-07-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: 65
  • Routes: 25
  • Shapes: 152
  • Stops: 627
  • Trips: 5018

Specification Compliance report

49 notices reported (0 errors, 49 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 25

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.
"trips.txt" "trip_headsign" "IC via SHBP" 359
"trips.txt" "trip_headsign" "IC via SHBP" 362
"trips.txt" "trip_headsign" "IC via SHBP" 364
"trips.txt" "trip_headsign" "IC via SHBP" 366
"trips.txt" "trip_headsign" "IC via SHBP" 368
"trips.txt" "trip_headsign" "IC via SHBP" 403
"trips.txt" "trip_headsign" "IC via SHBP" 406
"trips.txt" "trip_headsign" "IC via SHBP" 408
"trips.txt" "trip_headsign" "IC via SHBP" 410
"trips.txt" "trip_headsign" "IC via SHBP" 412
"trips.txt" "trip_headsign" "IC via SHBP" 447
"trips.txt" "trip_headsign" "IC via SHBP" 450
"trips.txt" "trip_headsign" "IC via SHBP" 452
"trips.txt" "trip_headsign" "IC via SHBP" 454
"trips.txt" "trip_headsign" "IC via SHBP" 456
"trips.txt" "trip_headsign" "IC via SHBP" 491
"trips.txt" "trip_headsign" "IC via SHBP" 494
"trips.txt" "trip_headsign" "IC via SHBP" 496
"trips.txt" "trip_headsign" "IC via SHBP" 498
"trips.txt" "trip_headsign" "IC via SHBP" 500
"trips.txt" "trip_headsign" "IC via SHBP" 536
"trips.txt" "trip_headsign" "IC via SHBP" 539
"trips.txt" "trip_headsign" "IC via SHBP" 542
"trips.txt" "trip_headsign" "IC via SHBP" 544
"trips.txt" "trip_headsign" "IC via SHBP" 546
route_long_name_contains_short_name WARNING 23

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`.
"10" 2 "10" "10"
"11" 3 "11" "11"
"13" 4 "13" "13"
"14" 5 "14" "14"
"15" 6 "15" "15"
"17" 7 "17" "17"
"20" 8 "20" "20"
"21" 9 "21" "21"
"30" 10 "30" "30"
"31" 11 "31" "31"
"32" 12 "32" "32"
"36" 13 "36" "36"
"37" 14 "37" "37"
"40" 15 "40" "40"
"43" 16 "43" "43"
"51" 17 "51" "51"
"52" 18 "52" "52"
"65" 19 "65" "65"
"67" 20 "67" "67"
"81" 21 "81" "81"
"82" 22 "82" "82"
"90" 23 "90" "90"
"92" 24 "92" "92"