Home
Japan Feeds
shodoshimaolivebus2
Source Data Validation Report

shodoshimaolivebus2 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-22T02:18:11Z,
for the dataset file:///shared/shodoshimaolivebus2_2b2755ed.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

小豆島オリーブバス
- website: https://www.shodoshima-olive-bus.com/
- phone number: 0879-62-0171
- email: olibus1@olive-bus.com

Feed Info

Publisher Name:
小豆島オリーブバス株式会社: Publisher URL:
https://www.shodoshima-olive-bus.com/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2025-09-01: Feed End Date:
2026-09-30: Service Window:
2025-09-01 to 2026-09-30 (?) 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
agency_jp.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
frequencies.txt
office_jp.txt
pattern_jp.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 20
Shapes: 42
Stops: 295
Trips: 329

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

TransfersShapesFeed InformationTranslationsFares V1Route ColorsHeadsignsLocation Types

Specification Compliance report

9913 notices reported (0 errors, 9905 warnings, 8 infos)

Notice Code Severity Total

duplicate_route_name WARNING 8

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	"000061"	4	"000063"	""	"北廻り福田線"	3	"2470001012482"
5	"000041"	6	"000043"	""	"坂手線"	3	"2470001012482"
5	"000041"	7	"000045"	""	"坂手線"	3	"2470001012482"
5	"000041"	8	"000047"	""	"坂手線"	3	"2470001012482"
14	"000068"	15	"000069"	""	"中山線"	3	"2470001012482"
16	"000066"	17	"000067"	""	"西浦線"	3	"2470001012482"
16	"000066"	18	"000087"	""	"西浦線"	3	"2470001012482"
16	"000066"	19	"000088"	""	"西浦線"	3	"2470001012482"

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 6

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"
"fare_attributes.txt"	5	"agency_id"
"fare_attributes.txt"	6	"agency_id"
"fare_attributes.txt"	7	"agency_id"

missing_timepoint_value WARNING 9385

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's `stop_times.trip_id`.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2	"00_00_000001_001_0710"	1
3	"00_00_000001_001_0710"	2
4	"00_00_000001_001_0710"	3
5	"00_00_000001_001_0710"	4
6	"00_00_000001_001_0710"	5
7	"00_00_000001_001_0710"	6
8	"00_00_000001_001_0710"	7
9	"00_00_000001_001_0710"	8
10	"00_00_000001_001_0710"	9
11	"00_00_000001_001_0710"	10
12	"00_00_000001_001_0710"	11
13	"00_00_000001_001_0710"	12
14	"00_00_000001_001_0710"	13
15	"00_00_000001_001_0710"	14
16	"00_00_000001_001_0710"	15
17	"00_00_000001_001_0710"	16
18	"00_00_000001_001_0710"	17
19	"00_00_000001_001_0710"	18
20	"00_00_000001_001_0710"	19
21	"00_00_000001_001_0710"	20
22	"00_00_000001_001_0710"	21
23	"00_00_000001_001_0710"	22
24	"00_00_000001_001_0710"	23
25	"00_00_000001_001_0710"	24
26	"00_00_000001_001_0710"	25
27	"00_00_000001_001_0710"	26
28	"00_00_000001_001_0710"	27
29	"00_00_000001_001_0710"	28
30	"00_00_000001_001_0710"	29
31	"00_00_000001_001_0710"	30
32	"00_00_000001_001_0710"	31
33	"00_00_000001_001_0710"	32
34	"00_00_000001_001_0710"	33
35	"00_00_000001_001_0710"	34
36	"00_00_000001_001_0710"	35
37	"00_00_000001_001_0710"	36
38	"00_00_000001_001_0710"	37
39	"00_00_000001_001_0710"	38
40	"00_00_000001_001_0710"	39
41	"00_00_000001_001_0710"	40
42	"00_00_000001_001_0710"	41
43	"00_00_000001_001_0710"	42
44	"00_00_000001_001_0710"	43
45	"00_00_000001_001_0710"	44
46	"00_00_000001_001_0710"	45
47	"00_00_000001_001_0710"	46
48	"00_00_000001_003_1010"	1
49	"00_00_000001_003_1010"	2
50	"00_00_000001_003_1010"	3
51	"00_00_000001_003_1010"	4

