GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T16:26:20Z,
for the dataset file:///shared/ryujin.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Japanese
Feed Start Date:
2025-12-01
Feed End Date:
2026-12-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. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 10
  • Shapes: 14
  • Stops: 453
  • Trips: 76

Specification Compliance report

4150 notices reported (1 errors, 4143 warnings, 6 infos)

Notice Code Severity Total
duplicate_key ERROR 1

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"fare_rules.txt" 4061 4062 "fare_id,route_id" "1249-150,1249-12"
duplicate_route_name WARNING 1

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 "1249-10B" 4 "1249-10C" "81 熊野本宮線" "" 3 "1249-9170001008975"
missing_recommended_field WARNING 236

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.

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

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"
"fare_attributes.txt" 48 "agency_id"
"fare_attributes.txt" 49 "agency_id"
"fare_attributes.txt" 50 "agency_id"
"fare_attributes.txt" 51 "agency_id"
mixed_case_recommended_field WARNING 33

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_short_name" "80 熊野本宮線" 2
"routes.txt" "route_short_name" "81 熊野本宮線" 3
"routes.txt" "route_short_name" "81 熊野本宮線" 4
"routes.txt" "route_short_name" "84 熊野本宮線" 5
"routes.txt" "route_short_name" "85 熊野本宮線" 6
"stops.txt" "stop_name" "南新万１番地" 7
"stops.txt" "stop_name" "南新万１番地" 8
"stops.txt" "stop_name" "龍神温泉（国道）" 229
"stops.txt" "stop_name" "龍神温泉（国道）" 230
"stops.txt" "stop_name" "龍神温泉（温泉街）" 231
"stops.txt" "stop_name" "龍神温泉（温泉街）" 232
"stops.txt" "stop_name" "朝日ヶ丘12番地" 401
"stops.txt" "stop_name" "朝日ヶ丘12番地" 402
"stops.txt" "stop_name" "南部梅林（観梅臨時）" 454
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 21
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 22
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 23
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 24
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 25
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 26
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 27
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 28
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 29
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 30
"trips.txt" "trip_headsign" "外回り 紀伊田辺駅" 31
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 32
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 33
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 34
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 35
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 36
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 37
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 38
"trips.txt" "trip_headsign" "内回り 紀伊田辺駅" 39
non_ascii_or_non_printable_char WARNING 3873

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 3873 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" "1249-みなべ梅林臨時"
"calendar.txt" 3 "service_id" "1249-全日"
"calendar.txt" 4 "service_id" "1249-冬季運休"
"calendar.txt" 5 "service_id" "1249-冬季運転"
"calendar.txt" 6 "service_id" "1249-土日祝日運休"
"calendar.txt" 7 "service_id" "1249-月水金運休"
"calendar.txt" 8 "service_id" "1249-月水金運転"
"calendar.txt" 9 "service_id" "1249-火木運転"
"calendar.txt" 10 "service_id" "1249-聖地巡礼"
"calendar_dates.txt" 2 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 3 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 4 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 5 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 6 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 7 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 8 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 9 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 10 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 11 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 12 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 13 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 14 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 15 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 16 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 17 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 18 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 19 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 20 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 21 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 22 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 23 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 24 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 25 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 26 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 27 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 28 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 29 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 30 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 31 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 32 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 33 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 34 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 35 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 36 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 37 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 38 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 39 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 40 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 41 "service_id" "1249-みなべ梅林臨時"
"calendar_dates.txt" 42 "service_id" "1249-みなべ梅林臨時"
platform_without_parent_station INFO 6

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.
19 "1249-110_01" "紀伊田辺駅"
20 "1249-110_02" "紀伊田辺駅"
192 "1249-197_01" "請川"
193 "1249-197_02" "請川"
194 "1249-197_03" "請川"
195 "1249-197_04" "請川"