GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T10:17:35Z,
for the dataset file:///shared/wotm-wa-us_486c0995.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:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2025-11-01
Feed End Date:
2026-10-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 2
  • Shapes: 9
  • Stops: 42
  • Trips: 14

Specification Compliance report

10 notices reported (0 errors, 4 warnings, 6 infos)

Notice Code Severity Total
expired_calendar WARNING 2

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 "1632-c_17428_b_85063_d_31"
3 "1632-c_17428_b_85063_d_32"
route_short_name_too_long WARNING 2

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`.
"1632-13383" 2 "Wahkiakum on the Move"
"1632-13343" 3 "Wahkiakum on the Move"
stop_without_zone_id INFO 6

stop_without_zone_id

Stop without value for stops.zone_id contained in a route with a zone-dependent fare rule.

If fare_rules.txt is provided, and fare_rules.txt uses at least one column among origin_id, destination_id, and contains_id, then all stops and platforms (location_type = 0) must have stops.zone_id assigned if they are defined in a trip defined in a route defined in a fare rule which also defines at least one of origin_id, destination_id, or contains_id.

You can see more about this notice here.

stopId (?) The faulty record's id. stopName (?) The faulty record's `stops.stop_name`. csvRowNumber (?) The row number of the faulty record.
"1632-2528792" "Cathlamet Mini Mart" 17
"1632-2528795" "Grays River" 18
"1632-2528812" "Erickson Park" 34
"1632-2528828" "Three Rivers Mall" 41
"1632-2528829" "Twin City Mall" 42
"1632-4245259" "Cowlitz Farmers Market" 43