Search
  1. Home
  2. Japan Feeds
  3. kurashikishi
  4. Source Data Validation Report

kurashikishi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-11T19:17:37Z,
for the dataset file:///shared/kurashikishi_d0442bf4.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-10-01

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 0
  • Stops: 188
  • Trips: 15

Specification Compliance report

30 notices reported (0 errors, 26 warnings, 4 infos)

Notice Code Severity Total
duplicate_route_name WARNING 1

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`.
3 "R7" 4 "R8" "" "船穂線" 3 "6000020332020"
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_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 4

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.
"feed_info.txt" 2 "feed_end_date"
"feed_info.txt" 2 "feed_version"
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 19

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.
"stops.txt" "stop_name" "中山［真備町］" 29
"stops.txt" "stop_name" "中山［真備町］" 30
"stops.txt" "stop_name" "箭田南団地(要予約)" 50
"stops.txt" "stop_name" "箭田南団地(要予約)" 51
"stops.txt" "stop_name" "上成第２公園" 66
"stops.txt" "stop_name" "上成第２公園" 67
"stops.txt" "stop_name" "市場［船穂町］" 96
"stops.txt" "stop_name" "市場［船穂町］" 97
"stops.txt" "stop_name" "有井団地(要予約)" 120
"stops.txt" "stop_name" "有井団地(要予約)" 121
"stops.txt" "stop_name" "門田［蒲池］" 130
"stops.txt" "stop_name" "門田［蒲池］" 131
"stops.txt" "stop_name" "川辺団地(要予約)" 132
"stops.txt" "stop_name" "川辺団地(要予約)" 133
"stops.txt" "stop_name" "若葉台第２公園下" 150
"stops.txt" "stop_name" "若葉台第２公園下" 151
"stops.txt" "stop_name" "若葉台第３公園前" 152
"stops.txt" "stop_name" "若葉台第３公園前" 153
"routes.txt" "route_long_name" "南ルート：柳井原～吉備真備駅" 6
future_feed INFO 1

future_feed

The feed covers the future only.

The minimum start_date in feed_info.txt is greater than today's date, indicating the feed covers the future only.

You can see more about this notice here.

feedStartDate (?) Feed start date. currentDate (?) Current date.
"20261001" "20260911"
unknown_column INFO 1

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" 8
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

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