Feed status · checked 2026-09-05
Nagaden Bus, Nagano depot area (長電バス長野営業所管内)
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
424 of 424 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
752 of 752 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
- 424 of 424 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
- 752 of 752 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 205 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 35135 instances (0 error, 35096 warning, 39 informational).
Service data covers the next 205 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.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (【51】 平林線, 【62】 東長野病院線, 【63】 三才線, 【R】 屋代須坂線, 【46】 大豆島川田線).
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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 424 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.
- 【64】 マユミダ三才線 (white)
- 【162】 三才東長野病院線 (brown)
- 【63】 三才線 (orange)
- 【46】 大豆島川田線 (teal)
- 【R】 屋代須坂線 (pink)
- 【51】 平林線 (green)
- 【81】 日赤線 (white)
- 【62】 東長野病院線 (red)
- 【161】 浅川西条市民病院線 (white)
- 【61】 浅川西条線 (white)
- 【82B】 綿内屋島線 (yellow)
- 【52】 運動公園線 (white)
- 【82】 須坂屋島線 (yellow)
| Route | Type | Line color |
|---|---|---|
| 【64】 マユミダ三才線 | Bus | white |
| 【162】 三才東長野病院線 | Bus | brown |
| 【63】 三才線 | Bus | orange |
| 【46】 大豆島川田線 | Bus | teal |
| 【R】 屋代須坂線 | Bus | pink |
| 【51】 平林線 | Bus | green |
| 【81】 日赤線 | Bus | white |
| 【62】 東長野病院線 | Bus | red |
| 【161】 浅川西条市民病院線 | Bus | white |
| 【61】 浅川西条線 | Bus | white |
| 【82B】 綿内屋島線 | Bus | yellow |
| 【52】 運動公園線 | Bus | white |
| 【82】 須坂屋島線 | Bus | yellow |
List every stop
- 湯谷小学校
- 湯谷小学校
- 三輪十丁目
- 三輪十丁目
- 檀田
- 檀田
- 檀田東
- 檀田東
- 稲田一丁目
- 稲田一丁目
- 稲田北
- 稲田北
- 新田川公園
- 新田川公園
- 徳間小学校
- 徳間小学校
- 緑ヶ丘住宅地
- 緑ヶ丘住宅地
- 高専
- 市立高校
- 市立高校
- 第二団地
- 第二団地
- 駒沢団地
- 三笠台住宅地
- 三才駅
- 三才駅
- 三才駅
- 三才駅
- 三才
- 三才東
- リハビリセンター
- リハビリセンター
- 東北中学
- 東北中学
- 栗田中
- 栗田中
- 文化会館入口
- 文化会館入口
- 北市
- 北市
- 信大工学部
- 信大工学部
- 若里
- 若里
- 日赤
- 若里多目的広場
- 若里多目的広場
- 水野美術館
- アークス前
- アークス東
- アークス中央
- ビッグハット
- 南千歳町
- 南千歳町
- 七瀬西
- 七瀬西
- ABN前
- ABN前
- 長野日大ゲートウェイ
- 長野日大ゲートウェイ
- 栗田
- 栗田
- 鶴賀七瀬
- 鶴賀七瀬
- 桜ヶ岡中学前
- 桜ヶ岡中学前
- 上高田
- 上高田
- 高田寺村
- 高田寺村
- 高田
- 高田
- 南高田
- 南高田
- 緑ヶ丘小学校口
- 緑ヶ丘小学校口
- 南長池
- 南長池
- 南長池下
- 南長池下
- 東和田
- 東和田
- 南長池東
- 南長池東
- エムウェーブ前
- エムウェーブ前
- 長野東高校
- 長野東高校
- 屋島
- 屋島
- 南屋島
- 南屋島
- 福島南
- 福島南
- 牛池入口
- 牛池入口
- 幸高
- 幸高
- 井上町東
- 井上町東
- 米持町東
- 米持町東
- 東郵便局
- 東郵便局
- 八幡町南
- 八幡町南
- 屋部下
- メセナホール
- 屋部
- 須坂高校前
- 信州医療センター
- 蔵のまち入口
- 蔵のまち入口
- 末広町
- 末広町
- 須坂駅
- 須坂長野東IC
- 須坂長野東IC
- 尾張部神社前
- 尾張部神社前
- 湯～ぱれあ
- 湯～ぱれあ
- 清水
- 森
- 森
- 綿内小学校
- 綿内駅
- 須坂市役所西
- 八幡
- 八幡
- 境沢
- 境沢
- 自動車学校
- 自動車学校
- 米持
- 米持
- 北尾張部
- 北尾張部
- 井上小学校
- 井上小学校
- 井上
- 井上
- 牛池交差点
- 牛池交差点
- 北野美術館
- 北野美術館
- 若穂病院
- 領家
- 領家
- 川田駅
- 町川田工業団地
- 町川田工業団地
- 大室駅
- 大室駅
- 大室団地
- 大室団地
- FICT
- FICT
- 寺尾森林組合
- 小島田
- 小島田
- 金井山
- 金井山
- 柴
- 柴
- 柴南
- 柴南
- 東寺尾北
- 東寺尾
- 松代温泉入口
- 荒神町
- 荒神町
- 松代中町
- 松代中町
- 千曲住宅地
- 千曲住宅地
- 松代駅
- 長野松代総合病院
- 長野松代総合病院
- 松代高校
- 紺屋町
- 紙屋町
- 紙屋町
- 馬喰町
- 象山口
- 象山口
- 道島
- 道島
- 清野
- 清野
- 岩野
- 岩野
- 小島
- 小島
- 岩野西
- 土口水門
- 土口水門
- 雨宮北町
- 雨宮北町
- 屋代工業団地
- 土口北
- 土口北
- 土口中
- 土口中
- 土口南
- 土口南
- 雨宮東
- 雨宮東
- 雨宮中
- 雨宮中
- 雨宮上
- 雨宮上
- 柳原中央
- 柳原中央
- JAあんず店前
- JAあんず店前
- 屋代高校前
- 屋代高校前
- 屋代高見町
- 屋代高見町
- 屋代南高校前
- 屋代南高校前
- 屋代駅
- 千歳町
- 千歳町
- 市役所前
- 市役所前
- 長野鶴賀
- 長野鶴賀
- 七瀬中町
- 七瀬中町
- 商工会議所前
- 商工会議所前
- 柳原駅
- 柳原駅
- 芹田体育館
- 芹田体育館
- 南俣西
- 南俣西
- 南俣西
- 南俣
- 南俣
- 日詰
- 日詰
- 東日詰
- 東日詰
- 風間西口
- 風間西口
- 風間
- and 174 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
6 findings, ordered by severity.
Show every finding
- Warning35082 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)
- Warning752 instances
752 of 752 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)
- Warning424 instances
424 of 424 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)
- Warning14 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info39 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)
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 205 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 205 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 85 / 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/nagaden-bus-nagano/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.