Home
Japan Feeds
utoshi
Source Data Validation Report

utoshi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-11T19:40:45Z,
for the dataset file:///shared/utoshi_8d33432e.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

宇土市コミュニティ
- website: https://www.city.uto.lg.jp/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
ジョルダン株式会社: Publisher URL:
http://www.jorudan.co.jp: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2020-09-01: Feed End Date:
2021-02-28: Service Window:
2020-09-01 to 2021-02-27 (?) 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
routes.txt
routes_jp.txt
stop_times.txt
stops.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 7
Shapes: 0
Stops: 207
Trips: 25

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

Feed InformationTranslationsFares V1Route ColorsHeadsignsLocation Types

Specification Compliance report

47 notices reported (0 errors, 36 warnings, 11 infos)

Notice Code Severity Total

expired_calendar WARNING 5

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.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"S1"
3	"S2"
4	"S3"
5	"S4"
6	"S5"

feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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	"20260911"	"20210228"	"20260918"

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 3

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.
"feed_info.txt"	2	"feed_version"
"fare_attributes.txt"	2	"agency_id"
"fare_attributes.txt"	3	"agency_id"

mixed_case_recommended_field WARNING 25

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"	"緑川切所［網津直築］"	10
"stops.txt"	"stop_name"	"緑川切所［網津直築］"	11
"stops.txt"	"stop_name"	"辺田・厳島神社前"	12
"stops.txt"	"stop_name"	"辺田・厳島神社前"	13
"stops.txt"	"stop_name"	"下新開区公民館［地域学習Ｃ］"	16
"stops.txt"	"stop_name"	"下新開区公民館［地域学習Ｃ］"	17
"stops.txt"	"stop_name"	"北走区公民館［地域学習Ｃ］"	34
"stops.txt"	"stop_name"	"北走区公民館［地域学習Ｃ］"	35
"stops.txt"	"stop_name"	"駅前団地［宇土駅］"	52
"stops.txt"	"stop_name"	"駅前団地［宇土駅］"	53
"stops.txt"	"stop_name"	"クロス２１ＵＴＯ"	111
"stops.txt"	"stop_name"	"クロス２１ＵＴＯ"	112
"stops.txt"	"stop_name"	"石橋・佐伯商店前"	131
"stops.txt"	"stop_name"	"石橋・佐伯商店前"	132
"stops.txt"	"stop_name"	"栗崎・神原"	137
"stops.txt"	"stop_name"	"栗崎・神原"	138
"stops.txt"	"stop_name"	"宇土本町一丁目・宇土高校入口"	149
"stops.txt"	"stop_name"	"宇土本町一丁目・宇土高校入口"	150
"stops.txt"	"stop_name"	"神馬・神合町"	157
"stops.txt"	"stop_name"	"神馬・神合町"	158
"stops.txt"	"stop_name"	"宇土高校第３グラウンド前"	159
"stops.txt"	"stop_name"	"宇土高校第３グラウンド前"	160
"stops.txt"	"stop_name"	"宇土市役所前［行長しゃん専用］"	165
"stops.txt"	"stop_name"	"宇土市役所前［行長しゃん専用］"	166
"routes.txt"	"route_long_name"	"網津・緑川線"	8

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.
"20260911"	"20200902"	"20210225"

trip_headsign_matches_intermediate_stop INFO 8

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`.	tripId (?) The id of the trip with the problematic headsign.	tripHeadsign (?) The headsign value that matches an intermediate stop name.	stopId1 (?) The id of the intermediate stop whose name matches the headsign.	stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign.	stopId2 (?) The id of the actual last stop of the trip.
5	"R6+0+S4+1"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
6	"R6+0+S4+2"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
7	"R6+0+S4+3"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
8	"R6+0+S4+4"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
9	"R5+0+S4+1"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
10	"R5+0+S4+2"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
11	"R5+0+S4+3"	"宇土シティモール南口"	"S43_1"	1	"S43_2"
12	"R5+0+S4+4"	"宇土シティモール南口"	"S43_1"	1	"S43_2"

unknown_column INFO 1

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"	8

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.
"routes_jp.txt"
"office_jp.txt"