minamishinshu-minamishinshu-takagi-1 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-27T10:11:03Z,
for the dataset file:///shared/minamishinshu-minamishinshu-takagi-1_a7e4dcbd.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-23
Feed End Date:
2026-12-15

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: 1
  • Routes: 7
  • Shapes: 34
  • Stops: 197
  • Trips: 41

Specification Compliance report

1587 notices reported (0 errors, 1581 warnings, 6 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 3

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

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" "E3 喬木村民バス 喬木大島線 せせらぎ" 2
"routes.txt" "route_long_name" "E4 喬木村民バス 氏乗線 そよかぜ" 3
"routes.txt" "route_long_name" "E5 たかぎコミュニティバス 阿島線" 4
"routes.txt" "route_long_name" "E6 たかぎコミュニティバス 伊久間線" 5
"routes.txt" "route_long_name" "E8 喬木村民バス 上平線" 7
"routes.txt" "route_long_name" "E9 喬木村民バス 富田線" 8
"stops.txt" "stop_name" "中央通り3丁目" 6
"stops.txt" "stop_name" "中央通り3丁目" 7
"stops.txt" "stop_name" "名古熊東(信金前)" 8
"stops.txt" "stop_name" "農道1号線入口" 46
"stops.txt" "stop_name" "農道1号線入口" 47
non_ascii_or_non_printable_char WARNING 1566

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 1566 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.txt" 5 "service_id" "登校日"
"calendar.txt" 6 "service_id" "登校日4月~8月"
"calendar.txt" 7 "service_id" "登校日9月・3月"
"calendar.txt" 8 "service_id" "登校日10月~2月"
"calendar.txt" 9 "service_id" "火・金"
"calendar.txt" 10 "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" "月曜日~金曜日"
big_gap_in_service INFO 2

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"登校日" "2026-07-23" "2026-08-20" 27
"登校日4月~8月" "2026-07-23" "2026-08-20" 27
trip_headsign_matches_intermediate_stop INFO 2

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
3 "4登校日_07時30分_系統751002" "運動公園" "4006_01" 14 "4006_01"
6 "1月曜日~金曜日_14時30分_系統751005" "交流センター" "1556_01" 19 "1556_01"
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