Home
Japan Feeds
bus-daisencity-02
Source Data Validation Report

bus-daisencity-02 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-09T13:00:30Z,
for the dataset file:///shared/bus-daisencity-02_3d2b382d.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

大仙市
- website: https://www.city.daisen.lg.jp/docs/2013090600010/
- phone number: 0187-63-1111
- email: chikatu@city.daisen.lg.jp

Feed Info

Publisher Name:
大仙市: Publisher URL:
https://www.city.daisen.lg.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2025-04-21: Feed End Date:
2025-03-31: Service Window:
2025-04-21 to 2025-04-21 (?) 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: 7
Shapes: 0
Stops: 55
Trips: 34

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

Feed Information Translations Headsigns Location Types

Specification Compliance report

440 notices reported (22 errors, 416 warnings, 2 infos)

Notice Code Severity Total

duplicate_key ERROR 2

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.
"calendar.txt"	3	10	"service_id"	"火・木"
"calendar.txt"	6	12	"service_id"	"金曜"

invalid_float ERROR 1

invalid_float

A field cannot be parsed as a floating point number.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"fare_attributes.txt"	2	"price"	"200円"

start_and_end_range_out_of_order ERROR 18

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	entityId (?) The faulty service id.	startFieldName (?) The start value's field name.	startValue (?) The start value.	endFieldName (?) The end value's field name.	endValue (?) The end value.
"calendar.txt"	2	"月・木"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	3	"火・木"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	4	"水・金"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	5	"木曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	6	"金曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	7	"火曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	8	"水曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	9	"月・水"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	10	"火・木"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	11	"月曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	12	"金曜"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	13	"月・火・水・木"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	14	"平日"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	15	"火・水"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	16	"月・火・水"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	17	"月・金"	"start_date"	"20250421"	"end_date"	"20250331"
"calendar.txt"	18	"木・金"	"start_date"	"20250421"	"end_date"	"20250331"
"feed_info.txt"	2	N/A	"feed_start_date"	"20250421"	"feed_end_date"	"20250331"

stop_time_with_arrival_before_previous_departure_time ERROR 1

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	prevCsvRowNumber (?) The row of the previous stop time.	tripId (?) The trip_id associated to the faulty record.	arrivalTime (?) Arrival time at the faulty record.	departureTime (?) Departure time at the previous stop time.
274	273	"8月・水_12時20分_系統200032"	"12:03:00"	"12:20:00"

expired_calendar WARNING 7

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	"月・木"
9	"月・水"
11	"月曜"
13	"月・火・水・木"
14	"平日"
16	"月・火・水"
17	"月・金"

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	"20260409"	"20250331"	"20260416"

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

mixed_case_recommended_field WARNING 7

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
"routes.txt"	"route_long_name"	"南外地域市民バス　滝・中野線"	7
"routes.txt"	"route_long_name"	"南外地域市民バス　西ノ又線"	8

non_ascii_or_non_printable_char WARNING 399

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 399 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.
"calendar.txt"	2	"service_id"	"月・木"
"calendar.txt"	3	"service_id"	"火・木"
"calendar.txt"	4	"service_id"	"水・金"
"calendar.txt"	5	"service_id"	"木曜"
"calendar.txt"	6	"service_id"	"金曜"
"calendar.txt"	7	"service_id"	"火曜"
"calendar.txt"	8	"service_id"	"水曜"
"calendar.txt"	9	"service_id"	"月・水"
"calendar.txt"	10	"service_id"	"火・木"
"calendar.txt"	11	"service_id"	"月曜"
"calendar.txt"	12	"service_id"	"金曜"
"calendar.txt"	13	"service_id"	"月・火・水・木"
"calendar.txt"	14	"service_id"	"平日"
"calendar.txt"	15	"service_id"	"火・水"
"calendar.txt"	16	"service_id"	"月・火・水"
"calendar.txt"	17	"service_id"	"月・金"
"calendar.txt"	18	"service_id"	"木・金"
"fare_attributes.txt"	2	"fare_id"	"200円"
"fare_rules.txt"	2	"fare_id"	"200円"
"fare_rules.txt"	3	"fare_id"	"200円"
"fare_rules.txt"	4	"fare_id"	"200円"
"fare_rules.txt"	5	"fare_id"	"200円"
"fare_rules.txt"	6	"fare_id"	"200円"
"fare_rules.txt"	7	"fare_id"	"200円"
"fare_rules.txt"	8	"fare_id"	"200円"
"stop_times.txt"	2	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	3	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	4	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	5	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	6	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	7	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	8	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	9	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	10	"trip_id"	"10月曜_08時35分_系統200041"
"stop_times.txt"	11	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	12	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	13	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	14	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	15	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	16	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	17	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	18	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	19	"trip_id"	"10月曜_12時50分_系統200042"
"stop_times.txt"	20	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	21	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	22	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	23	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	24	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	25	"trip_id"	"11金曜_07時45分_系統200041"
"stop_times.txt"	26	"trip_id"	"11金曜_07時45分_系統200041"

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.
"20260409"	"20250421"	"20250421"

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