Home
Japan Feeds
noriai-taxi
Source Data Validation Report

noriai-taxi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-20T13:57:20Z,
for the dataset file:///shared/noriai-taxi_defbd6b8.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

八代市
- website: https://www.city.yatsushiro.lg.jp/kiji00310058/index.html
- phone number: 0965-33-4104
- email: kikaku@city.yatsushiro.lg.jp

Feed Info

Publisher Name:
八代市: Publisher URL:
https://www.city.yatsushiro.lg.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2023-10-02: Feed End Date:
2024-10-31: Service Window:
2023-10-02 to 2024-10-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
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
translations.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 5
Shapes: 10
Stops: 151
Trips: 76

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

Shapes Feed Information Translations Fares V1 Route Colors Headsigns Location Types

Specification Compliance report

9781 notices reported (0 errors, 9779 warnings, 2 infos)

Notice Code Severity Total

expired_calendar WARNING 14

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	"平日"
3	"平日（百済来）"
4	"木のみ（百済来）"
5	"毎日（親和）"
6	"毎日（西田）"
7	"平日（文政１）"
8	"平日（文政２）"
9	"土日祝（文政１）"
10	"土日祝（文政２）"
11	"毎日（坂本線）神園"
12	"平日（坂本線）神園"
13	"土日祝（坂本線）神園"
14	"平日（坂本線）大和"
15	"平日大和、土日神園（坂本線）"

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	"20260420"	"20241031"	"20260427"

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 1

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"

mixed_case_recommended_field WARNING 11

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
"stops.txt"	"stop_name"	"３班ゴミ集積所"	9
"stops.txt"	"stop_name"	"御倉（文政）"	40
"stops.txt"	"stop_name"	"宮園（有佐）"	49
"stops.txt"	"stop_name"	"南平和町２区公民館"	147
"stops.txt"	"stop_name"	"北平和町２区公民館"	148
"stops.txt"	"stop_name"	"北平和町１区公民館"	149

non_ascii_or_non_printable_char WARNING 9747

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 9747 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_dates.txt"	2	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	3	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	4	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	5	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	6	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	7	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	8	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	9	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	10	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	11	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	12	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	13	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	14	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	15	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	16	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	17	"service_id"	"土日祝（坂本線）神園"
"calendar_dates.txt"	18	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	19	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	20	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	21	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	22	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	23	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	24	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	25	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	26	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	27	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	28	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	29	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	30	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	31	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	32	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	33	"service_id"	"土日祝（文政１）"
"calendar_dates.txt"	34	"service_id"	"土日祝（文政２）"
"calendar_dates.txt"	35	"service_id"	"土日祝（文政２）"
"calendar_dates.txt"	36	"service_id"	"土日祝（文政２）"
"calendar_dates.txt"	37	"service_id"	"土日祝（文政２）"

route_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"30"	3	"#BFBFBF"	"#FFFFFF"

stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`.	shapeId (?) The id of the shape that is referred to.	tripId (?) The id of the trip that is referred to.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
5	"河俣～種山線（往路）"	"1平日_11時20分_系統102001"	689	"21_01"	"八代市役所東陽支所前"	[32.54616,130.71617]	688	"22_02"	"種山"	[32.54757,130.71538]

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.
"20260420"	"20231002"	"20241031"

unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id.	csvRowNumber (?) The row number of the faulty record.
"百済来～坂本線（復路）"	3479

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