GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T01:27:53Z,
for the dataset file:///shared/syncromatics-mct_76ebcc71.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2026-03-17
Feed End Date:
2027-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 139
  • Routes: 23
  • Shapes: 112
  • Stops: 1228
  • Trips: 1595

Specification Compliance report

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

Notice Code Severity Total
feed_info_lang_and_agency_lang_mismatch WARNING 1

feed_info_lang_and_agency_lang_mismatch

Mismatching feed and agency language fields.

Files agency.txt and feed_info.txt should define matching agency.agency_lang and feed_info.feed_lang. The default language may be multilingual for datasets with the original text in multiple languages. In such cases, the feed_lang field should contain the language code mul defined by the norm ISO 639-2.

  • If feed_lang is not mul and does not match with agency_lang, that's an error.
  • If there is more than one agency_lang and feed_lang isn't mul, that's an error.
  • If feed_lang is mul and there isn't more than one agency_lang, that's an error.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. agencyId (?) The agency id of the faulty record. agencyName (?) The agency name of the faulty record. agencyLang (?) The agency language of the faulty record. feedLang (?) The feed language of the faulty record.
2 "105094-250" "Madisoncounty" "en-US" "en"
mixed_case_recommended_field WARNING 1

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" "IL 162 & IL 159" 945