GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T14:57:34Z,
for the dataset file:///shared/okabo-bus.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. agency_jp.txt
  3. calendar.txt
  4. calendar_dates.txt
  5. fare_attributes.txt
  6. fare_rules.txt
  7. feed_info.txt
  8. office_jp.txt
  9. routes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. translations.txt
  14. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 11
  • Shapes: 0
  • Stops: 60
  • Trips: 19

Specification Compliance report

706 notices reported (2 errors, 702 warnings, 2 infos)

Notice Code Severity Total
missing_required_field ERROR 2

missing_required_field

A required field is missing.

The given field has no value in some input row, even though values are required.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_publisher_name"
"feed_info.txt" 2 "feed_publisher_url"
duplicate_route_name WARNING 9

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 "2_1" 3 "2_2" "" "OKABO 北回り系統" 3 "7000020182010_10"
2 "2_1" 4 "2_3" "" "OKABO 北回り系統" 3 "7000020182010_10"
2 "2_1" 5 "2_4" "" "OKABO 北回り系統" 3 "7000020182010_10"
6 "2_5" 7 "2_6" "" "OKABO 南回り系統" 3 "7000020182010_10"
6 "2_5" 8 "2_7" "" "OKABO 南回り系統" 3 "7000020182010_10"
6 "2_5" 9 "2_8" "" "OKABO 南回り系統" 3 "7000020182010_10"
6 "2_5" 10 "2_9" "" "OKABO 南回り系統" 3 "7000020182010_10"
6 "2_5" 11 "2_10" "" "OKABO 南回り系統" 3 "7000020182010_10"
6 "2_5" 12 "2_11" "" "OKABO 南回り系統" 3 "7000020182010_10"
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 "岡保北"
3 "岡保南"
mixed_case_recommended_field WARNING 15

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_long_name" "OKABO 北回り系統" 2
"routes.txt" "route_long_name" "OKABO 北回り系統" 3
"routes.txt" "route_long_name" "OKABO 北回り系統" 4
"routes.txt" "route_long_name" "OKABO 北回り系統" 5
"routes.txt" "route_long_name" "OKABO 南回り系統" 6
"routes.txt" "route_long_name" "OKABO 南回り系統" 7
"routes.txt" "route_long_name" "OKABO 南回り系統" 8
"routes.txt" "route_long_name" "OKABO 南回り系統" 9
"routes.txt" "route_long_name" "OKABO 南回り系統" 10
"routes.txt" "route_long_name" "OKABO 南回り系統" 11
"routes.txt" "route_long_name" "OKABO 南回り系統" 12
"stops.txt" "stop_name" "和田東２丁目" 53
"stops.txt" "stop_name" "大東２丁目" 55
"stops.txt" "stop_name" "北四ツ居２丁目第２" 56
"stops.txt" "stop_name" "御幸４丁目東" 58
non_ascii_or_non_printable_char WARNING 675

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

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

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"calendar.txt" 2 "service_id" "岡保北"
"calendar.txt" 3 "service_id" "岡保南"
"calendar_dates.txt" 2 "service_id" "岡保北"
"calendar_dates.txt" 3 "service_id" "岡保北"
"calendar_dates.txt" 4 "service_id" "岡保北"
"calendar_dates.txt" 5 "service_id" "岡保北"
"calendar_dates.txt" 6 "service_id" "岡保北"
"calendar_dates.txt" 7 "service_id" "岡保北"
"calendar_dates.txt" 8 "service_id" "岡保北"
"calendar_dates.txt" 9 "service_id" "岡保北"
"calendar_dates.txt" 10 "service_id" "岡保北"
"calendar_dates.txt" 11 "service_id" "岡保北"
"calendar_dates.txt" 12 "service_id" "岡保北"
"calendar_dates.txt" 13 "service_id" "岡保北"
"calendar_dates.txt" 14 "service_id" "岡保北"
"calendar_dates.txt" 15 "service_id" "岡保北"
"calendar_dates.txt" 16 "service_id" "岡保北"
"calendar_dates.txt" 17 "service_id" "岡保北"
"calendar_dates.txt" 18 "service_id" "岡保北"
"calendar_dates.txt" 19 "service_id" "岡保北"
"calendar_dates.txt" 20 "service_id" "岡保北"
"calendar_dates.txt" 21 "service_id" "岡保北"
"calendar_dates.txt" 22 "service_id" "岡保北"
"calendar_dates.txt" 23 "service_id" "岡保北"
"calendar_dates.txt" 24 "service_id" "岡保南"
"calendar_dates.txt" 25 "service_id" "岡保南"
"calendar_dates.txt" 26 "service_id" "岡保南"
"calendar_dates.txt" 27 "service_id" "岡保南"
"calendar_dates.txt" 28 "service_id" "岡保南"
"calendar_dates.txt" 29 "service_id" "岡保南"
"calendar_dates.txt" 30 "service_id" "岡保南"
"calendar_dates.txt" 31 "service_id" "岡保南"
"calendar_dates.txt" 32 "service_id" "岡保南"
"calendar_dates.txt" 33 "service_id" "岡保南"
"calendar_dates.txt" 34 "service_id" "岡保南"
"calendar_dates.txt" 35 "service_id" "岡保南"
"calendar_dates.txt" 36 "service_id" "岡保南"
"calendar_dates.txt" 37 "service_id" "岡保南"
"calendar_dates.txt" 38 "service_id" "岡保南"
"calendar_dates.txt" 39 "service_id" "岡保南"
"calendar_dates.txt" 40 "service_id" "岡保南"
"calendar_dates.txt" 41 "service_id" "岡保南"
"calendar_dates.txt" 42 "service_id" "岡保南"
"calendar_dates.txt" 43 "service_id" "岡保南"
"calendar_dates.txt" 44 "service_id" "岡保南"
"calendar_dates.txt" 45 "service_id" "岡保南"
"stop_times.txt" 2 "trip_id" "2_11+1+岡保南+17"
"stop_times.txt" 3 "trip_id" "2_11+1+岡保南+17"
"stop_times.txt" 4 "trip_id" "2_11+1+岡保南+17"
"stop_times.txt" 5 "trip_id" "2_11+1+岡保南+17"
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.
"20260123" "20230401" "20240330"
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"agency_jp.txt"
"office_jp.txt"