GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T17:50:58Z,
for the dataset file:///shared/rosenzu-kiho.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-12-03
Feed End Date:
2026-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. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. translations.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 3
  • Shapes: 0
  • Stops: 168
  • Trips: 25

Specification Compliance report

1299 notices reported (0 errors, 1296 warnings, 3 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 1

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

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
"stops.txt" "stop_name" "井田舞子[井田舞子橋]" 63
"stops.txt" "stop_name" "上野口[紀宝バイパス]" 77
"stops.txt" "stop_name" "浅里神社前[飛雪の滝キャンプ場]" 127
non_ascii_or_non_printable_char WARNING 1288

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 1288 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" "平日"
"stop_times.txt" 2 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 3 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 4 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 5 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 6 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 7 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 8 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 9 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 10 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 11 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 12 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 13 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 14 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 15 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 16 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 17 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 18 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 19 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 20 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 21 "trip_id" "1全日_06時40分_系統301001"
"stop_times.txt" 22 "trip_id" "1全日_06時40分_系統301001"
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.
62 "143_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