Home
Japan Feeds
yamagata-ogunitown
Source Data Validation Report

yamagata-ogunitown — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T09:37:53Z,
for the dataset file:///shared/yamagata-ogunitown_89e210be.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

小国町
- website: https://www.town.oguni.yamagata.jp/life/1/5/22/
- phone number: 0238-62-2261
- email: choumin@town.oguni.yamagata.jp

Feed Info

Publisher Name:
小国町: Publisher URL:
http://www.town.oguni.yamagata.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2026-04-01: Feed End Date:
2027-03-31: Service Window:
2026-04-12 to 2026-09-13 (?) 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
stop_times.txt
stops.txt
transfers.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 5
Shapes: 0
Stops: 133
Trips: 46

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

3493 notices reported (0 errors, 3491 warnings, 2 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`.
3	"11"	4	"12"	""	"小国町営バス循環線"	3	"9000020064017"

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 5

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"

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
"routes.txt"	"route_long_name"	"小国町営バス南部線"	6

non_ascii_or_non_printable_char WARNING 3479

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 3479 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.
"trips.txt"	2	"trip_id"	"12北部線（焼山通過）_08時15分_系統1104"
"trips.txt"	2	"service_id"	"北部線（焼山通過）"
"trips.txt"	3	"trip_id"	"13北部（焼山通過）徳網単独_08時15分_系統1105"
"trips.txt"	3	"service_id"	"北部（焼山通過）徳網単独"
"trips.txt"	4	"trip_id"	"7北部中野-りふれ_12時10分_系統1106"
"trips.txt"	4	"service_id"	"北部中野-りふれ"
"trips.txt"	5	"trip_id"	"11北部土休日のみ_12時10分_系統1107"
"trips.txt"	5	"service_id"	"北部土休日のみ"
"trips.txt"	6	"trip_id"	"8北部中野-徳網_12時10分_系統1108"
"trips.txt"	6	"service_id"	"北部中野-徳網"
"trips.txt"	7	"trip_id"	"9北部全日運転_15時50分_系統1109"
"trips.txt"	7	"service_id"	"北部全日運転"
"trips.txt"	8	"trip_id"	"10北部平日のみ_18時00分_系統1110"
"trips.txt"	8	"service_id"	"北部平日のみ"
"trips.txt"	9	"trip_id"	"9北部全日運転_16時40分_系統1204"
"trips.txt"	9	"service_id"	"北部全日運転"
"trips.txt"	10	"trip_id"	"7北部中野-りふれ_09時05分_系統1206"
"trips.txt"	10	"service_id"	"北部中野-りふれ"
"trips.txt"	11	"trip_id"	"11北部土休日のみ_09時15分_系統1207"
"trips.txt"	11	"service_id"	"北部土休日のみ"
"trips.txt"	12	"trip_id"	"8北部中野-徳網_09時10分_系統1208"
"trips.txt"	12	"service_id"	"北部中野-徳網"
"trips.txt"	13	"trip_id"	"5北部線_13時10分_系統1211"
"trips.txt"	13	"service_id"	"北部線"
"trips.txt"	14	"trip_id"	"6北部徳網単独_13時25分_系統1212"
"trips.txt"	14	"service_id"	"北部徳網単独"
"trips.txt"	15	"trip_id"	"23北部平日、幸町・小学校前経由_07時14分_系統1221"
"trips.txt"	15	"service_id"	"北部平日、幸町・小学校前経由"
"trips.txt"	16	"trip_id"	"15南部線_08時12分_系統2113"
"trips.txt"	16	"service_id"	"南部線"
"trips.txt"	17	"trip_id"	"16南部火曜無し_11時50分_系統2114"
"trips.txt"	17	"service_id"	"南部火曜無し"
"trips.txt"	18	"trip_id"	"16南部火曜無し_15時50分_系統2114"
"trips.txt"	18	"service_id"	"南部火曜無し"
"trips.txt"	19	"trip_id"	"18南部小玉川_11時50分_系統2115"
"trips.txt"	19	"service_id"	"南部小玉川"
"trips.txt"	20	"trip_id"	"18南部小玉川_15時50分_系統2115"
"trips.txt"	20	"service_id"	"南部小玉川"
"trips.txt"	21	"trip_id"	"22南部平日のみ・小学校前通過_18時00分_系統2116"
"trips.txt"	21	"service_id"	"南部平日のみ・小学校前通過"
"trips.txt"	22	"trip_id"	"19南部線夏_08時12分_系統2117"
"trips.txt"	22	"service_id"	"南部線夏"
"trips.txt"	23	"trip_id"	"20南部夏火曜無し_11時50分_系統2118"
"trips.txt"	23	"service_id"	"南部夏火曜無し"
"trips.txt"	24	"trip_id"	"20南部夏火曜無し_15時50分_系統2118"
"trips.txt"	24	"service_id"	"南部夏火曜無し"
"trips.txt"	25	"trip_id"	"21南部夏小玉川_11時50分_系統2119"
"trips.txt"	25	"service_id"	"南部夏小玉川"
"trips.txt"	26	"trip_id"	"21南部夏小玉川_15時50分_系統2119"
"trips.txt"	26	"service_id"	"南部夏小玉川"

unknown_column INFO 2

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.
"trips.txt"	"jp_trip_desc"	9
"trips.txt"	"jp_pattern_id"	10