Search
  1. Home
  2. United States Feeds
  3. knox-county-transit
  4. Source Data Validation Report

knox-county-transit — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T21:05:20Z,
for the dataset file:///shared/knox-county-transit_a86b27f6.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
Knox County Transit
Feed Email:
transit@knoxcounty.org
Feed Language:
English
Feed Start Date:
2023-01-01
Feed End Date:
2025-12-31

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: 0
  • Routes: 6
  • Shapes: 6
  • Stops: 17
  • Trips: 73

Specification Compliance report

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

Notice Code Severity Total
duplicate_key ERROR 9

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"stops.txt" 3 4 "stop_id" "4311"
"stops.txt" 3 8 "stop_id" "4311"
"stops.txt" 9 10 "stop_id" "5932"
"stops.txt" 15 16 "stop_id" "4032"
"stops.txt" 20 21 "stop_id" "10915"
"stops.txt" 9 24 "stop_id" "5932"
"stops.txt" 9 25 "stop_id" "5932"
"stops.txt" 2 26 "stop_id" "21039"
"stops.txt" 2 27 "stop_id" "21039"
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 "20260509" "20251231" "20260516"
route_long_name_contains_short_name WARNING 3

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`.
"2" 2 "Coshocton Express" "Coshocton Express Route"
"3" 3 "Round Hill" "Round Hill Route"
"6" 4 "Progress" "Progress Loop"
route_short_name_too_long WARNING 1

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"2" 2 "Coshocton Express"
unusable_trip WARNING 2

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
67 "1b_5"
74 "1c_7"