GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T18:25:41Z,
for the dataset file:///shared/gtfs10-highway03kamenoi.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:
Japanese
Feed Start Date:
2025-04-01
Feed End Date:
2026-03-31

Files included

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

Counts

  • Agencies: 2
  • Blocks: 0
  • Routes: 8
  • Shapes: 8
  • Stops: 32
  • Trips: 48

Specification Compliance report

24 notices reported (3 errors, 19 warnings, 2 infos)

Notice Code Severity Total
missing_required_column ERROR 3

missing_required_column

A required column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the missing column.
"translations.txt" "field_name"
"translations.txt" "language"
"translations.txt" "table_name"
duplicate_route_name WARNING 2

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 "101679-80020" 8 "101679-80022" "" "湯布院～福岡（ゆふいん号）" 3 "101679-4320001006282"
6 "101679-80021" 9 "101679-80023" "" "福岡～湯布院（ゆふいん号）" 3 "101679-4320001006282"
mixed_case_recommended_field WARNING 9

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" "別府～福岡空港～福岡（とよのくに号）" 2
"routes.txt" "route_long_name" "福岡～福岡空港～別府（とよのくに号）" 3
"routes.txt" "route_long_name" "別府～福岡（とよのくに号）" 4
"routes.txt" "route_long_name" "湯布院～福岡（ゆふいん号）" 5
"routes.txt" "route_long_name" "福岡～湯布院（ゆふいん号）" 6
"routes.txt" "route_long_name" "福岡～別府（とよのくに号）" 7
"routes.txt" "route_long_name" "湯布院～福岡（ゆふいん号）" 8
"routes.txt" "route_long_name" "福岡～湯布院（ゆふいん号）" 9
"stops.txt" "stop_name" "別府北浜（②のりば【スタバ前】）" 3
non_ascii_or_non_printable_char WARNING 8

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.

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.
"fare_rules.txt" 2 "fare_id" "101679-Agency1_運賃_別府_福岡_10"
"fare_rules.txt" 3 "fare_id" "101679-Agency1_運賃_別府_福岡_10"
"fare_rules.txt" 4 "fare_id" "101679-Agency1_運賃_別府_福岡_10"
"fare_rules.txt" 91 "fare_id" "101679-Agency2_運賃_別府_福岡_10"
"fare_rules.txt" 92 "fare_id" "101679-Agency2_運賃_別府_福岡_10"
"fare_rules.txt" 93 "fare_id" "101679-Agency2_運賃_別府_福岡_10"
"fare_attributes.txt" 2 "fare_id" "101679-Agency1_運賃_別府_福岡_10"
"fare_attributes.txt" 21 "fare_id" "101679-Agency2_運賃_別府_福岡_10"
unknown_column INFO 2

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.
"translations.txt" "trans_id" 1
"translations.txt" "lang" 2