minamishinshu-minamishinshu-nanbu-1 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-04T01:36:09Z,
for the dataset file:///shared/minamishinshu-minamishinshu-nanbu-1_4461c510.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

下伊那南部地域公共交通対策協議会
- website: http://www.town.anan.nagano.jp/no_information/nanbu-bus/664/
- phone number: 0260-22-4054
- email: Not provided

Feed Info

Publisher Name:
下伊那南部地域公共交通対策協議会: Publisher URL:
https://kk.minami.nagano.jp/: Feed Email:
N/A: Feed Language:
Japanese: Feed Start Date:
2026-04-01: Feed End Date:
2027-03-31: Service Window:
2026-04-02 to 2027-02-28 (?) 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: 6
Routes: 3
Shapes: 24
Stops: 145
Trips: 32

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

Transfers Shapes Feed Information Translations Fares V1 Route Colors Headsigns Location Types

Specification Compliance report

1748 notices reported (121 errors, 1625 warnings, 2 infos)

Notice Code Severity Total

duplicate_key ERROR 121

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

Only the first 50 of 121 affected records are displayed below.

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.
"fare_rules.txt"	2111	4640	"fare_id,origin_id,destination_id"	"100,3045,3044"
"fare_rules.txt"	2112	4641	"fare_id,origin_id,destination_id"	"100,3045,3043"
"fare_rules.txt"	2113	4642	"fare_id,origin_id,destination_id"	"100,3045,3042"
"fare_rules.txt"	2114	4643	"fare_id,origin_id,destination_id"	"100,3045,3041"
"fare_rules.txt"	2115	4644	"fare_id,origin_id,destination_id"	"100,3045,3040"
"fare_rules.txt"	2116	4645	"fare_id,origin_id,destination_id"	"100,3045,3038"
"fare_rules.txt"	2117	4646	"fare_id,origin_id,destination_id"	"100,3045,3037"
"fare_rules.txt"	2118	4647	"fare_id,origin_id,destination_id"	"100,3045,3036"
"fare_rules.txt"	2119	4648	"fare_id,origin_id,destination_id"	"100,3045,3035"
"fare_rules.txt"	2120	4649	"fare_id,origin_id,destination_id"	"100,3045,3034"
"fare_rules.txt"	2121	4650	"fare_id,origin_id,destination_id"	"100,3045,3045"
"fare_rules.txt"	2150	4688	"fare_id,origin_id,destination_id"	"100,3044,3043"
"fare_rules.txt"	2151	4689	"fare_id,origin_id,destination_id"	"100,3044,3042"
"fare_rules.txt"	2152	4690	"fare_id,origin_id,destination_id"	"100,3044,3041"
"fare_rules.txt"	2153	4691	"fare_id,origin_id,destination_id"	"100,3044,3040"
"fare_rules.txt"	2154	4692	"fare_id,origin_id,destination_id"	"100,3044,3038"
"fare_rules.txt"	2155	4693	"fare_id,origin_id,destination_id"	"100,3044,3037"
"fare_rules.txt"	2156	4694	"fare_id,origin_id,destination_id"	"100,3044,3036"
"fare_rules.txt"	2157	4695	"fare_id,origin_id,destination_id"	"100,3044,3035"
"fare_rules.txt"	2158	4696	"fare_id,origin_id,destination_id"	"100,3044,3034"
"fare_rules.txt"	2159	4697	"fare_id,origin_id,destination_id"	"100,3044,3044"
"fare_rules.txt"	2160	4698	"fare_id,origin_id,destination_id"	"100,3044,3045"
"fare_rules.txt"	2189	4736	"fare_id,origin_id,destination_id"	"100,3043,3042"
"fare_rules.txt"	2190	4737	"fare_id,origin_id,destination_id"	"100,3043,3041"
"fare_rules.txt"	2191	4738	"fare_id,origin_id,destination_id"	"100,3043,3040"
"fare_rules.txt"	2192	4739	"fare_id,origin_id,destination_id"	"100,3043,3038"
"fare_rules.txt"	2193	4740	"fare_id,origin_id,destination_id"	"100,3043,3037"
"fare_rules.txt"	2194	4741	"fare_id,origin_id,destination_id"	"100,3043,3036"
"fare_rules.txt"	2195	4742	"fare_id,origin_id,destination_id"	"100,3043,3035"
"fare_rules.txt"	2196	4743	"fare_id,origin_id,destination_id"	"100,3043,3034"
"fare_rules.txt"	2197	4744	"fare_id,origin_id,destination_id"	"100,3043,3043"
"fare_rules.txt"	2198	4745	"fare_id,origin_id,destination_id"	"100,3043,3044"
"fare_rules.txt"	2199	4746	"fare_id,origin_id,destination_id"	"100,3043,3045"
"fare_rules.txt"	2228	4784	"fare_id,origin_id,destination_id"	"100,3042,3041"
"fare_rules.txt"	2229	4785	"fare_id,origin_id,destination_id"	"100,3042,3040"
"fare_rules.txt"	2230	4786	"fare_id,origin_id,destination_id"	"100,3042,3038"
"fare_rules.txt"	2231	4787	"fare_id,origin_id,destination_id"	"100,3042,3037"
"fare_rules.txt"	2232	4788	"fare_id,origin_id,destination_id"	"100,3042,3036"
"fare_rules.txt"	2233	4789	"fare_id,origin_id,destination_id"	"100,3042,3035"
"fare_rules.txt"	2234	4790	"fare_id,origin_id,destination_id"	"100,3042,3034"
"fare_rules.txt"	2235	4791	"fare_id,origin_id,destination_id"	"100,3042,3042"
"fare_rules.txt"	2236	4792	"fare_id,origin_id,destination_id"	"100,3042,3043"
"fare_rules.txt"	2237	4793	"fare_id,origin_id,destination_id"	"100,3042,3044"
"fare_rules.txt"	2238	4794	"fare_id,origin_id,destination_id"	"100,3042,3045"
"fare_rules.txt"	2267	4832	"fare_id,origin_id,destination_id"	"100,3041,3040"
"fare_rules.txt"	2268	4833	"fare_id,origin_id,destination_id"	"100,3041,3038"
"fare_rules.txt"	2269	4834	"fare_id,origin_id,destination_id"	"100,3041,3037"
"fare_rules.txt"	2270	4835	"fare_id,origin_id,destination_id"	"100,3041,3036"
"fare_rules.txt"	2271	4836	"fare_id,origin_id,destination_id"	"100,3041,3035"
"fare_rules.txt"	2272	4837	"fare_id,origin_id,destination_id"	"100,3041,3034"

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	"3"	4	"4"	""	"S0 南部公共バス阿南線"	3	"4000020204048"

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 6

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"
"fare_attributes.txt"	7	"agency_id"

