GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:13:37Z,
for the dataset file:///shared/east-mikawa3.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:
2019-10-01
Feed End Date:
2020-12-31

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 13
  • Stops: 114
  • Trips: 135

Specification Compliance report

5543 notices reported (3 errors, 5537 warnings, 3 infos)

Notice Code Severity Total
missing_required_column ERROR 3

missing_required_column

A required column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the missing column.
"translations.txt" "field_name"
"translations.txt" "language"
"translations.txt" "table_name"
duplicate_route_name WARNING 7

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 "13030" 4 "13040" "[97]新豊線" "新豊線" 3 "6180301008850"
5 "13110" 6 "13120" "[90]豊川線" "豊川線" 3 "6180301008850"
7 "13130" 8 "13140" "[92]豊川線" "豊川線" 3 "6180301008850"
9 "13150" 10 "13160" "[91]豊川線" "豊川線" 3 "6180301008850"
11 "13170" 12 "13180" "[94]豊川線" "豊川線" 3 "6180301008850"
11 "13170" 13 "13190" "[94]豊川線" "豊川線" 3 "6180301008850"
11 "13170" 14 "13200" "[94]豊川線" "豊川線" 3 "6180301008850"
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.
2 "平日"
3 "土日祝"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251212" "20201231" "20251219"
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 46

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"
"fare_attributes.txt" 12 "agency_id"
"fare_attributes.txt" 13 "agency_id"
"fare_attributes.txt" 14 "agency_id"
"fare_attributes.txt" 15 "agency_id"
"fare_attributes.txt" 16 "agency_id"
"fare_attributes.txt" 17 "agency_id"
"fare_attributes.txt" 18 "agency_id"
"fare_attributes.txt" 19 "agency_id"
"fare_attributes.txt" 20 "agency_id"
"fare_attributes.txt" 21 "agency_id"
"fare_attributes.txt" 22 "agency_id"
"fare_attributes.txt" 23 "agency_id"
"fare_attributes.txt" 24 "agency_id"
"fare_attributes.txt" 25 "agency_id"
"fare_attributes.txt" 26 "agency_id"
"fare_attributes.txt" 27 "agency_id"
"fare_attributes.txt" 28 "agency_id"
"fare_attributes.txt" 29 "agency_id"
"fare_attributes.txt" 30 "agency_id"
"fare_attributes.txt" 31 "agency_id"
"fare_attributes.txt" 32 "agency_id"
"fare_attributes.txt" 33 "agency_id"
"fare_attributes.txt" 34 "agency_id"
"fare_attributes.txt" 35 "agency_id"
"fare_attributes.txt" 36 "agency_id"
"fare_attributes.txt" 37 "agency_id"
"fare_attributes.txt" 38 "agency_id"
"fare_attributes.txt" 39 "agency_id"
"fare_attributes.txt" 40 "agency_id"
"fare_attributes.txt" 41 "agency_id"
"fare_attributes.txt" 42 "agency_id"
"fare_attributes.txt" 43 "agency_id"
"fare_attributes.txt" 44 "agency_id"
"fare_attributes.txt" 45 "agency_id"
"fare_attributes.txt" 46 "agency_id"
"fare_attributes.txt" 47 "agency_id"
mixed_case_recommended_field WARNING 116

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.

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

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_short_name" "[95]新豊線" 2
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間に迂回運行（開運通二丁目・開運通一丁目・稲荷前・豊川駅前・進雄神社バス停通過、イオン豊川店・豊川東部中学校バス停位置変更）" 2
"routes.txt" "route_short_name" "[97]新豊線" 3
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間に迂回運行（開運通二丁目・開運通一丁目・稲荷前・豊川駅前・進雄神社バス停通過、イオン豊川店・豊川東部中学校バス停位置変更）" 3
"routes.txt" "route_short_name" "[97]新豊線" 4
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間に迂回運行（開運通二丁目・開運通一丁目・稲荷前・豊川駅前・進雄神社バス停通過、イオン豊川店・豊川東部中学校バス停位置変更）" 4
"routes.txt" "route_short_name" "[90]豊川線" 5
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行" 5
"routes.txt" "route_short_name" "[90]豊川線" 6
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行" 6
"routes.txt" "route_short_name" "[92]豊川線" 7
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間の豊川駅前着8：00～17：00または18：00の便は迂回運行（免許センター・金屋元町・イオン豊川店・開運通二丁目・開運通一丁目・稲荷前バス停通過）" 7
"routes.txt" "route_short_name" "[92]豊川線" 8
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間の豊川駅前発8：00～17：00の便は迂回運行（稲荷前・開運通一丁目・開運通二丁目・イオン豊川店・金屋元町バス停通過）" 8
"routes.txt" "route_short_name" "[91]豊川線" 9
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行" 9
"routes.txt" "route_short_name" "[91]豊川線" 10
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行" 10
"routes.txt" "route_short_name" "[94]豊川線" 11
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間の豊川駅前着8：00～17：00または18：00の便は迂回運行（免許センター・金屋元町・イオン豊川店・開運通二丁目・開運通一丁目・稲荷前バス停通過）" 11
"routes.txt" "route_short_name" "[94]豊川線" 12
"routes.txt" "route_desc" "8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間の豊川駅前発8：00～17：00の便は迂回運行（稲荷前・開運通一丁目・開運通二丁目・イオン豊川店・金屋元町バス停通過）" 12
"routes.txt" "route_short_name" "[94]豊川線" 13
"routes.txt" "route_desc" "豊川駅前から豊川市コミュニティバス一宮線本宮の湯行きに直通運行、8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間に迂回運行（免許センター・金屋元町・イオン豊川店・開運通二丁目・開運通一丁目・稲荷前バス停通過、迂回期間中は直通運行なし）" 13
"routes.txt" "route_short_name" "[94]豊川線" 14
"routes.txt" "route_desc" "豊川駅前で豊川市コミュニティバス一宮線本宮の湯発から直通運行、8/13～8/15・12/29～1/3は休日ダイヤで運行、別にお知らせする正月期間に迂回運行（稲荷前・開運通一丁目・開運通二丁目・イオン豊川店・金屋元町バス停通過、迂回期間中は直通運行なし）" 14
"stops.txt" "stop_name" "こども未来館・商工会議所" 4
"stops.txt" "stop_name" "こども未来館・商工会議所" 5
"stops.txt" "stop_name" "新城栄町・新城駅口" 10
"stops.txt" "stop_name" "新城栄町・新城駅口" 11
"trips.txt" "trip_headsign" "新城富永行き（豊川市民病院 経由）" 7
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 10
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 11
"trips.txt" "trip_headsign" "豊川駅前行き（豊川市民病院 経由）" 12
"trips.txt" "trip_headsign" "豊川駅前行き（豊川市民病院 経由）" 13
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 15
"trips.txt" "trip_headsign" "新城富永行き（豊川市民病院 経由）" 16
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 17
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 18
"trips.txt" "trip_headsign" "豊川駅前行き（豊川市民病院 経由）" 19
"trips.txt" "trip_headsign" "本宮の湯行き（豊川市民病院 経由）" 20
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 21
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 23
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 24
"trips.txt" "trip_headsign" "本宮の湯行き（豊川市民病院 経由）" 25
"trips.txt" "trip_headsign" "新城富永行き（豊川市民病院 経由）" 26
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 29
"trips.txt" "trip_headsign" "豊川駅前行き（豊川市民病院 経由）" 30
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 31
"trips.txt" "trip_headsign" "豊橋駅前行き（豊川市民病院 経由）" 33
non_ascii_or_non_printable_char WARNING 5363

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 5363 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_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" "平日"
"calendar_dates.txt" 49 "service_id" "土日祝"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20251212" "20191001" "20201231"
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.
"translations.txt" "trans_id" 1
"translations.txt" "lang" 2
unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

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