Home
Japan Feeds
tokubus-tokushimabus
Source Data Validation Report

tokubus-tokushimabus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T04:03:54Z,
for the dataset file:///shared/tokubus-tokushimabus_2aa4aea8.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

徳島バス
- website: https://www.tokubus.co.jp/routebus/
- phone number: 088-622-1811
- email: Not provided

Feed Info

Publisher Name:
徳島バス: Publisher URL:
https://www.tokubus.co.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2026-04-01: Feed End Date:
2027-03-31: Service Window:
2026-04-01 to 2027-03-31 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 85
Shapes: 209
Stops: 1620
Trips: 1888

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Feed Information Translations Fares V1 Route Colors Headsigns

Specification Compliance report

170 notices reported (0 errors, 153 warnings, 17 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`.
85	"5301"	86	"5391"	""	"室戸・生見・阿南大阪線"	3	"4480001001730"

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

mixed_case_recommended_field WARNING 151

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 151 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"	"16 鳴門線"	2
"routes.txt"	"route_long_name"	"23 鳴門線"	3
"routes.txt"	"route_long_name"	"15 鳴門線"	4
"routes.txt"	"route_long_name"	"17 鳴門線"	5
"routes.txt"	"route_long_name"	"97 鳴門公園線"	6
"routes.txt"	"route_long_name"	"98 鳴門公園線"	7
"routes.txt"	"route_long_name"	"18 鳴門線"	8
"routes.txt"	"route_long_name"	"25 鳴門線"	9
"routes.txt"	"route_long_name"	"21 鳴門線"	10
"routes.txt"	"route_long_name"	"33 立道線"	11
"routes.txt"	"route_long_name"	"38 応神北島線"	12
"routes.txt"	"route_long_name"	"28 鍛冶屋原線"	13
"routes.txt"	"route_long_name"	"39 応神藍住線"	14
"routes.txt"	"route_long_name"	"52 鴨島線"	15
"routes.txt"	"route_long_name"	"53 石井・高原線"	16
"routes.txt"	"route_long_name"	"51 鴨島線"	17
"routes.txt"	"route_long_name"	"15 不動線"	18
"routes.txt"	"route_long_name"	"43 竜王団地線"	19
"routes.txt"	"route_long_name"	"56 神山線"	20
"routes.txt"	"route_long_name"	"17 ⑰号線"	21
"routes.txt"	"route_long_name"	"5 ⑰号線"	22
"routes.txt"	"route_long_name"	"17 天の原西線"	23
"routes.txt"	"route_long_name"	"48 鍛冶屋原線"	25
"routes.txt"	"route_long_name"	"47 鍛冶屋原線"	26
"routes.txt"	"route_long_name"	"16 不動線"	27
"routes.txt"	"route_long_name"	"31 中央循環線"	28
"routes.txt"	"route_long_name"	"6 島田石橋線"	29
"routes.txt"	"route_long_name"	"13 大神子線"	30
"routes.txt"	"route_long_name"	"14 大神子線"	31
"routes.txt"	"route_long_name"	"82 勝浦線"	32
"routes.txt"	"route_long_name"	"81 小松島線"	33
"routes.txt"	"route_long_name"	"87 橘線"	34
"routes.txt"	"route_long_name"	"6 市原線"	35
"routes.txt"	"route_long_name"	"6 市原線・島田石橋線"	36
"routes.txt"	"route_long_name"	"7 市原線"	37
"routes.txt"	"route_long_name"	"62 佐那河内線"	38
"routes.txt"	"route_long_name"	"18 一宮線"	39
"routes.txt"	"route_long_name"	"11 五滝線"	40
"routes.txt"	"route_long_name"	"12 五滝線"	41
"routes.txt"	"route_long_name"	"11 渋野線"	42
"routes.txt"	"route_long_name"	"33 南部循環線"	43
"routes.txt"	"route_long_name"	"9 山城線"	44
"routes.txt"	"route_long_name"	"2 法花線"	45
"routes.txt"	"route_long_name"	"3 中央市場線"	46
"routes.txt"	"route_long_name"	"オーシャン東九フェリー線（徳島駅前直行便）"	47
"routes.txt"	"route_long_name"	"1 津田線"	48
"routes.txt"	"route_long_name"	"24 津田線"	49
"routes.txt"	"route_long_name"	"1 新浜線"	50
"routes.txt"	"route_long_name"	"1 上鮎喰線"	51
"routes.txt"	"route_long_name"	"10 上鮎喰線"	52

platform_without_parent_station INFO 17

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.
650	"3_1"	"徳島駅前"
651	"3_12"	"徳島駅前"
652	"3_13"	"徳島駅前"
653	"3_14"	"徳島駅前"
654	"3_15"	"徳島駅前"
655	"3_16"	"徳島駅前"
656	"3_2"	"徳島駅前"
657	"3_3"	"徳島駅前"
659	"3_4"	"徳島駅前"
660	"3_5"	"徳島駅前"
661	"3_6"	"徳島駅前"
662	"3_7"	"徳島駅前"
977	"57_1"	"松茂"
978	"57_2"	"松茂"
979	"57_3"	"松茂"
980	"57_4"	"松茂"
1525	"94_2"	"徳島阿波おどり空港"