GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-18T09:43:21Z,
for the dataset file:///shared/boise-state-university-boise_9b4b8e32.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:
ETA Transit Systems
Publisher URL:
https://etatransit.com
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2023-11-01
Feed End Date:
2030-04-30

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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 10
  • Shapes: 10
  • Stops: 55
  • Trips: 10

Specification Compliance report

25 notices reported (0 errors, 22 warnings, 3 infos)

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
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`.
"20" 2 "Blue" "Blue On Campus"
"46" 4 "Green" "Green"
"12" 11 "BOAS" "BOAS Soccer"
stop_without_stop_time WARNING 18

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
3 "36" "Micron Business & Economics Bldg"
7 "40" "Theatre Lane"
10 "43" "Caven-Williams Sports Complex"
11 "44" "Bleymaier Football Ctr."
12 "45" "East Albertsons Stadium"
24 "103" "6th & Broad"
26 "106" "Copper Basin"
28 "108" "Engineering"
42 "122" "Airport"
44 "124" "Multi-Purpose Building"
45 "125" "Chart1"
46 "126" "Chart2"
48 "14" "Varsity Center"
49 "213" "Cesar Chavez & Broadway"
50 "215" "BoDo Stop"
51 "216" "Payette Brewing"
52 "218" "Boise Brewing"
53 "219" "House of Western"
unknown_column INFO 3

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"calendar.txt" "service_name" 11
"trips.txt" "block_service_id" 11
"trips.txt" "block_name" 12