ottop-tokyo-bus-co — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-07T22:31:42Z,
for the dataset file:///shared/ottop-tokyo-bus-co_14de9228.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 Language:
Japanese
Feed Start Date:
2024-04-11
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. translations.txt
  12. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 9
  • Shapes: 15
  • Stops: 24
  • Trips: 152

Specification Compliance report

466 notices reported (0 errors, 460 warnings, 6 infos)

Notice Code Severity Total
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`.
5 "101689-793" 10 "101689-895" "Tk04" "瀬長島ホテルエアポートリムジン(那覇空港行)" 3 "101689-7011501003070"
expired_calendar WARNING 1

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.
3 "101689-TK04(土日祝)_20260724迄"
missing_recommended_field WARNING 203

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 203 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 75

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 75 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_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" "ジャングリアエクスプレス(国際通り入口・那覇空港〜ジャングリア沖縄)" 9
"routes.txt" "route_long_name" "瀬長島ホテルエアポートリムジン(那覇空港行)" 10
"stops.txt" "stop_name" "瀬長島ホテル ウミカジテラス" 3
"stops.txt" "stop_name" "サザンビーチホテル&リゾート沖縄" 10
"stops.txt" "stop_name" "那覇商業高校(松山入口)" 12
"stops.txt" "stop_name" "那覇商業高校(松山入口)" 17
"stops.txt" "stop_name" "琉球ホテル&リゾート名城ビーチ" 19
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 7
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 8
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 13
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 14
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 15
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 16
"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
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 40
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 41
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 42
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 43
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 44
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 45
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 46
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 47
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 48
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 49
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 50
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 51
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 52
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 53
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 54
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 55
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 56
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 57
"trips.txt" "trip_headsign" "琉球ホテル&リゾート名城ビーチ" 58
non_ascii_or_non_printable_char WARNING 180

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 180 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" "101689-TK04(土日祝)"
"calendar.txt" 3 "service_id" "101689-TK04(土日祝)_20260724迄"
"calendar.txt" 4 "service_id" "101689-TK05全日(2025年3月以降)"
"calendar.txt" 5 "service_id" "101689-TK06(全日)"
"calendar.txt" 6 "service_id" "101689-全日(R6_411-)"
"calendar.txt" 7 "service_id" "101689-土日祝(R6_411-)"
"calendar.txt" 8 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 2 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 3 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 4 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 5 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 6 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 7 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 8 "service_id" "101689-TK04(土日祝)"
"calendar_dates.txt" 9 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 10 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 11 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 12 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 13 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 14 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 15 "service_id" "101689-土日祝(R6_411-)"
"calendar_dates.txt" 16 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 17 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 18 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 19 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 20 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 21 "service_id" "101689-平日(R6_411-)"
"calendar_dates.txt" 22 "service_id" "101689-平日(R6_411-)"
"trips.txt" 2 "service_id" "101689-平日(R6_411-)"
"trips.txt" 3 "service_id" "101689-平日(R6_411-)"
"trips.txt" 4 "service_id" "101689-平日(R6_411-)"
"trips.txt" 5 "service_id" "101689-土日祝(R6_411-)"
"trips.txt" 6 "service_id" "101689-土日祝(R6_411-)"
"trips.txt" 7 "service_id" "101689-平日(R6_411-)"
"trips.txt" 8 "service_id" "101689-土日祝(R6_411-)"
"trips.txt" 9 "service_id" "101689-全日(R6_411-)"
"trips.txt" 10 "service_id" "101689-全日(R6_411-)"
"trips.txt" 11 "service_id" "101689-全日(R6_411-)"
"trips.txt" 12 "service_id" "101689-全日(R6_411-)"
"trips.txt" 13 "service_id" "101689-全日(R6_411-)"
"trips.txt" 14 "service_id" "101689-全日(R6_411-)"
"trips.txt" 15 "service_id" "101689-全日(R6_411-)"
"trips.txt" 16 "service_id" "101689-全日(R6_411-)"
"trips.txt" 17 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 18 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 19 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 20 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 21 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 22 "service_id" "101689-TK04(土日祝)_20260724迄"
"trips.txt" 23 "service_id" "101689-TK04(土日祝)_20260724迄"
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.
5 "101689-S5396" "那覇空港"
16 "101689-S6094" "那覇空港"
18 "101689-S6096" "那覇空港"
20 "101689-S6100" "那覇空港"
22 "101689-S6095" "那覇空港"
23 "101689-S5899" "北谷ゲートウェイ"