Search
  1. Home
  2. Japan Feeds
  3. tokyubus-tokyubus-community
  4. Source Data Validation Report

tokyubus-tokyubus-community — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-18T01:52:53Z,
for the dataset file:///shared/tokyubus-tokyubus-community_3e9e1015.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:
2026-02-01
Feed End Date:
2026-05-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. office_jp.txt
  8. routes.txt
  9. stop_times.txt
  10. stops.txt
  11. translations.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 0
  • Stops: 50
  • Trips: 350

Specification Compliance report

495 notices reported (0 errors, 440 warnings, 55 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 3

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"
"fare_attributes.txt" 4 "agency_id"
mixed_case_recommended_field WARNING 5

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
"stops.txt" "stop_name" "上大崎２丁目" 19
non_ascii_or_non_printable_char WARNING 431

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 431 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" "休日_66"
"calendar.txt" 3 "service_id" "休日_68"
"calendar.txt" 4 "service_id" "休日_69"
"calendar.txt" 5 "service_id" "土曜_66"
"calendar.txt" 6 "service_id" "土曜_68"
"calendar.txt" 7 "service_id" "土曜_69"
"calendar.txt" 8 "service_id" "平日_66"
"calendar.txt" 9 "service_id" "平日_68"
"calendar.txt" 10 "service_id" "平日_69"
"calendar_dates.txt" 2 "service_id" "休日_66"
"calendar_dates.txt" 3 "service_id" "休日_66"
"calendar_dates.txt" 4 "service_id" "休日_66"
"calendar_dates.txt" 5 "service_id" "休日_66"
"calendar_dates.txt" 6 "service_id" "休日_66"
"calendar_dates.txt" 7 "service_id" "休日_66"
"calendar_dates.txt" 8 "service_id" "休日_66"
"calendar_dates.txt" 9 "service_id" "休日_66"
"calendar_dates.txt" 10 "service_id" "休日_68"
"calendar_dates.txt" 11 "service_id" "休日_68"
"calendar_dates.txt" 12 "service_id" "休日_68"
"calendar_dates.txt" 13 "service_id" "休日_68"
"calendar_dates.txt" 14 "service_id" "休日_68"
"calendar_dates.txt" 15 "service_id" "休日_68"
"calendar_dates.txt" 16 "service_id" "休日_68"
"calendar_dates.txt" 17 "service_id" "休日_68"
"calendar_dates.txt" 18 "service_id" "休日_69"
"calendar_dates.txt" 19 "service_id" "休日_69"
"calendar_dates.txt" 20 "service_id" "休日_69"
"calendar_dates.txt" 21 "service_id" "休日_69"
"calendar_dates.txt" 22 "service_id" "休日_69"
"calendar_dates.txt" 23 "service_id" "休日_69"
"calendar_dates.txt" 24 "service_id" "休日_69"
"calendar_dates.txt" 25 "service_id" "休日_69"
"calendar_dates.txt" 26 "service_id" "土曜_66"
"calendar_dates.txt" 27 "service_id" "土曜_66"
"calendar_dates.txt" 28 "service_id" "土曜_66"
"calendar_dates.txt" 29 "service_id" "土曜_66"
"calendar_dates.txt" 30 "service_id" "土曜_66"
"calendar_dates.txt" 31 "service_id" "土曜_66"
"calendar_dates.txt" 32 "service_id" "土曜_66"
"calendar_dates.txt" 33 "service_id" "土曜_66"
"calendar_dates.txt" 34 "service_id" "土曜_68"
"calendar_dates.txt" 35 "service_id" "土曜_68"
"calendar_dates.txt" 36 "service_id" "土曜_68"
"calendar_dates.txt" 37 "service_id" "土曜_68"
"calendar_dates.txt" 38 "service_id" "土曜_68"
"calendar_dates.txt" 39 "service_id" "土曜_68"
"calendar_dates.txt" 40 "service_id" "土曜_68"
"calendar_dates.txt" 41 "service_id" "土曜_68"
"calendar_dates.txt" 42 "service_id" "土曜_69"
platform_without_parent_station INFO 50

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.
2 "1715509_1" "東京共済病院前"
3 "1715510_1" "目黒警察署前"
4 "1725503_2" "正覚寺前"
5 "1725524_1" "目黒区総合庁舎前"
6 "1725524_2" "目黒区総合庁舎前"
7 "1735607_1" "茶屋坂"
8 "1735607_2" "茶屋坂"
9 "1735608_1" "中里橋"
10 "1735801_8" "目黒駅前"
11 "1735901_1" "目黒区総合庁舎"
12 "1735902_1" "東京共済病院"
13 "1735903_1" "中目黒スクエア前"
14 "1735904_1" "恵比寿南一公園前"
15 "1735905_1" "厚生中央病院前"
16 "1735906_1" "三田一丁目"
17 "1735907_1" "目黒三田会館前"
18 "1735908_1" "目黒一丁目"
19 "1735909_1" "上大崎２丁目"
20 "1735910_1" "三田公園前"
21 "1735911_1" "田道ふれあい館前"
22 "1735912_1" "なかめ公園橋前"
23 "1735913_1" "恵比寿ガーデンプレイス南"
24 "1740115_2" "池上八丁目"
25 "1740116_2" "矢口小学校"
26 "1740314_1" "大井五丁目"
27 "1740314_2" "大井五丁目"
28 "1740315_1" "伊藤学園"
29 "1740315_2" "伊藤学園"
30 "1740316_1" "西大井二丁目"
31 "1740316_2" "西大井二丁目"
32 "1740317_1" "大井原町"
33 "1740317_2" "大井原町"
34 "1740318_3" "西大井駅"
35 "1740319_2" "大森駅北口"
36 "1740320_1" "品川歴史館北"
37 "1740320_2" "品川歴史館北"
38 "1740321_1" "さくら会前"
39 "1740321_2" "さくら会前"
40 "1746001_1" "武蔵新田駅"
41 "1746003_1" "下丸子駅入口"
42 "1746004_1" "オリンピック下丸子店前"
43 "1746005_1" "キヤノン本社通用門前"
44 "1746006_1" "白洋舎前"
45 "1746007_1" "ガス橋二十一世紀桜"
46 "1746008_1" "矢口中学校"
47 "1746009_1" "下丸子図書館入口"
48 "1746010_1" "稲葉製作所前"
49 "1746011_1" "矢口特別出張所入口"
50 "1746012_1" "延命寺前"
51 "1746013_1" "矢口三丁目"
unknown_column INFO 4

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.
"routes.txt" "jp_parent_route_id" 11
"trips.txt" "jp_trip_desc" 11
"trips.txt" "jp_trip_desc_symbol" 12
"trips.txt" "jp_office_id" 13
unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"office_jp.txt"