mixed_case_recommended_field WARNING 337

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 337 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"	"豊島シャトルバス（唐櫃線）"	12
"routes.txt"	"route_long_name"	"豊島シャトルバス（甲生線）"	13
"stops.txt"	"stop_name"	"国際ホテル（エンジェルロード前）"	172
"stops.txt"	"stop_name"	"国際ホテル（エンジェルロード前）"	173
"stops.txt"	"stop_name"	"小豆島大観音前（しあわせの駅）"	243
"stops.txt"	"stop_name"	"小豆島大観音前（しあわせの駅）"	244
"stops.txt"	"stop_name"	"池田内科クリニック（池田港前）"	270
"stops.txt"	"stop_name"	"池田内科クリニック（池田港前）"	271
"trips.txt"	"trip_headsign"	"小豆島中央病院行き"	2
"trips.txt"	"trip_headsign"	"福田港行き"	3
"trips.txt"	"trip_headsign"	"土庄港行き"	4
"trips.txt"	"trip_headsign"	"福田港行き"	5
"trips.txt"	"trip_headsign"	"土庄港行き"	6
"trips.txt"	"trip_headsign"	"土庄港行き"	7
"trips.txt"	"trip_headsign"	"福田港行き"	8
"trips.txt"	"trip_headsign"	"土庄港行き"	9
"trips.txt"	"trip_headsign"	"田ノ浦映画村行き"	10
"trips.txt"	"trip_headsign"	"土庄港行き"	11
"trips.txt"	"trip_headsign"	"土庄港行き"	12
"trips.txt"	"trip_headsign"	"土庄港行き"	13
"trips.txt"	"trip_headsign"	"坂手東行き"	14
"trips.txt"	"trip_headsign"	"土庄港行き"	15
"trips.txt"	"trip_headsign"	"福田港行き"	16
"trips.txt"	"trip_headsign"	"小豆島中央病院行き"	17
"trips.txt"	"trip_headsign"	"福田港行き"	18
"trips.txt"	"trip_headsign"	"土庄港行き"	19
"trips.txt"	"trip_headsign"	"福田港行き"	20
"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
"trips.txt"	"trip_headsign"	"小豆島中央病院行き"	40
"trips.txt"	"trip_headsign"	"土庄港行き"	41
"trips.txt"	"trip_headsign"	"土庄港行き"	42
"trips.txt"	"trip_headsign"	"土庄港行き"	43

translation_unknown_table_name WARNING 168

translation_unknown_table_name

A translation references an unknown or missing GTFS table.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record.	tableName (?) `table_name` of the faulty record.
5	"agency_jp"
6	"agency_jp"
7	"agency_jp"
11	"office_jp"
12	"office_jp"
13	"office_jp"
14	"pattern_jp"
15	"pattern_jp"
16	"pattern_jp"
17	"pattern_jp"
18	"pattern_jp"
19	"pattern_jp"
20	"pattern_jp"
21	"pattern_jp"
22	"pattern_jp"
23	"pattern_jp"
24	"pattern_jp"
25	"pattern_jp"
26	"pattern_jp"
27	"pattern_jp"
28	"pattern_jp"
29	"pattern_jp"
30	"pattern_jp"
31	"pattern_jp"
32	"pattern_jp"
33	"pattern_jp"
34	"pattern_jp"
35	"pattern_jp"
36	"pattern_jp"
37	"pattern_jp"
38	"pattern_jp"
39	"pattern_jp"
40	"pattern_jp"
41	"pattern_jp"
42	"pattern_jp"
43	"pattern_jp"
44	"pattern_jp"
45	"pattern_jp"
46	"pattern_jp"
47	"pattern_jp"
48	"pattern_jp"
49	"pattern_jp"
50	"pattern_jp"
51	"pattern_jp"
52	"pattern_jp"
53	"pattern_jp"
54	"pattern_jp"
55	"pattern_jp"
56	"pattern_jp"
57	"pattern_jp"

unknown_column INFO 5

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"	10
"trips.txt"	"jp_trip_desc"	11
"trips.txt"	"jp_trip_desc_symbol"	12
"trips.txt"	"jp_office_id"	13
"trips.txt"	"jp_pattern_id"	14

unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

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