GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T21:40:37Z,
for the dataset file:///shared/komonotown-communitybus.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-04-16
Feed End Date:
2026-02-26

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: 6
  • Shapes: 0
  • Stops: 97
  • Trips: 61

Specification Compliance report

42 notices reported (0 errors, 35 warnings, 7 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
missing_recommended_field WARNING 6

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.

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"
mixed_case_recommended_field WARNING 26

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" "かもしか号1コース 神森福王山線" 2
"routes.txt" "route_long_name" "かもしか号2コース 千種根の平線" 3
"routes.txt" "route_long_name" "かもしか号3コース 小島永井線" 4
"routes.txt" "route_long_name" "かもしか号6コース 潤田福王山線" 5
"routes.txt" "route_long_name" "かもしか号7コース 竹永小島線" 6
"routes.txt" "route_long_name" "かもしか号9コース 神森菰野線" 7
"stops.txt" "stop_name" "けやき・菰野町役場" 22
"stops.txt" "stop_name" "柳原(菰野町)" 42
"stops.txt" "stop_name" "柳原(菰野町)" 43
"trips.txt" "trip_headsign" "けやき・菰野町役場" 25
"trips.txt" "trip_headsign" "けやき・菰野町役場" 26
"trips.txt" "trip_headsign" "けやき・菰野町役場" 27
"trips.txt" "trip_headsign" "けやき・菰野町役場" 34
"trips.txt" "trip_headsign" "けやき・菰野町役場" 35
"trips.txt" "trip_headsign" "けやき・菰野町役場" 36
"trips.txt" "trip_headsign" "けやき・菰野町役場" 37
"trips.txt" "trip_headsign" "けやき・菰野町役場" 38
"trips.txt" "trip_headsign" "けやき・菰野町役場" 39
"trips.txt" "trip_headsign" "けやき・菰野町役場" 40
"trips.txt" "trip_headsign" "けやき・菰野町役場" 41
"trips.txt" "trip_headsign" "けやき・菰野町役場" 42
"trips.txt" "trip_headsign" "けやき・菰野町役場" 43
"trips.txt" "trip_headsign" "けやき・菰野町役場" 44
"trips.txt" "trip_headsign" "けやき・菰野町役場" 45
"trips.txt" "trip_headsign" "けやき・菰野町役場" 59
"trips.txt" "trip_headsign" "けやき・菰野町役場" 60
unusable_trip WARNING 1

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
60 "8_2_2880912_1_2357_20250416"
unused_trip WARNING 1

unused_trip

Trip is not be used in stop_times.txt

Trips should be referred to at least once in stop_times.txt.

You can see more about this notice here.

tripId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"8_2_2880912_1_2357_20250416" 60
unknown_column INFO 4

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
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.
"office_jp.txt"
"routes_jp.txt"
"agency_jp.txt"