GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T20:49:57Z,
for the dataset file:///shared/shonaitown.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-05-07
Feed End Date:
2026-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: 8
  • Shapes: 0
  • Stops: 128
  • Trips: 38

Specification Compliance report

2165 notices reported (0 errors, 2163 warnings, 2 infos)

Notice Code Severity Total
duplicate_route_name WARNING 2

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`.
2 "10" 8 "41" "" "幹線路線（立谷沢余目線）" 3 "9000020064289"
2 "10" 9 "42" "" "幹線路線（立谷沢余目線）" 3 "9000020064289"
expired_calendar WARNING 2

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.
13 "月～金の平日（スクールバス夏季運行）"
15 "立川中（立川小）スクールバス夏季運行日"
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 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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "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" "幹線路線（立谷沢余目線）" 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" "幹線路線（立谷沢余目線）" 8
"routes.txt" "route_long_name" "幹線路線（立谷沢余目線）" 9
"stops.txt" "stop_name" "オハナ・デンタル" 33
"stops.txt" "stop_name" "古関（幹線）" 67
"stops.txt" "stop_name" "古関（循環）" 68
"trips.txt" "trip_headsign" "古関（循環）" 16
non_ascii_or_non_printable_char WARNING 2143

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 2143 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" "幹線1便（鉢子（往路））月～金"
"calendar.txt" 3 "service_id" "幹線1便（鉢子（往路））土日祝"
"calendar.txt" 4 "service_id" "幹線1便（鉢子（復路））月水金日"
"calendar.txt" 5 "service_id" "幹線1便（中村（復路））火木土"
"calendar.txt" 6 "service_id" "幹線2便（鉢子）月水金"
"calendar.txt" 7 "service_id" "幹線2便（中村）火木土"
"calendar.txt" 8 "service_id" "幹線3便（鉢子）月水金日"
"calendar.txt" 9 "service_id" "幹線3便（中村）火木土"
"calendar.txt" 10 "service_id" "月水金"
"calendar.txt" 11 "service_id" "火木土"
"calendar.txt" 12 "service_id" "月～土"
"calendar.txt" 13 "service_id" "月～金の平日（スクールバス夏季運行）"
"calendar.txt" 14 "service_id" "月～金の平日（スクールバス冬季運行）"
"calendar.txt" 15 "service_id" "立川中（立川小）スクールバス夏季運行日"
"calendar.txt" 16 "service_id" "立川中（立川小）スクールバス冬季運行日"
"calendar.txt" 17 "service_id" "月（循環1コース3便）"
"calendar.txt" 18 "service_id" "水金（循環1コース3便）"
"calendar.txt" 19 "service_id" "火木（循環3コース3便）"
"calendar.txt" 20 "service_id" "土（循環3コース3便）"
"calendar_dates.txt" 2 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 3 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 4 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 5 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 6 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 7 "service_id" "火木（循環3コース3便）"
"calendar_dates.txt" 8 "service_id" "火木（循環3コース3便）"
"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" "幹線1便（中村（復路））火木土"
"calendar_dates.txt" 17 "service_id" "幹線1便（中村（復路））火木土"
"calendar_dates.txt" 18 "service_id" "幹線1便（中村（復路））火木土"
"calendar_dates.txt" 19 "service_id" "幹線1便（中村（復路））火木土"
"calendar_dates.txt" 20 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 21 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 22 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 23 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 24 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 25 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 26 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 27 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 28 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 29 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 30 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 31 "service_id" "幹線1便（鉢子（往路））月～金"
"calendar_dates.txt" 32 "service_id" "幹線1便（鉢子（往路））月～金"
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