GTFS Schedule Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
熊本バス
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2025-08-01
Feed End Date:
2025-11-16

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. routes_jp.txt
  11. stop_times.txt
  12. stops.txt
  13. translations.txt
  14. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 68
  • Shapes: 0
  • Stops: 590
  • Trips: 1351

Specification Compliance report

3826 notices reported (3 errors, 3799 warnings, 24 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"
expired_calendar WARNING 4

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 "1_1_20250801"
3 "1_2_20250801"
4 "1_3_20250801"
5 "1_11_20250801"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260123" "20251116" "20260130"
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
missing_recommended_field WARNING 3592

missing_recommended_field

A recommended field is missing.

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

You can see more about this notice here.

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "agency_id"
"fare_attributes.txt" 6 "agency_id"
"fare_attributes.txt" 7 "agency_id"
"fare_attributes.txt" 8 "agency_id"
"fare_attributes.txt" 9 "agency_id"
"fare_attributes.txt" 10 "agency_id"
"fare_attributes.txt" 11 "agency_id"
"fare_attributes.txt" 12 "agency_id"
"fare_attributes.txt" 13 "agency_id"
"fare_attributes.txt" 14 "agency_id"
"fare_attributes.txt" 15 "agency_id"
"fare_attributes.txt" 16 "agency_id"
"fare_attributes.txt" 17 "agency_id"
"fare_attributes.txt" 18 "agency_id"
"fare_attributes.txt" 19 "agency_id"
"fare_attributes.txt" 20 "agency_id"
"fare_attributes.txt" 21 "agency_id"
"fare_attributes.txt" 22 "agency_id"
"fare_attributes.txt" 23 "agency_id"
"fare_attributes.txt" 24 "agency_id"
"fare_attributes.txt" 25 "agency_id"
"fare_attributes.txt" 26 "agency_id"
"fare_attributes.txt" 27 "agency_id"
"fare_attributes.txt" 28 "agency_id"
"fare_attributes.txt" 29 "agency_id"
"fare_attributes.txt" 30 "agency_id"
"fare_attributes.txt" 31 "agency_id"
"fare_attributes.txt" 32 "agency_id"
"fare_attributes.txt" 33 "agency_id"
"fare_attributes.txt" 34 "agency_id"
"fare_attributes.txt" 35 "agency_id"
"fare_attributes.txt" 36 "agency_id"
"fare_attributes.txt" 37 "agency_id"
"fare_attributes.txt" 38 "agency_id"
"fare_attributes.txt" 39 "agency_id"
"fare_attributes.txt" 40 "agency_id"
"fare_attributes.txt" 41 "agency_id"
"fare_attributes.txt" 42 "agency_id"
"fare_attributes.txt" 43 "agency_id"
"fare_attributes.txt" 44 "agency_id"
"fare_attributes.txt" 45 "agency_id"
"fare_attributes.txt" 46 "agency_id"
"fare_attributes.txt" 47 "agency_id"
"fare_attributes.txt" 48 "agency_id"
"fare_attributes.txt" 49 "agency_id"
"fare_attributes.txt" 50 "agency_id"
"fare_attributes.txt" 51 "agency_id"
mixed_case_recommended_field WARNING 198

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.

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

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" "M3-2：桜町バスターミナル→田迎→イオン→通潤山荘" 2
"routes.txt" "route_long_name" "M3-2：通潤山荘→イオン→田迎→桜町バスターミナル" 3
"routes.txt" "route_long_name" "M4-1：桜町バスターミナル→田迎→イオン→辺場→甲佐" 4
"routes.txt" "route_long_name" "M4-1：甲佐→辺場→イオン→田迎→桜町バスターミナル" 5
"routes.txt" "route_long_name" "M4-2：桜町バスターミナル→田迎→イオン→辺場→砥用" 6
"routes.txt" "route_long_name" "M4-2：砥用→辺場→イオン→田迎→桜町バスターミナル" 7
"routes.txt" "route_long_name" "浜町→内大臣→甲佐" 8
"routes.txt" "route_long_name" "M4-3：桜町バスターミナル→田迎→イオン→辺場→内大臣→浜町" 9
"routes.txt" "route_long_name" "M4-3：浜町→内大臣→辺場→イオン→田迎→桜町バスターミナル" 10
"routes.txt" "route_long_name" "K2-4/M4-1：甲佐→辺場→イオン→田迎→桜町バスターミナル・県庁・健軍→甲佐" 11
"routes.txt" "route_long_name" "M3-1：桜町バスターミナル→田迎→イオン→御船→甲佐" 12
"routes.txt" "route_long_name" "M3-1：甲佐→御船→イオン→田迎→桜町バスターミナル" 13
"routes.txt" "route_long_name" "M1-1：桜町バスターミナル→田迎→中の瀬車庫" 14
"routes.txt" "route_long_name" "M1-1：中の瀬車庫→田迎→桜町バスターミナル" 15
"routes.txt" "route_long_name" "M2-1：桜町バスターミナル→田迎→中の瀬車庫→イオン" 16
"routes.txt" "route_long_name" "M2-1：イオン→中の瀬車庫→田迎→桜町バスターミナル" 17
"routes.txt" "route_long_name" "M2-1：◆深夜◆桜町バスターミナル→田迎→中車庫→イオン" 18
"routes.txt" "route_long_name" "M2-1：熊本駅→桜町バスターミナル→田迎→中車庫→イオン" 19
"routes.txt" "route_long_name" "M2-1：イオン→中車庫→田迎→桜町バスターミナル→熊本駅" 20
"routes.txt" "route_long_name" "M0-0：中の瀬車庫ー田迎ー桜町BT?中央病院ー中の瀬車庫" 21
"routes.txt" "route_long_name" "K2-3：桜町バスターミナル→県庁→健軍→東区→イオン→城南" 22
"routes.txt" "route_long_name" "K2-3：城南→イオン→東区→健軍→県庁→桜町バスターミナル" 23
"routes.txt" "route_long_name" "K2-4：桜町バスターミナル→県庁→健軍→御船→甲佐" 24
"routes.txt" "route_long_name" "K2-4：甲佐→御船→健軍→県庁→桜町バスターミナル" 25
"routes.txt" "route_long_name" "K2-1：桜町バスターミナル→県庁→健軍→東区→イオン" 26
"routes.txt" "route_long_name" "K2-1：イオン→東区→健軍→県庁→桜町バスターミナル" 27
"routes.txt" "route_long_name" "K2-2：健軍→東区→イオン" 28
"routes.txt" "route_long_name" "K2-2：イオン→東区→健軍" 29
"routes.txt" "route_long_name" "K2-5：桜町バスターミナル→県庁→健軍→甲佐→砥用" 30
"routes.txt" "route_long_name" "K2-5：砥用→御船→健軍→県庁→桜町バスターミナル" 31
"routes.txt" "route_long_name" "M6-1：桜町バスターミナル→田迎→イオン→城南" 32
"routes.txt" "route_long_name" "M6-1：城南→イオン→田迎→桜町バスターミナル" 33
"routes.txt" "route_long_name" "M6-2：桜町バスターミナル→田迎→イオン→城南→宇土駅" 34
"routes.txt" "route_long_name" "M6-2：宇土駅→城南→イオン→田迎→桜町バスターミナル" 35
"routes.txt" "route_long_name" "M6-3：桜町バスターミナル→田迎→イオン→城南→松橋駅" 36
"routes.txt" "route_long_name" "M6-3：松橋駅→城南→イオン→田迎→桜町バスターミナル" 37
"routes.txt" "route_long_name" "M6-4：桜町バスターミナル→田迎→イオン→城南→志導寺" 38
"routes.txt" "route_long_name" "M6-4：志導寺→城南→イオン→田迎→桜町バスターミナル" 39
"routes.txt" "route_long_name" "M6-5：桜町バスターミナル→田迎→イオン→城南→志導寺→下安見" 40
"routes.txt" "route_long_name" "M6-6：桜町バスターミナル→田迎→イオン→城南→段鶴" 41
"routes.txt" "route_long_name" "M6-6：段鶴→城南→イオン→田迎→桜町バスターミナル" 42
"routes.txt" "route_long_name" "K1-3：桜町バスターミナル→県庁→画図→イオン→城南" 43
"routes.txt" "route_long_name" "K1-3：城南→イオン→烏ヶ江→画図→県庁→桜町バスターミナル" 44
"routes.txt" "route_long_name" "K1-4：桜町バスターミナル→県庁→画図→イオン→辺場→甲佐" 45
"routes.txt" "route_long_name" "K1-4：甲佐→辺場→イオン→烏ヶ江→画図→県庁→桜町バスターミナル" 46
"routes.txt" "route_long_name" "M5-1：桜町バスターミナル→田迎→イオン→乙女→甲佐" 47
"routes.txt" "route_long_name" "M5-1：甲佐→乙女→イオン→田迎→桜町バスターミナル" 48
"routes.txt" "route_long_name" "P4-3：桜町バスターミナル→尚絅校前→出仲間→中の瀬車庫" 49
"routes.txt" "route_long_name" "P4-3：中の瀬車庫→出仲間（ﾊﾞ）→尚絅校前→桜町バスターミナル" 50
"routes.txt" "route_long_name" "P4-1：桜町バスターミナル→尚絅校前→中央病院→中の瀬車庫" 51
stop_without_stop_time WARNING 2

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.
561 "100462_2" "出仲間（バイパス）"
568 "100626_1" "熊本中央病院入口"
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" "20250801" "20251116"
platform_without_parent_station INFO 15

platform_without_parent_station

A platform has no parent_station field set.

This is different from location_without_parent_station since it is less severe.

You can see more about this notice here.

csvRowNumber (?) Row number of the faulty record. stopId (?) The id of the faulty record. stopName (?) The stop name of the faulty record.
4 "100002_1" "桜町バスターミナル"
5 "100002_2" "桜町バスターミナル"
6 "100002_4" "桜町バスターミナル"
7 "100002_9" "桜町バスターミナル"
8 "100002_13" "桜町バスターミナル"
9 "100002_24" "桜町バスターミナル"
10 "100002_25" "桜町バスターミナル"
11 "100002_29" "桜町バスターミナル"
14 "100004_1" "水道町"
15 "100004_2" "水道町"
16 "100004_3" "水道町"
441 "100339_1" "熊本駅前"
442 "100339_3" "熊本駅前"
566 "100598_1" "水前寺駅通り"
567 "100598_2" "水前寺駅通り"
unknown_column INFO 6

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.
"routes.txt" "jp_parent_route_id" 10
"trips.txt" "jp_trip_desc" 9
"trips.txt" "jp_trip_desc_symbol" 10
"trips.txt" "jp_office_id" 11
"translations.txt" "trans_id" 1
"translations.txt" "lang" 2
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

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