GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T21:01:10Z,
for the dataset file:///shared/yukicity-junkaibus.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-01
Feed End Date:
2027-03-31

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 7
  • Shapes: 0
  • Stops: 121
  • Trips: 50

Specification Compliance report

27 notices reported (1 errors, 26 warnings, 0 infos)

Notice Code Severity Total
translation_foreign_key_violation ERROR 1

translation_foreign_key_violation

An entity with the given record_id and record_sub_id cannot be found in the referenced table.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tableName (?) `table_name` of the faulty record. recordId (?) `record_id` of the faulty record. recordSubId (?) `record_sub_id` of the faulty record.
12 "stops" "9" ""
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 1

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

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
"stops.txt" "stop_name" "下り松西（よこやま歯科）" 4
"stops.txt" "stop_name" "久保田（絹川郵便局）" 7
"stops.txt" "stop_name" "市役所・アクロス" 15
"stops.txt" "stop_name" "江川大町西（谷明神社）" 22
"stops.txt" "stop_name" "新田間町（関ふとん店）" 34
"stops.txt" "stop_name" "公達（和尚塚）" 42
"stops.txt" "stop_name" "大橋町（永田屋）" 43
"stops.txt" "stop_name" "芳賀崎（八幡神社入口）" 58
"stops.txt" "stop_name" "山王（北島商店）" 61
"stops.txt" "stop_name" "上山川消防第10分団" 64
"stops.txt" "stop_name" "瓦塚（魚正商店）" 65
"stops.txt" "stop_name" "結城中学校南（大木医院）" 89
"stops.txt" "stop_name" "大町（郷土館）" 96
"stops.txt" "stop_name" "穀町（河野歯科医院）" 97
"stops.txt" "stop_name" "栄町中央（神明橋歯科医院）" 105
"stops.txt" "stop_name" "五助（わたなべ歯科医院）" 109
"stops.txt" "stop_name" "結城出張所・公民館" 113