Feed status · checked 2026-07-19
Ueda Bus (上田バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
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
334 of 334 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
260 of 260 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
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 295 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 15223 instances (0 error, 15221 warning, 2 informational).
Service data covers the next 295 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
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (信州上田医療センター線, 久保林線, 豊殿線, 塩田循環線, 傍陽線, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 久保林線 (teal)
- 信州上田医療センター線 (teal)
- 傍陽線 (teal)
- 塩田循環線 (teal)
- 塩田線 (teal)
- 真田線 (teal)
- 菅平高原線 (teal)
- 西丸子線 (teal)
- 豊殿線 (teal)
| Route | Type | Line color |
|---|---|---|
| 久保林線 | Bus | teal |
| 信州上田医療センター線 | Bus | teal |
| 傍陽線 | Bus | teal |
| 塩田循環線 | Bus | teal |
| 塩田線 | Bus | teal |
| 真田線 | Bus | teal |
| 菅平高原線 | Bus | teal |
| 西丸子線 | Bus | teal |
| 豊殿線 | Bus | teal |
This feed has 334 stops.
List every stop
- イオン上田ショッピングセンター
- イオン上田ショッピングセンター
- 横町
- 横町
- 笠原工業前
- 笠原工業前
- 上田駅前
- 上田駅前
- 松尾町
- 松尾町
- 原町
- 原町
- 房山
- 房山
- 新田
- 新田
- 下川原柳
- 下川原柳
- 上川原柳
- 上川原柳
- 染屋浄水場前
- 染屋浄水場前
- 住吉南
- 住吉南
- 上田検査場前
- 上田検査場前
- 住吉
- 住吉
- 神科農協前
- 神科農協前
- 神科小学校前
- 神科小学校前
- 樋之沢
- 樋之沢
- 伊勢山
- 伊勢山
- 殿城口
- 殿城口
- 下原
- 下原
- 下原
- 本原
- 本原
- 真田自治センター入口
- 真田自治センター入口
- 幸村の郷 夢工房前
- 幸村の郷 夢工房前
- 石舟
- 石舟
- 長小学校前（旧道経由）
- 長小学校前（旧道経由）
- 中真田
- 中真田
- 真田（旧道）
- 横沢
- 湯の平
- 下大日向
- 和熊口
- 大日向
- 大日向 宮前
- 上大日向
- 菅平口
- 菅平ダム
- 大洞
- 別荘入口
- 菅平高原 羽根尾
- 菅平高原 大松
- 菅平高原 つばくろ
- 菅平高原 西菅平
- 菅平高原 白金
- 菅平高原 表太郎前
- 菅平高原 アリーナ
- 菅平高原 東公園前
- 菅平高原 天狗
- 菅平高原 ダボス
- 菅平高原 裏太郎
- 真田（回転場）
- 下原上
- 下原上
- 上原
- 上原
- 本原小学校前
- 本原小学校前
- 中原
- 中原
- 藤沢
- 藤沢
- 真田中学校
- 真田中学校
- 横尾
- 横尾
- 小林医院前
- 小林医院前
- 曲尾
- 曲尾
- 旧農協スタンド前
- 旧農協スタンド前
- 傍陽
- 傍陽
- 八幡前
- 八幡前
- 畑中
- 畑中
- 中組
- 中組
- 水出
- 水出
- 岡保
- 岡保
- 松村
- 松村
- 軽井沢橋
- 軽井沢橋
- 入軽井沢公民館
- 入軽井沢公民館
- 入軽井沢
- 入軽井沢
- 傍陽小学校
- 傍陽小学校
- 金縄山入口
- 金縄山入口
- 田中
- 田中
- 横道
- 横道
- こまごめ橋
- こまごめ橋
- 穴沢
- 穴沢
- 三島平
- 三島平
- 大倉
- 大倉
- 川原柳
- 川原柳
- 蛇沢
- 蛇沢
- 上蛇沢
- 上蛇沢
- 金井（豊殿）
- 金井（豊殿）
- 大久保入口
- 大久保入口
- 神科
- 神科
- 五中前
- 五中前
- 新屋西
- 新屋西
- 新屋（豊殿）
- 新屋（豊殿）
- 下郷西
- 下郷西
- ショッピングパーク
- 漆戸
- 漆戸
- 下郷
- 下郷
- 宮前（豊殿）
- 宮前（豊殿）
- 岩清水入口
- 岩清水入口
- 殿城郵便局前
- 殿城郵便局前
- 矢沢
- 矢沢
- 赤坂口
- 赤坂口
- 赤坂北
- 赤坂
- 北上田
- 北上田
- 八幡北
- 八幡北
- 信州上田医療センター
- 高砂殿前
- 高砂殿前
- お城下
- お城下
- 玉姫殿前
- 玉姫殿前
- 千曲高校前
- 千曲高校前
- 中之条
- 中之条
- 三ツ角
- 三ツ角
- 赤坂上
- 赤坂上
- 創造館前
- 創造館前
- 月見ヶ丘
- 月見ヶ丘
- 上神畑
- 上神畑
- 神畑
- 神畑
- 下神畑
- 下神畑
- 下本郷
- 下本郷
- 下小島
- 下小島
- 上小島
- 上小島
- 保野東
- 保野東
- 川西医院入口
- 川西医院入口
- 川西医院
- 保野
- 保野
- 学海団地
- 学海団地
- JA塩田
- JA塩田
- 塩田町駅
- 塩田町駅
- 塩田病院
- 塩田病院
- 塩田自治センター
- 塩田自治センター
- 上本郷入口
- 上本郷入口
- 十人
- 十人
- 新町
- 新町
- 新町公民館
- 新町公民館
- 王子
- 王子
- 手塚
- 手塚
- さくら国際高校前
- さくら国際高校前
- 金井（塩田）
- 金井（塩田）
- 満願寺入口
- 満願寺入口
- 山田
- 山田
- 比蘭樹
- 比蘭樹
- 別所温泉駅
- 別所温泉駅
- 別所温泉
- 別所温泉
- ツルヤ塩田店
- 田中（塩田）
- and 84 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 80.2 | first check |
| 2026-07-19 | 80.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
5 findings, ordered by severity.
Show every finding
- Warning14997 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.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning334 instances
334 of 334 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning260 instances
260 of 260 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning224 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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.)
Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to 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 295 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 295 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 84 / 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/ueda-bus/2026-07-19.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-07-19. 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.