mixed_case_recommended_field WARNING 3

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"	"S1 南部公共バス温田線"	2
"routes.txt"	"route_long_name"	"S0 南部公共バス阿南線"	3
"routes.txt"	"route_long_name"	"S0 南部公共バス阿南線"	4

non_ascii_or_non_printable_char WARNING 1614

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 1614 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"	"4～11月"
"calendar.txt"	4	"service_id"	"冬季期間(12～3月)"
"calendar_dates.txt"	2	"service_id"	"4～11月"
"calendar_dates.txt"	3	"service_id"	"4～11月"
"calendar_dates.txt"	4	"service_id"	"4～11月"
"calendar_dates.txt"	5	"service_id"	"4～11月"
"calendar_dates.txt"	6	"service_id"	"4～11月"
"calendar_dates.txt"	7	"service_id"	"4～11月"
"calendar_dates.txt"	8	"service_id"	"4～11月"
"calendar_dates.txt"	9	"service_id"	"4～11月"
"calendar_dates.txt"	10	"service_id"	"4～11月"
"calendar_dates.txt"	11	"service_id"	"4～11月"
"calendar_dates.txt"	12	"service_id"	"4～11月"
"calendar_dates.txt"	13	"service_id"	"4～11月"
"calendar_dates.txt"	14	"service_id"	"4～11月"
"calendar_dates.txt"	15	"service_id"	"4～11月"
"calendar_dates.txt"	16	"service_id"	"4～11月"
"calendar_dates.txt"	17	"service_id"	"4～11月"
"calendar_dates.txt"	18	"service_id"	"4～11月"
"calendar_dates.txt"	19	"service_id"	"4～11月"
"calendar_dates.txt"	20	"service_id"	"4～11月"
"calendar_dates.txt"	21	"service_id"	"4～11月"
"calendar_dates.txt"	22	"service_id"	"4～11月"
"calendar_dates.txt"	23	"service_id"	"4～11月"
"calendar_dates.txt"	24	"service_id"	"4～11月"
"calendar_dates.txt"	25	"service_id"	"4～11月"
"calendar_dates.txt"	26	"service_id"	"4～11月"
"calendar_dates.txt"	27	"service_id"	"4～11月"
"calendar_dates.txt"	28	"service_id"	"4～11月"
"calendar_dates.txt"	29	"service_id"	"4～11月"
"calendar_dates.txt"	30	"service_id"	"4～11月"
"calendar_dates.txt"	31	"service_id"	"4～11月"
"calendar_dates.txt"	32	"service_id"	"4～11月"
"calendar_dates.txt"	33	"service_id"	"4～11月"
"calendar_dates.txt"	34	"service_id"	"4～11月"
"calendar_dates.txt"	35	"service_id"	"4～11月"
"calendar_dates.txt"	36	"service_id"	"4～11月"
"calendar_dates.txt"	37	"service_id"	"4～11月"
"calendar_dates.txt"	38	"service_id"	"4～11月"
"calendar_dates.txt"	39	"service_id"	"4～11月"
"calendar_dates.txt"	40	"service_id"	"4～11月"
"calendar_dates.txt"	41	"service_id"	"4～11月"
"calendar_dates.txt"	42	"service_id"	"4～11月"
"calendar_dates.txt"	43	"service_id"	"4～11月"
"calendar_dates.txt"	44	"service_id"	"4～11月"
"calendar_dates.txt"	45	"service_id"	"4～11月"
"calendar_dates.txt"	46	"service_id"	"4～11月"
"calendar_dates.txt"	47	"service_id"	"4～11月"
"calendar_dates.txt"	48	"service_id"	"4～11月"

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