iiyama-city — Enhanced Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Language:
Japanese
Feed Start Date:
2026-09-01
Feed End Date:
2027-02-28

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. stop_times.txt
  9. stops.txt
  10. translations.txt
  11. trips.txt

Counts


  • Agencies: 6
  • Blocks: 0
  • Routes: 28
  • Shapes: 0
  • Stops: 309
  • Trips: 272

Specification Compliance report

36 notices reported (0 errors, 29 warnings, 7 infos)

Notice Code Severity Total
duplicate_route_name WARNING 13

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 "3983-R200500030020000" 4 "3983-R200500030010000" "11合庁線:田麦経由" "" 3 "3983-5100001002583"
6 "3983-R200500022000000" 7 "3983-R200500022010000" "12温井線" "" 3 "3983-5100001002583"
6 "3983-R200500022000000" 8 "3983-R200500022020000" "12温井線" "" 3 "3983-5100001002583"
6 "3983-R200500022000000" 9 "3983-R200500022030000" "12温井線" "" 3 "3983-5100001002583"
6 "3983-R200500022000000" 10 "3983-R200500022040000" "12温井線" "" 3 "3983-5100001002583"
6 "3983-R200500022000000" 11 "3983-R200500022050000" "12温井線" "" 3 "3983-5100001002583"
12 "3983-R200500036010000" 13 "3983-R200500036000000" "13小境線" "" 3 "3983-5100001002583"
14 "3983-R200500044020000" 15 "3983-R200500044000000" "9野沢線" "" 3 "3983-5100001002583"
14 "3983-R200500044020000" 16 "3983-R200500044080000" "9野沢線" "" 3 "3983-5100001002583"
18 "3983-R203600003010000" 19 "3983-R203600003000000" "斑尾線" "" 3 "3983-4000020202134"
20 "3983-R203700001000000" 21 "3983-R203700001020000" "木島平村シャトル便" "" 3 "3983-7000020205621"
23 "3983-R151000001030000" 24 "3983-R151000001000000" "関・燕温泉線" "" 3 "3983-6000020152170"
27 "3983-R151000007010000" 28 "3983-R151000007030000" "妙高山麓線" "" 3 "3983-6000020152170"
mixed_case_recommended_field WARNING 16

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_short_name" "10中野木島線" 2
"routes.txt" "route_short_name" "11合庁線:田麦経由" 3
"routes.txt" "route_short_name" "11合庁線:田麦経由" 4
"routes.txt" "route_short_name" "11合庁線:北間長瀬経由" 5
"routes.txt" "route_short_name" "12温井線" 6
"routes.txt" "route_short_name" "12温井線" 7
"routes.txt" "route_short_name" "12温井線" 8
"routes.txt" "route_short_name" "12温井線" 9
"routes.txt" "route_short_name" "12温井線" 10
"routes.txt" "route_short_name" "12温井線" 11
"routes.txt" "route_short_name" "13小境線" 12
"routes.txt" "route_short_name" "13小境線" 13
"routes.txt" "route_short_name" "9野沢線" 14
"routes.txt" "route_short_name" "9野沢線" 15
"routes.txt" "route_short_name" "9野沢線" 16
"routes.txt" "route_long_name" "湯田中駅~竜王ロープウェイ" 29
big_gap_in_service INFO 1

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"3983-S000012" "2026-12-25" "2027-01-12" 17
platform_without_parent_station INFO 6

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 "3983-S200500020100100" "飯山駅"
4 "3983-S200500020100200" "飯山駅"
5 "3983-S200500020100300" "飯山駅"
6 "3983-S203700001200100" "飯山駅"
7 "3983-S203800003200100" "飯山駅"
11 "3983-S200500023600100" "信州中野駅"