GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-02-03T16:40:27Z,
for the dataset file:///shared/tomo-railway_61fdaddc.zip. No country code was provided.

Notice Code

Severity

Total

duplicate_key

ERROR

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file	oldCsvRowNumber (?) The row of the first occurrence.	newCsvRowNumber (?) The row of the other occurrence.	fieldName1 (?) Composite key's first field name.	fieldValue1 (?) Composite key's first value.
"translations.txt"	127	128	"table_name,field_name,language,field_value"	"stops,stop_name,en,三原駅"
"translations.txt"	470	471	"table_name,field_name,language,field_value"	"stops,stop_name,en,寺前"
"translations.txt"	495	496	"table_name,field_name,language,field_value"	"stops,stop_name,en,小林"
"translations.txt"	498	499	"table_name,field_name,language,field_value"	"stops,stop_name,ja__#Hrkt,小林"
"translations.txt"	1202	1203	"table_name,field_name,language,field_value"	"stops,stop_name,en,道上"
"translations.txt"	1205	1206	"table_name,field_name,language,field_value"	"stops,stop_name,ja__#Hrkt,道上"

expired_calendar

WARNING

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.

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

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"1_581_20241027"
3	"1_583_20241027"
4	"1_585_20241027"
5	"1_599_20241229"
6	"1_602_20241231"
7	"1_604_20241231"
8	"1_606_20241231"
9	"1_617_20250401"
10	"1_618_20250401"
11	"1_619_20250401"
12	"1_636_20250621"
13	"1_637_20250621"
14	"1_638_20250621"
15	"1_655_20251001"
16	"1_656_20251001"
17	"1_657_20251001"
20	"1_657_20251229"
24	"3_586_20241027"
25	"3_588_20241027"
26	"3_590_20241027"
27	"3_601_20241229"
28	"3_607_20241231"
29	"3_609_20241231"
30	"3_611_20241231"
31	"3_623_20250401"
32	"3_626_20250401"
33	"3_628_20250401"
34	"3_642_20250621"
35	"3_645_20250621"
36	"3_647_20250621"
37	"3_661_20251001"
38	"3_664_20251001"
39	"3_666_20251001"
42	"3_666_20251229"
46	"5_591_20241027"
47	"5_593_20241027"
48	"5_595_20241027"
49	"5_600_20241229"
50	"5_612_20241231"
51	"5_614_20241231"
52	"5_616_20241231"
53	"5_630_20250401"
54	"5_632_20250401"
55	"5_634_20250401"
56	"5_649_20250621"
57	"5_651_20250621"
58	"5_653_20250621"
59	"5_668_20251001"
60	"5_670_20251001"
61	"5_672_20251001"

missing_feed_contact_email_and_url

WARNING

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

424

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 424 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

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"	"みろくの里・神勝寺直行便"	14
"stops.txt"	"stop_name"	"内海・横田漁港前"	32
"stops.txt"	"stop_name"	"地吹町(老人大学前)"	190
"stops.txt"	"stop_name"	"地吹町(老人大学前)"	191
"stops.txt"	"stop_name"	"リム・ふくやま前"	475
"stops.txt"	"stop_name"	"糸崎3丁目"	528
"stops.txt"	"stop_name"	"糸崎3丁目"	529
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	729
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	730
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	731
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	759
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	760
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	761
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	762
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	763
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	764
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	765
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	766
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	767
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	917
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	918
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	919
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	920
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	921
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	922
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	923
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	924
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	925
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	926
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	927
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	928
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	929
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	930
"trips.txt"	"trip_headsign"	"内海・横田漁港前"	931

same_name_and_description_for_stop

WARNING

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty record.	stopDesc (?) The faulty record's `stop_desc`.
27	"111_226"	"入船町"
64	"232_474"	"河口大橋"
65	"232_475"	"河口大橋"
111	"389_799"	"県立歴史博物館前"
119	"402_824"	"光寿園前"
160	"527_1078"	"市役所北"
161	"528_1079"	"市役所東"
206	"613_1252"	"すこやかセンター前"
249	"721_1470"	"中央図書館ローズコム"
268	"767_1565"	"天下橋"
332	"923_1899"	"ばら公園前"
337	"932_1917"	"東警察署前"
338	"934_1922"	"東中学校前"
351	"999_2055"	"福山駅北口"
357	"1019_2101"	"伏見町"
396	"1128_2321"	"南小学校前"
416	"1149_2369"	"水呑小学校入口"
417	"1149_2370"	"水呑小学校入口"
434	"1175_2429"	"三吉町南"
475	"1292_2676"	"リム・ふくやま前"
486	"1318_2726"	"阿伏兎観音"
499	"1443_2977"	"尾道工業団地"

stop_without_stop_time

WARNING

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
39	"160_327"	"江の浦"
40	"160_328"	"江の浦"
120	"404_828"	"荒神社前"
121	"404_829"	"荒神社前"
343	"968_1989"	"平"
344	"968_1990"	"平"
394	"1124_2313"	"港口"
395	"1124_2314"	"港口"
467	"1274_2642"	"四ツ角"
468	"1275_2641"	"四ツ角"
471	"1278_2648"	"阿藻珍味前"
472	"1278_2649"	"阿藻珍味前"
532	"2047_3677"	"三原駅"

unknown_column

INFO

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"	9
"trips.txt"	"jp_trip_desc_symbol"	10
"trips.txt"	"jp_office_id"	11

unknown_file

INFO

unknown_file

A file is unknown.

You can see more about this notice here.

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

GTFS Schedule Validation Report

Summary

Agencies included

Feed Info

Files included

Counts

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

Specification Compliance report

560 notices reported (6 errors, 547 warnings, 7 infos)

duplicate_key

expired_calendar

missing_feed_contact_email_and_url

missing_recommended_field

mixed_case_recommended_field

same_name_and_description_for_stop

stop_without_stop_time

unknown_column

unknown_file