Home
Japan Feeds
kochi-ekimae-kanko-gtfs-ekimae-expressbus
Source Data Validation Report

kochi-ekimae-kanko-gtfs-ekimae-expressbus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T21:13:09Z,
for the dataset file:///shared/kochi-ekimae-kanko-gtfs-ekimae-expressbus_c3a439fc.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

株式会社高知駅前観光
- website: https://kochiekimaekanko.jp/
- phone number: 088-831-8891
- email: Not provided

Feed Info

Publisher Name:
株式会社高知駅前観光: Publisher URL:
https://kochiekimaekanko.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2026-03-01: Feed End Date:
2026-03-31: Service Window:
2026-03-01 to 2026-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
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 4
Shapes: 4
Stops: 16
Trips: 4

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

ShapesFeed InformationTranslationsRoute ColorsHeadsignsBike AllowedLocation Types

Specification Compliance report

56 notices reported (0 errors, 48 warnings, 8 infos)

Notice Code Severity Total

duplicate_route_name WARNING 2

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`.
2	"スマイルライナー_A"	3	"スマイルライナー_B"	""	"スマイルライナー"	3	"9490001000578_2"
4	"フラットン_A"	5	"フラットン_B"	""	"フラットン"	3	"9490001000578_2"

feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20260323"	"20260331"	"20260422"

mixed_case_recommended_field WARNING 4

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.
"stops.txt"	"stop_name"	"東京ディズニーランド・バスターミナル・ウエスト"	14
"stops.txt"	"stop_name"	"東京ディズニーランド・バスターミナル・ウエスト"	15
"trips.txt"	"trip_headsign"	"高知（徳島経由）"	4
"trips.txt"	"trip_headsign"	"高知（高速鳴門経由）"	5

non_ascii_or_non_printable_char WARNING 40

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.

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.
"calendar.txt"	2	"service_id"	"スマ高知発"
"calendar.txt"	3	"service_id"	"スマ東京発"
"calendar.txt"	4	"service_id"	"フラ高知発"
"calendar.txt"	5	"service_id"	"フラ東京発"
"routes.txt"	2	"route_id"	"スマイルライナー_A"
"routes.txt"	3	"route_id"	"スマイルライナー_B"
"routes.txt"	4	"route_id"	"フラットン_A"
"routes.txt"	5	"route_id"	"フラットン_B"
"stop_times.txt"	2	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	3	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	4	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	5	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	6	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	7	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	8	"trip_id"	"スマ高知発_19時15分_系統1001"
"stop_times.txt"	9	"trip_id"	"フラ高知発_19時40分_系統1101"
"stop_times.txt"	10	"trip_id"	"フラ高知発_19時40分_系統1101"
"stop_times.txt"	11	"trip_id"	"フラ高知発_19時40分_系統1101"
"stop_times.txt"	12	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	13	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	14	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	15	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	16	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	17	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	18	"trip_id"	"スマ東京発_20時00分_系統1002"
"stop_times.txt"	19	"trip_id"	"フラ東京発_21時30分_系統1102"
"stop_times.txt"	20	"trip_id"	"フラ東京発_21時30分_系統1102"
"stop_times.txt"	21	"trip_id"	"フラ東京発_21時30分_系統1102"
"trips.txt"	2	"trip_id"	"スマ高知発_19時15分_系統1001"
"trips.txt"	2	"route_id"	"スマイルライナー_A"
"trips.txt"	2	"service_id"	"スマ高知発"
"trips.txt"	3	"trip_id"	"フラ高知発_19時40分_系統1101"
"trips.txt"	3	"route_id"	"フラットン_A"
"trips.txt"	3	"service_id"	"フラ高知発"
"trips.txt"	4	"trip_id"	"スマ東京発_20時00分_系統1002"
"trips.txt"	4	"route_id"	"スマイルライナー_B"
"trips.txt"	4	"service_id"	"スマ東京発"
"trips.txt"	5	"trip_id"	"フラ東京発_21時30分_系統1102"
"trips.txt"	5	"route_id"	"フラットン_B"
"trips.txt"	5	"service_id"	"フラ東京発"

trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260323"	"20260301"	"20260329"

platform_without_parent_station INFO 8

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.
3	"8206_02"	"はりまや橋観光バスターミナル"
4	"8200_03"	"高知駅バスターミナル"
5	"8200_06"	"高知駅バスターミナル"
6	"31001_01"	"徳島駅前"
9	"31002_02"	"バスタ新宿"
12	"31003_05"	"バスターミナル東京八重洲"
13	"31003_06"	"バスターミナル東京八重洲"
14	"31004_01"	"東京ディズニーランド・バスターミナル・ウエスト"