yakima2 — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T13:30:33Z,
for the dataset file:///shared/yakima2_79ee4e94.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 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. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 23
  • Shapes: 1
  • Stops: 605
  • Trips: 342

Specification Compliance report

17 notices reported (6 errors, 11 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 6

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.

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.
2421 2419 "101950-35" "09:09:00" "09:11:00"
2425 2421 "101950-35" "08:58:00" "09:09:00"
2491 2489 "101950-36" "10:09:00" "10:11:00"
2495 2491 "101950-36" "09:58:00" "10:09:00"
2561 2559 "101950-37" "11:09:00" "11:11:00"
2565 2561 "101950-37" "10:58:00" "11:09:00"
duplicate_route_name WARNING 11

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 "101950-56" 6 "101950-37" "1" "Summitview / Lincoln" 3 "101950-yakima2"
8 "101950-22" 12 "101950-66" "4" "Fruitvale / Mead" 3 "101950-yakima2"
2 "101950-74" 13 "101950-75" "6" "Fair Ave. / No. 4th St" 3 "101950-yakima2"
3 "101950-19" 15 "101950-64" "2" "Tieton / Nob Hill" 3 "101950-yakima2"
16 "101950-68" 17 "101950-31" "5" "Nob Hill / Tieton" 3 "101950-yakima2"
8 "101950-22" 18 "101950-67" "4" "Fruitvale / Mead" 3 "101950-yakima2"
19 "101950-71" 20 "101950-6" "8" "Yakima Ave" 3 "101950-yakima2"
11 "101950-77" 21 "101950-76" "12" "Fair Ave. / No. 4th St" 3 "101950-yakima2"
19 "101950-71" 22 "101950-70" "8" "Yakima Ave" 3 "101950-yakima2"
5 "101950-56" 23 "101950-35" "1" "Summitview / Lincoln" 3 "101950-yakima2"
14 "101950-72" 24 "101950-53" "9" "1st Street / Washington" 3 "101950-yakima2"