GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T20:03:30Z,
for the dataset file:///shared/yakima_e2d76c55.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-05-08
Feed End Date:
2027-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 17
  • Shapes: 0
  • Stops: 560
  • Trips: 315

Specification Compliance report

76 notices reported (69 errors, 7 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 69

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

Only the first 50 of 69 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
6834 6832 "100157-102" "18:09:00" "18:11:00"
6837 6834 "100157-102" "17:58:00" "18:09:00"
2107 2105 "100157-32" "18:09:00" "18:11:00"
2110 2107 "100157-32" "17:58:00" "18:09:00"
1973 1971 "100157-30" "15:55:00" "15:58:00"
1976 1973 "100157-30" "15:41:00" "15:55:00"
2040 2038 "100157-31" "17:08:00" "17:10:00"
2043 2040 "100157-31" "16:56:00" "17:08:00"
6700 6698 "100157-100" "15:55:00" "15:58:00"
6703 6700 "100157-100" "15:41:00" "15:55:00"
6767 6765 "100157-101" "17:08:00" "17:10:00"
6770 6767 "100157-101" "16:56:00" "17:08:00"
3910 3908 "100157-58" "09:09:00" "09:11:00"
3913 3910 "100157-58" "08:58:00" "09:09:00"
3977 3975 "100157-59" "10:09:00" "10:11:00"
3980 3977 "100157-59" "09:58:00" "10:09:00"
3776 3774 "100157-56" "07:09:00" "07:11:00"
3779 3776 "100157-56" "06:58:00" "07:09:00"
3843 3841 "100157-57" "08:09:00" "08:11:00"
3846 3843 "100157-57" "07:58:00" "08:09:00"
3709 3707 "100157-55" "06:09:00" "06:11:00"
4379 4377 "100157-65" "17:08:00" "17:10:00"
4382 4379 "100157-65" "16:56:00" "17:08:00"
4446 4444 "100157-66" "18:09:00" "18:11:00"
4449 4446 "100157-66" "17:58:00" "18:09:00"
4245 4243 "100157-63" "14:45:00" "14:48:00"
4248 4245 "100157-63" "14:31:00" "14:45:00"
4312 4310 "100157-64" "15:55:00" "15:58:00"
4315 4312 "100157-64" "15:41:00" "15:55:00"
4111 4109 "100157-61" "12:25:00" "12:28:00"
4114 4111 "100157-61" "12:11:00" "12:25:00"
4178 4176 "100157-62" "13:35:00" "13:38:00"
4181 4178 "100157-62" "13:21:00" "13:35:00"
4044 4042 "100157-60" "11:15:00" "11:18:00"
4047 4044 "100157-60" "11:01:00" "11:15:00"
6566 6564 "100157-98" "13:35:00" "13:38:00"
6569 6566 "100157-98" "13:21:00" "13:35:00"
6633 6631 "100157-99" "14:45:00" "14:48:00"
6636 6633 "100157-99" "14:31:00" "14:45:00"
6432 6430 "100157-96" "11:15:00" "11:18:00"
6435 6432 "100157-96" "11:01:00" "11:15:00"
6499 6497 "100157-97" "12:25:00" "12:28:00"
6502 6499 "100157-97" "12:11:00" "12:25:00"
6298 6296 "100157-94" "09:09:00" "09:11:00"
6301 6298 "100157-94" "08:58:00" "09:09:00"
6365 6363 "100157-95" "10:09:00" "10:11:00"
6368 6365 "100157-95" "09:58:00" "10:09:00"
6164 6162 "100157-92" "07:09:00" "07:11:00"
6167 6164 "100157-92" "06:58:00" "07:09:00"
6231 6229 "100157-93" "08:09:00" "08:11:00"
duplicate_route_name WARNING 7

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`.
5 "100157-96" 7 "100157-99" "9" "1st Street / Washington" 3 "100157-yakima"
6 "100157-101" 9 "100157-100" "8" "Yakima Ave" 3 "100157-yakima"
6 "100157-101" 12 "100157-102" "8" "Yakima Ave" 3 "100157-yakima"
14 "100157-106" 15 "100157-107" "1" "Summitview / Lincoln" 3 "100157-yakima"
13 "100157-111" 16 "100157-112" "3" "Mead / Fruitvale" 3 "100157-yakima"
8 "100157-108" 17 "100157-110" "2" "Tieton / Nob Hill" 3 "100157-yakima"
4 "100157-114" 18 "100157-113" "5" "Nob Hill / Tieton" 3 "100157-yakima"