bizen-city — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T00:42:19Z,
for the dataset file:///shared/bizen-city_f59ecb3c.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:
2026-04-01
Feed End Date:
2026-09-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. shapes.txt
  12. stop_times.txt
  13. stops.txt
  14. translations.txt
  15. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 10
  • Shapes: 93
  • Stops: 308
  • Trips: 323

Specification Compliance report

156 notices reported (0 errors, 149 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 10

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"
"fare_attributes.txt" 8 "agency_id"
"fare_attributes.txt" 9 "agency_id"
"fare_attributes.txt" 10 "agency_id"
"fare_attributes.txt" 11 "agency_id"
mixed_case_recommended_field WARNING 1

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" "南北・閑谷学校のぞみ線" 9
same_name_and_description_for_stop WARNING 118

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty record. stopDesc (?) The faulty record's `stop_desc`.
6 "2_1" "亀楽荘前"
7 "3_1" "閑谷下"
8 "4_1" "閑谷学校"
9 "5_1" "閑谷中"
10 "6_1" "せばと"
17 "10_1" "吉永駅"
18 "11_1" "吉永病院前"
21 "13_1" "飯掛上"
22 "14_1" "飯掛下"
23 "15_1" "牛中"
24 "16_1" "大藤下"
25 "17_1" "大藤橋"
26 "18_1" "落合橋"
27 "19_1" "樫"
28 "20_1" "樫車庫"
29 "21_1" "下畑上"
30 "22_1" "下畑下"
31 "23_1" "高場診療所前"
32 "24_1" "滝谷"
33 "25_1" "出合橋"
34 "26_1" "東畑"
35 "27_1" "三国小"
36 "28_1" "和意谷"
37 "29_1" "脇谷"
38 "30_1" "麻宇那上"
43 "34_1" "伊里小前"
47 "36_1" "大橋"
51 "41_1" "佐那高下"
54 "43_1" "蕃山下"
69 "53_1" "農協前"
72 "55_1" "備前病院前"
75 "58_1" "船坂峠入口"
76 "61_1" "三石"
77 "62_1" "三石駅"
80 "64_1" "持田"
85 "68_1" "青石"
86 "69_1" "飯井"
87 "70_1" "飯井新田"
88 "71_1" "稲荷山"
95 "75_1" "長船駅"
98 "77_1" "海水浴場前"
103 "80_1" "国府小学校前"
104 "81_1" "佐山公民館前"
105 "82_1" "佐山西"
110 "85_1" "瀬戸内市長船庁舎前"
113 "87_1" "鶴海港"
116 "90_1" "鶴海西"
117 "91_1" "鶴山小学校前"
118 "92_1" "帝窯前"
121 "94_1" "西宮"
stop_too_far_from_shape WARNING 1

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
186 "1_5072_2" "1_51_5072_2_10022509_20260401" 6024 "215_1" "伊里中公民館" [34.75974597831724,134.22133604920631] 130.00350553383774
stops_match_shape_out_of_order WARNING 5

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
182 "1_5051_1" "1_51_5051_1_10022498_20260401" 5933 "12_1" "西河原" [34.81359925965306,134.19935925724624] 5932 "9_1" "吉田橋" [34.81194401042423,134.19905734481418]
56 "1_1071_1" "1_51_1071_1_10022563_20260401" 2294 "144_1" "日生幼稚園前" [34.74058148165891,134.29418578732736] 2292 "127_1" "スワ住宅前" [34.73911267693734,134.2958527936676]
58 "1_1081_1" "1_53_1081_1_10022549_20260401" 2416 "146_2" "穂浪橋" [34.73176114695976,134.2230792721321] 2414 "113_1" "伊里局前" [34.73171394844172,134.22104969177926]
170 "1_5031_1" "1_51_5031_1_10022496_20260401" 5672 "12_1" "西河原" [34.81359925965306,134.19935925724624] 5670 "9_1" "吉田橋" [34.81194388996783,134.19905718801297]
52 "1_1061_1" "1_51_1061_1_10022234_20260401" 2131 "144_1" "日生幼稚園前" [34.74058108709266,134.29419720816156] 2128 "127_1" "スワ住宅前" [34.739108079698674,134.2958531262306]
unused_shape WARNING 13

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"1_1041_1" 2956
"1_1051_1" 3692
"1_1092_2" 6257
"1_2031_1" 7670
"1_2032_2" 8016
"1_2072_2" 9849
"1_4041_1" 12895
"1_4051_1" 13509
"1_5042_2" 16198
"1_8012_2" 19775
"1_9022_2" 24054
"1_9061_1" 24560
"1_9071_1" 24665
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.
"routes_jp.txt"
"agency_jp.txt"
"office_jp.txt"