GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T18:51:54Z,
for the dataset file:///shared/topeka-metro.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:
2019-12-13
Feed End Date:
2021-12-12

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: 0
  • Routes: 29
  • Shapes: 63
  • Stops: 572
  • Trips: 1000

Specification Compliance report

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

Notice Code Severity Total
duplicate_route_name WARNING 8

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
2 "2284-30" 4 "2284-88" "3" "#3 E 6th to Downtown" 3 "2284-topeka-metro"
10 "2284-25" 12 "2284-72" "21" "#21 W 21st to Downtown" 3 "2284-topeka-metro"
6 "2284-67" 20 "2284-103" "12" "#12 Huntoon to Downtown" 3 "2284-topeka-metro"
11 "2284-21" 23 "2284-37" "10s" "10 Special" 3 "2284-topeka-metro"
21 "2284-105" 24 "2284-11" "17" "#17 W 17th to Downtown" 3 "2284-topeka-metro"
16 "2284-4" 27 "2284-43" "10s2" "10 Special #2" 3 "2284-topeka-metro"
14 "2284-5" 28 "2284-110" "5" "#5 Indiana to Downtown" 3 "2284-topeka-metro"
9 "2284-109" 30 "2284-16" "29" "#29 W 29th to Downtown" 3 "2284-topeka-metro"
expired_calendar WARNING 10

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "2284-100"
3 "2284-110"
4 "2284-113"
5 "2284-39"
6 "2284-4"
7 "2284-4f72373efc7f14a45954"
8 "2284-58"
9 "2284-86"
10 "2284-91"
11 "2284-f8bbc7df59806752e110"
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 "20251205" "20211212" "20251212"
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.
927 "2284-42" "2284-986" 23925 "2284-569" "27th @ Wanamaker" [39.017810173689796,-95.76266116115569] 23924 "2284-568" "Villa West @ 27th" [39.01770732394218,-95.76714539272108]
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20251205" "20191216" "20211210"