ottop-tokyo-bus-co — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T18:25:28Z,
for the dataset file:///shared/ottop-tokyo-bus-co_19439cc0.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
特定非営利活動法人OTTOP
Publisher URL:
https://ottop.org
Feed Email:
transit@ottop.org
Feed Language:
Japanese
Feed Start Date:
2026-02-04
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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. translations.txt
  14. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 13
  • Stops: 23
  • Trips: 270

Specification Compliance report

581 notices reported (0 errors, 575 warnings, 6 infos)

Notice Code Severity Total
expired_calendar WARNING 4

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.
5 "北谷線実証運行"
6 "TK05全日(2025年2月末まで)"
7 "2024年度年末年始"
10 "2025年末年始特別ダイヤ"
missing_recommended_field WARNING 188

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 188 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.
"feed_info.txt" 2 "feed_version"
"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"
mixed_case_recommended_field WARNING 18

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" "ウミカジライナー(国際通り入口行き)上り線" 9
"routes.txt" "route_long_name" "北谷直行シャトルバス(那覇空港・国際通り入口〜美浜アメリカンビレッジ)" 10
"routes.txt" "route_long_name" "北谷直行シャトルバス(美浜アメリカンビレッジ〜那覇空港・国際通り入口)" 11
"routes.txt" "route_long_name" "ジャングリアエクスプレス(国際通り入口〜ジャングリア沖縄)" 12
"routes.txt" "route_long_name" "ジャングリアエクスプレス(国際通り入口・那覇空港〜ジャングリア沖縄)" 13
"routes.txt" "route_long_name" "ジャングリアエクスプレス(ジャングリア沖縄〜那覇空港・国際通り入口)" 14
"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
non_ascii_or_non_printable_char WARNING 365

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 365 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_dates.txt" 2 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 3 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 4 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 5 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 6 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 7 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 8 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 9 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 10 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 11 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 12 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 13 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 14 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 15 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 16 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 17 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 18 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 19 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 20 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 21 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 22 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 23 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 24 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 25 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 26 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 27 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 28 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 29 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 30 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 31 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 32 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 33 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 34 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 35 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 36 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 37 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 38 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 39 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 40 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 41 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 42 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 43 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 44 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 45 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 46 "service_id" "平日(R6_411-)"
"calendar_dates.txt" 47 "service_id" "土日祝(R6_411-)"
"calendar_dates.txt" 48 "service_id" "土日祝(R6_411-)"
"calendar_dates.txt" 49 "service_id" "土日祝(R6_411-)"
"calendar_dates.txt" 50 "service_id" "土日祝(R6_411-)"
"calendar_dates.txt" 51 "service_id" "土日祝(R6_411-)"
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 "S5396" "那覇空港"
16 "S6094" "那覇空港"
18 "S6096" "那覇空港"
20 "S6100" "那覇空港"
22 "S6095" "那覇空港"
23 "S5899" "北谷ゲートウェイ"