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

chitabus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T08:02:58Z,
for the dataset file:///shared/chitabus_b18c0a0e.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-02-01
Feed End Date:
2027-01-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. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. translations.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 20
  • Routes: 17
  • Shapes: 49
  • Stops: 293
  • Trips: 456

Specification Compliance report

13052 notices reported (0 errors, 13042 warnings, 10 infos)

Notice Code Severity Total
duplicate_route_name WARNING 3

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 "佐布里_R" 4 "佐布里_S" "" "佐布里線" 3 "8180001091831"
13 "岡田_D" 14 "岡田_K" "" "岡田線" 3 "8180001091831"
15 "日長団地_K" 16 "日長団地_M" "" "日長団地線" 3 "8180001091831"
expired_calendar WARNING 1

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.
4 "◆"
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
mixed_case_recommended_field WARNING 3

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" "半田・常滑線" 10
"stops.txt" "stop_name" "半田運河・蔵の街" 12
"stops.txt" "stop_name" "半田運河・蔵の街" 13
non_ascii_or_non_printable_char WARNING 13034

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

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

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"calendar.txt" 2 "service_id" "平日"
"calendar.txt" 3 "service_id" "土日祝"
"calendar.txt" 4 "service_id" "◆"
"calendar_dates.txt" 2 "service_id" "平日"
"calendar_dates.txt" 3 "service_id" "土日祝"
"calendar_dates.txt" 4 "service_id" "平日"
"calendar_dates.txt" 5 "service_id" "土日祝"
"calendar_dates.txt" 6 "service_id" "平日"
"calendar_dates.txt" 7 "service_id" "土日祝"
"calendar_dates.txt" 8 "service_id" "平日"
"calendar_dates.txt" 9 "service_id" "土日祝"
"calendar_dates.txt" 10 "service_id" "平日"
"calendar_dates.txt" 11 "service_id" "土日祝"
"calendar_dates.txt" 12 "service_id" "平日"
"calendar_dates.txt" 13 "service_id" "土日祝"
"calendar_dates.txt" 14 "service_id" "平日"
"calendar_dates.txt" 15 "service_id" "土日祝"
"calendar_dates.txt" 16 "service_id" "平日"
"calendar_dates.txt" 17 "service_id" "土日祝"
"calendar_dates.txt" 18 "service_id" "平日"
"calendar_dates.txt" 19 "service_id" "土日祝"
"calendar_dates.txt" 20 "service_id" "平日"
"calendar_dates.txt" 21 "service_id" "土日祝"
"calendar_dates.txt" 22 "service_id" "平日"
"calendar_dates.txt" 23 "service_id" "土日祝"
"calendar_dates.txt" 24 "service_id" "平日"
"calendar_dates.txt" 25 "service_id" "土日祝"
"calendar_dates.txt" 26 "service_id" "平日"
"calendar_dates.txt" 27 "service_id" "土日祝"
"calendar_dates.txt" 28 "service_id" "平日"
"calendar_dates.txt" 29 "service_id" "土日祝"
"calendar_dates.txt" 30 "service_id" "平日"
"calendar_dates.txt" 31 "service_id" "土日祝"
"calendar_dates.txt" 32 "service_id" "平日"
"calendar_dates.txt" 33 "service_id" "土日祝"
"calendar_dates.txt" 34 "service_id" "平日"
"calendar_dates.txt" 35 "service_id" "土日祝"
"calendar_dates.txt" 36 "service_id" "平日"
"calendar_dates.txt" 37 "service_id" "土日祝"
"calendar_dates.txt" 38 "service_id" "平日"
"calendar_dates.txt" 39 "service_id" "土日祝"
"calendar_dates.txt" 40 "service_id" "平日"
"calendar_dates.txt" 41 "service_id" "土日祝"
"calendar_dates.txt" 42 "service_id" "◆"
"calendar_dates.txt" 43 "service_id" "◆"
"calendar_dates.txt" 44 "service_id" "◆"
"calendar_dates.txt" 45 "service_id" "◆"
"calendar_dates.txt" 46 "service_id" "◆"
"calendar_dates.txt" 47 "service_id" "◆"
"calendar_dates.txt" 48 "service_id" "◆"
platform_without_parent_station INFO 8

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.
2 "021001_02" "知多半田駅"
3 "021001_03" "知多半田駅"
88 "021045_04" "常滑駅"
91 "021047_05" "中部国際空港"
119 "021069_04" "知立駅"
157 "022018_03" "太田川駅前"
245 "023012_01" "朝倉駅前"
246 "023012_02" "朝倉駅前"
unknown_column INFO 2

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.
"trips.txt" "jp_trip_desc" 9
"trips.txt" "jp_pattern_id" 10