Feed status · checked 2026-09-05
Joshin Kanko Bus (上信観光バス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Gunma, 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
275 of 275 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
350 of 350 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
- 275 of 275 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
- 350 of 350 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 117 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 3 kinds of issue across 17364 instances (0 error, 17355 warning, 9 informational).
Service data covers the next 117 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 (鶴辺団地線, 13 前橋高崎線（京目経由）, 都心循環線, 倉賀野線, 観音山線, 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 275 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.
- 倉賀野線 (teal)
- 観音山線 (teal)
- 都心循環線 (teal)
- 高崎アリーナシャトル (teal)
- 13 前橋高崎線（京目経由） (teal)
- 鶴辺団地線 (teal)
| Route | Type | Line color |
|---|---|---|
| 倉賀野線 | Bus | teal |
| 観音山線 | Bus | teal |
| 都心循環線 | Bus | teal |
| 高崎アリーナシャトル | Bus | teal |
| 13 前橋高崎線（京目経由） | Bus | teal |
| 鶴辺団地線 | Bus | teal |
List every stop
- 中央病院入口
- 中央病院入口
- 上石倉
- 上石倉
- 石倉
- 石倉
- 小相木
- 小相木
- 育英高校
- 育英高校
- 済生会前橋病院
- 上新田郵便局
- 上新田郵便局
- 下新田入口
- 下新田入口
- 学校前
- 学校前
- 前橋駅
- 大利根団地
- 大利根団地
- 卸売センター
- 卸売センター
- 第二団地
- 第二団地
- 上京目
- 上京目
- 京目
- 京目
- 群南団地
- 群南団地
- 西島
- 西島
- 山王入口
- 山王入口
- 下新保
- 下新保
- マックス入口
- マックス入口
- 表町
- 表町
- 上大類
- 上大類
- 吉見パーキング
- 吉見パーキング
- 江木
- 江木
- 工業学校前
- 工業学校前
- 芝塚
- 芝塚
- 高砂町
- 高砂町
- 総合文化センター前
- 総合文化センター前
- 本町三丁目
- 本町三丁目
- 田町
- 田町
- 連雀町
- 連雀町
- あら町銀行前
- あら町銀行前
- あら町
- 高崎駅
- 高崎駅
- 鶴見町
- 鶴見町
- 新田町読売ビル
- 新田町読売ビル
- 佐藤病院
- 佐藤病院
- 竜広寺
- 竜広寺
- 聖石橋
- 聖石橋
- 石原局
- 石原局
- 保育園入口
- 小祝神社
- 小祝神社
- 大坂山入口
- 大坂山入口
- 農大二高入口
- 農大二高入口
- 農大二高
- 鶴辺団地
- アパート前
- 小相木北
- 小相木北
- アニバーサリーコートラシーネ
- アニバーサリーコートラシーネ
- 本町
- 本町
- 新前橋駅
- 滝川橋
- 滝川橋
- 市役所・合庁前
- 市役所・合庁前
- 日銀前
- 県庁前
- 県庁前
- 高崎アリーナ
- 新後閑町
- 城南野球場
- 宗真寺前
- 吉田歯科医院前
- ヤクルト高崎中央ＳＣ前
- 鶴見町南
- 鶴見町南
- 下和田町三丁目
- 高崎総合医療センター
- もてなし広場前
- 総合保健センター・中央図書館
- ＮＴＴ前
- 東京電力・スズラン入口
- 鞘町
- 白銀町
- 通町
- 旭町
- 高島屋前
- 高崎駅西口
- 高崎駅西口
- 高崎駅西口
- 八島町
- 双葉町
- 双葉町
- Ｇメッセ群馬
- 佐野中学校前
- 佐野中学校前
- 上中居郵便局前
- 上中居郵便局前
- 上中居町東
- 上中居町東
- 美術館前
- 美術館前
- 栄町
- 栄町
- 下中居町西
- 下中居町西
- 下中居町東
- 下中居町東
- モントレー・オーパ前
- 下中居普門寺前
- 下中居普門寺前
- 下中居町南
- 下中居町南
- 矢中町西
- 矢中町西
- 矢中郵便局前
- 矢中郵便局前
- いわたバディーズクリニック
- 倉賀野町桜木
- 倉賀野町桜木
- 倉賀野駅東
- 倉賀野駅東
- 倉賀野仲町
- 倉賀野仲町
- 倉賀野駅前
- 倉賀野公民館前
- 高島屋北入口
- 阿久津町
- 阿久津町
- 阿久津町南
- 阿久津町南
- 木部町北
- 木部町北
- 木部町
- 木部町
- 山名イーストタウン
- 山名イーストタウン
- 山名町南
- 山名町南
- ポリテクセンター群馬前
- ポリテクセンター群馬前
- 高崎産業技術専門校
- 山名郵便局前
- 山名郵便局前
- 南八幡中学校前
- 南八幡中学校前
- 慈光通り
- 商科大学入口
- 商科大学入口
- 商科大学前
- 商科大学前
- 下佐野町南
- 下佐野町南
- 下佐野町
- 下佐野町
- 下佐野町北
- 下佐野町北
- サンピエール病院前
- サンピエール病院前
- 倉賀野町西
- 倉賀野町西
- 倉賀野町西上正六
- 倉賀野町西上正六
- 佐野小学校入口
- 佐野小学校入口
- 上佐野町北
- 上佐野町北
- 大手前連雀町
- 和田多中町
- 和田多中町
- 新後閑郵便局前
- 新後閑郵便局前
- 下和田町
- 和田町
- 和田町
- 南町十字路
- 南町十字路
- 新田町
- 新田町
- 鶴見町
- 鶴見町
- 城南大橋西
- 城南大橋西
- 新雁行橋西
- 新雁行橋西
- 石原町東
- 石原町東
- スズラン前
- 農大二高入口
- 農大二高入口
- 農大二高
- 姥山入口
- 姥山入口
- 館東
- 館東
- 高風園前
- 高風園前
- 館西
- 館西
- 奥平入口
- 奥平入口
- 小塚
- 小塚
- 染料植物園駐車場前
- 染料植物園駐車場前
- 音楽センター前
- 染料植物園入口
- 染料植物園入口
- 国立のぞみの園
- 白衣観音前
- 白衣観音前
- 丸山団地南
- 丸山団地南
- 護国神社前
- 護国神社前
- 観音山中腹
- 観音山中腹
- and 25 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
5 findings, ordered by severity.
Show every finding
- Warning17055 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)
- Warning350 instances
350 of 350 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)
- Warning300 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)
- Warning275 instances
275 of 275 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)
- Info9 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · 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 117 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 117 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 83 / 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 60 / 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/joshin-kanko-bus/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.