Feed status · checked 2026-09-05
Minamishinshu Shinnan Kotsu Routes (南信州広域連合 信南交通 駒場・阿島・遠山郷線)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Nagano, Japan.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
288 of 288 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
94 of 94 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 288 of 288 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 94 of 94 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 207 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 8 kinds of issue across 3843 instances (0 error, 3831 warning, 12 informational).
Service data covers the next 207 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (W0-1 駒場線, W0-2 駒場線, E0 阿島線, E0 阿島線, E0 阿島線, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 288 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- W0-1 駒場線 (red)
- W0-2 駒場線 (red)
- E0 阿島線 (red)
- E0 阿島線 (red)
- E0 阿島線 (red)
- E0 阿島線 (red)
- E1 遠山郷線 (teal)
- E1 遠山郷線 (teal)
| Route | Type | Line color |
|---|---|---|
| W0-1 駒場線 | Bus | red |
| W0-2 駒場線 | Bus | red |
| E0 阿島線 | Bus | red |
| E0 阿島線 | Bus | red |
| E0 阿島線 | Bus | red |
| E0 阿島線 | Bus | red |
| E1 遠山郷線 | Bus | teal |
| E1 遠山郷線 | Bus | teal |
List every stop
- 飯田病院前
- 飯田病院前
- 飯田駅前
- 飯田駅前
- 中央通り３丁目
- 中央通り３丁目
- 中央通り１丁目
- 知久町１丁目
- 市役所前
- 市役所前
- 上茶屋
- 上茶屋
- 上山
- 上山
- 一色アップルロード（イオン前）
- 一色アップルロード（平安堂前）
- 名古熊中央
- 名古熊中央
- 名古熊東（アピタ前）
- 名古熊東（信金前）
- 市立病院
- 常盤台東
- 常盤台東
- 常盤台
- 常盤台
- ＯＩＤＥ長姫高校前
- ＯＩＤＥ長姫高校前
- 下農入口
- 下農入口
- 鼎公民館前
- 鼎公民館前
- 下山東
- 下山東
- 飯田橋
- 飯田橋
- 伝馬町１丁目
- 伝馬町１丁目
- 知久町３丁目
- 中央広場
- 中央広場
- 東中央通り
- 東中央通り
- 城下
- 城下
- 鼎駅前
- 鼎駅前
- 飯田市役所
- 飯田高校前
- 飯田高校前
- 高松診療所前
- 高松診療所前
- 上郷辻
- 上郷辻
- 小伝馬橋
- 小伝馬橋
- 小伝馬町角
- 小伝馬町角
- 結いスクエア前
- 結いスクエア前
- 飯田病院角
- 飯田病院角
- 箕瀬入口
- 箕瀬入口
- 切石
- 切石
- 大井橋
- 大井橋
- 育良館跡
- 育良館跡
- 農協前
- 農協前
- 伊賀良
- 北方
- 北方
- 大瀬木
- 大瀬木
- 伊賀良局前
- 伊賀良局前
- 中村
- 中村
- 茂都計橋
- 茂都計橋
- 二ツ山
- 二ツ山
- 水晶館跡
- 水晶館跡
- 鈴木屋前
- 鈴木屋前
- 山本自治振興センター前
- 山本自治振興センター前
- 南平
- 南平
- 七久里
- 七久里
- 湯川
- 湯川
- 前原
- 前原
- 中関
- 中関
- 阿智高校前
- 中関団地入口
- こまんば
- こまんば
- 役場入口
- 役場入口
- 伍和入口
- 駒場西
- 駒場西
- 局前
- 曽山入口
- 曽山入口
- 阿智川大橋
- 阿智川大橋
- 昼神温泉東
- 昼神温泉東
- 朝市広場前
- 朝市広場前
- 恩出
- 恩出
- 昼神温泉郷
- 健和会病院
- 健和会病院
- 永代橋南
- 永代橋南
- 寺所入口
- 寺所入口
- 新井
- 新井
- 弁天
- 弁天
- ほっ湯アップル
- 弁天橋東
- 弁天橋東
- 伊久間団地入口
- 伊久間団地入口
- 丸山前
- 丸山前
- 伊久間消防詰所前
- 伊久間消防詰所前
- 伊久間
- 伊久間
- 交流センター
- 内山自動車板金前
- 内山自動車板金前
- せぎ下橋南
- せぎ下橋南
- 北消防センター前
- 北消防センター前
- 阿島北
- 阿島北
- 逢橋
- 逢橋
- 阿島
- 阿島
- 山上前
- 山上前
- 里原
- 里原
- 鍛冶垣外
- 鍛冶垣外
- 自動車学校入口
- 自動車学校入口
- 中河原
- 中河原
- 欠野
- 欠野
- 高岡
- 高岡
- エス・バード
- 元善光寺駅前
- 元善光寺駅前
- 元善光寺入口
- 元善光寺入口
- 七草団地入口
- 七草団地入口
- 正泉寺
- 正泉寺
- 北条
- 北条
- イオン飯田店
- 薬師前
- 薬師前
- 鶏足院前
- 鶏足院前
- 北原
- 北原
- 楽珍館前
- 楽珍館前
- 富田辻
- 富田辻
- 第二小学校入口
- 第二小学校入口
- 馬草田
- 馬草田
- 一本木
- 一本木
- 大和知
- 大和知
- 久保の下
- 久保の下
- 氏乗
- 氏乗
- 近藤商店前
- 近藤商店前
- 小沢橋
- 小沢橋
- 程野
- 程野
- 柄沢前
- 柄沢前
- 宮の前（南信濃）
- 宮の前（南信濃）
- 東前
- 東前
- うとどち
- うとどち
- 行者
- 行者
- 上中郷
- 上中郷
- 新島
- 新島
- コミュニティ前
- コミュニティ前
- 下中郷
- 下中郷
- 黒川前
- 黒川前
- 万場
- 万場
- 上町
- 上町
- 学校前
- 学校前
- 診療所前（上村）
- 診療所前（上村）
- 住宅前
- 住宅前
- 赤沢
- 赤沢
- 中村入口
- 中村入口
- 八日市場
- 八日市場
- 八名瀬
- 八名瀬
- 上島
- 上島
- 上沢
- and 38 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning3801 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning288 instances
288 of 288 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning94 instances
94 of 94 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning16 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 207 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 207 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 67 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/minamishinshu-shinnan-kotsu/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.