Home
Japan Feeds
iyotetsubus
Source Data Validation Report

iyotetsubus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T00:18:39Z,
for the dataset file:///shared/iyotetsubus_0ff8c5b6.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

伊予鉄バス株式会社
- website: https://www.iyotetsu.co.jp/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
伊予鉄バス株式会社: Publisher URL:
https://www.iyotetsu.co.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2026-04-15: Feed End Date:
2026-05-31: Service Window:
2026-04-15 to 2026-05-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
office_jp.txt
pattern_jp.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 46
Shapes: 0
Stops: 1094
Trips: 3377

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

Feed Information Translations Fares V1 Route Colors Headsigns Location Types

Specification Compliance report

1545 notices reported (0 errors, 1528 warnings, 17 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 208

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 208 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 1316

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 1316 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.
"stops.txt"	"stop_name"	"別府（拝志）"	90
"stops.txt"	"stop_name"	"別府（拝志）"	91
"stops.txt"	"stop_name"	"五本松（上林）"	101
"stops.txt"	"stop_name"	"三島神社前（保内）"	343
"stops.txt"	"stop_name"	"三島神社前（保内）"	344
"stops.txt"	"stop_name"	"三島神社前（今出）"	456
"stops.txt"	"stop_name"	"パルティ・フジ垣生"	463
"stops.txt"	"stop_name"	"公民館前（石手）"	508
"stops.txt"	"stop_name"	"公民館前（石手）"	509
"stops.txt"	"stop_name"	"公民館前（南斎院）"	545
"stops.txt"	"stop_name"	"金比羅前（吉田）"	567
"stops.txt"	"stop_name"	"金比羅前（吉田）"	568
"stops.txt"	"stop_name"	"金比羅前（内宮）"	658
"stops.txt"	"stop_name"	"金比羅前（内宮）"	659
"stops.txt"	"stop_name"	"久保（粟井）"	679
"stops.txt"	"stop_name"	"久保（粟井）"	680
"stops.txt"	"stop_name"	"土居・湯の山ニュータウン口"	742
"stops.txt"	"stop_name"	"土居・湯の山ニュータウン口"	743
"stops.txt"	"stop_name"	"金比羅前（河之内）"	781
"stops.txt"	"stop_name"	"市役所前（新居浜）"	919
"stops.txt"	"stop_name"	"市役所前（新居浜）"	920
"stops.txt"	"stop_name"	"東京（バスタ新宿）"	1041
"stops.txt"	"stop_name"	"大阪（阪急三番街）"	1049
"stops.txt"	"stop_name"	"有馬温泉（太閤橋）"	1090
"stops.txt"	"stop_name"	"名古屋駅（新幹線口）"	1095
"routes.txt"	"route_long_name"	"⑧番線（松山駅前発着）"	2
"routes.txt"	"route_long_name"	"⑩番線（津田団地）"	3
"routes.txt"	"route_long_name"	"勝岡線（運転免許センター）"	9
"routes.txt"	"route_long_name"	"ひまわりバス東コース　左回り"	11
"routes.txt"	"route_long_name"	"高速バス福岡線（営業）"	12
"routes.txt"	"route_long_name"	"河之内線（白猪滝）"	15
"routes.txt"	"route_long_name"	"空港リムジン（道後発）"	18
"routes.txt"	"route_long_name"	"ひまわりバス西コース　右回り"	19
"routes.txt"	"route_long_name"	"観光港リムジン（道後）"	20
"routes.txt"	"route_short_name"	"高速バス（名古屋）"	22
"routes.txt"	"route_short_name"	"高速バス（大阪・京都）"	23
"routes.txt"	"route_long_name"	"高速バス大阪線（昼行６・１０・１４号）"	23
"routes.txt"	"route_short_name"	"高速バス（岡山）"	24
"routes.txt"	"route_short_name"	"高速バス（徳島）"	25
"routes.txt"	"route_short_name"	"高速バス（神戸）"	26
"routes.txt"	"route_short_name"	"高速バス（福山）"	27
"routes.txt"	"route_long_name"	"福山線（松山インター経由）"	27
"routes.txt"	"route_short_name"	"高速バス（福岡）"	28
"routes.txt"	"route_long_name"	"高速バス福岡線（営業）"	28
"routes.txt"	"route_short_name"	"高速バス（高知）"	29
"routes.txt"	"route_short_name"	"高速（東京・横浜）"	30
"routes.txt"	"route_long_name"	"高速バス東京線（横浜経由）松山系統"	30
"routes.txt"	"route_long_name"	"市坪線（市役所経由）"	31
"routes.txt"	"route_long_name"	"砥部線（市・舟・こどもの城）"	33
"routes.txt"	"route_long_name"	"森松・横河原線（ＣＨ経由）"	35

route_long_name_contains_short_name WARNING 3

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"10006"	7	"井内線"	"井内線"
"10013"	13	"松瀬川線"	"松瀬川線"
"10016"	16	"海上線"	"海上線"

platform_without_parent_station INFO 9

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.
880	"801_1"	"松山市駅"
882	"801_2"	"松山市駅"
883	"801_20"	"松山市駅"
884	"801_21"	"松山市駅"
886	"801_3"	"松山市駅"
887	"801_4"	"松山市駅"
888	"801_5"	"松山市駅"
889	"801_6"	"松山市駅"
890	"801_7"	"松山市駅"

unknown_column INFO 6

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
"shapes.txt"	"shape_dist_traveleded"	5

unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

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