GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T13:35:07Z,
for the dataset file:///shared/kats_c60cb031.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-02
Feed End Date:
2026-12-31

Files included


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

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 5
  • Stops: 183
  • Trips: 5

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 "102054-40080" "Kingsport Area Transit Service" "en-US" "en"
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
2 "102054-Route_1" "102054-10240726" 56 "102054-3680881" "Transit Office" [36.540423441496586,-82.55296124318654] 55 "102054-3681054" "E Main @ Broad" [36.54507425513691,-82.56187489277647]