GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T21:09:31Z,
for the dataset file:///shared/toki.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:
2024-10-01
Feed End Date:
2025-09-30

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: 173
  • Trips: 67

Specification Compliance report

1634 notices reported (0 errors, 1631 warnings, 3 infos)

Notice Code Severity Total
expired_calendar WARNING 5

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 "土日祝"
4 "平日（美濃焼団地線）"
5 "土日祝（美濃焼団地線）"
6 "土日祝（どんぶり会館バーデンパーク線）"
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 "20251205" "20250930" "20251212"
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 2

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"
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.
"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" "市民バス６曽木＝妻木線" 7
"routes.txt" "route_long_name" "市民バス７土岐南北線" 8
"routes.txt" "route_long_name" "市民バス13どんぶり会館バーデンパーク線" 9
"stops.txt" "stop_name" "泉が丘２丁目" 17
"stops.txt" "stop_name" "泉が丘３丁目" 29
"stops.txt" "stop_name" "泉が丘４丁目" 40
"stops.txt" "stop_name" "泉が丘４丁目" 41
"stops.txt" "stop_name" "泉が丘６丁目" 45
"stops.txt" "stop_name" "志野・織部" 105
"stops.txt" "stop_name" "土居北（記念町）" 119
"stops.txt" "stop_name" "細野口（白鳥神社前）" 143
"stops.txt" "stop_name" "泉が丘５丁目" 153
"stops.txt" "stop_name" "泉が丘１丁目" 154
"stops.txt" "stop_name" "泉が丘１丁目" 155
non_ascii_or_non_printable_char WARNING 1602

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 1602 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" "土日祝（どんぶり会館バーデンパーク線）"
"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" "土日祝（美濃焼団地線）"
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.
"20251205" "20241001" "20250930"
platform_without_parent_station INFO 1

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.
30 "121_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