Feed status · checked 2026-09-05
Nagaden Bus express services (長電バス急行)
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
225 of 225 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
75 of 75 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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +6 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
- 225 of 225 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
- 75 of 75 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 rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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.
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 90 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 6 kinds of issue across 25 instances (0 error, 21 warning, 4 informational).
Service data covers the next 90 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
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (奥志賀高原線).
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 225 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.
- 急行志賀高原線 (red)
- 急行タングラム・斑尾高原線 (white)
- 上林線 (yellow)
- 白根火山線 (green)
- 奥志賀高原線 (blue)
- 急行妙高高原線 (orange)
| Route | Type | Line color |
|---|---|---|
| 急行志賀高原線 | Bus | red |
| 急行タングラム・斑尾高原線 | Bus | white |
| 上林線 | Bus | yellow |
| 白根火山線 | Bus | green |
| 奥志賀高原線 | Bus | blue |
| 急行妙高高原線 | Bus | orange |
List every stop
- 運動公園
- 高速小布施
- 斑尾高原ホテル
- 斑尾高原ホテル
- 飯山駅1番のりば
- 飯山駅1番のりば
- 山の家前
- 山の家前
- プラザ前
- プラザ前
- タングラム斑尾
- タングラム斑尾
- 高速小布施
- 高速小布施
- アップルシティ中野
- アップルシティ中野
- アップルシティ中野
- 信州中野駅
- 信州中野駅
- 信州中野駅
- 三好町
- 三好町
- 官庁街
- 官庁街
- 官庁街
- 信金前
- 信金前
- 信金前
- 中町
- 中町
- 中町
- 松川大門
- 松川大門
- 松川駅
- 松川駅
- 松川駅
- 一本木公園
- 一本木公園
- 一本木公園
- 運動公園
- 運動公園
- 栗和田北
- 原町
- 原町
- 原町
- イオン中野店前
- イオン中野店前
- イオン中野店前
- 一本木
- 一本木
- 公園北
- 公園北
- 竹原
- 竹原
- 竹原
- 夜間瀬
- 夜間瀬
- 夜間瀬駅
- 夜間瀬駅
- 夜間瀬駅
- 塚田団地
- 塚田団地
- 上条
- 上条
- 上条
- 戸狩入口
- 戸狩入口
- 栗和田北
- 栗和田北
- 河原
- 星川温泉
- 星川温泉
- 星川中
- 星川中
- 星川中
- 大噴泉
- 大噴泉
- 大噴泉
- 安代温泉
- 安代温泉
- 安代温泉
- 渋温泉
- 渋温泉
- 渋温泉
- 渋和合橋
- 渋和合橋
- 渋和合橋
- 沓野
- 沓野
- 沓野
- 天川神社
- 天川神社
- 天川神社
- 沓野美明
- 沓野美明
- 沓野美明
- 砂止
- 砂止
- 砂止
- 河原
- 河原
- 湯田中駅
- 運動公園入口
- 運動公園入口
- 運動公園入口
- 澗満滝（臨停）
- 澗満滝（臨停）
- 澗満滝（臨停）
- 旭山下
- 旭山下
- サンバレー
- サンバレー
- サンバレー
- 丸池
- 丸池
- 丸池
- 蓮池ひろば
- 蓮池ひろば
- 蓮池ひろば
- 志賀高原山の駅
- 志賀高原山の駅
- 志賀高原山の駅
- 信大自然教育園
- 信大自然教育園
- 信大自然教育園
- 小池
- 小池
- 木戸池
- 木戸池
- 木戸池
- 湯田中駅
- スノーモンキーパーク
- 笠岳
- 笠岳
- 平床
- 平床
- 熊の湯
- 熊の湯
- ほたる温泉
- ほたる温泉
- ほたる温泉
- 硯川寮前
- 硯川寮前
- 横手山第１リフト
- 横手山第１リフト
- 横手山スキー場
- 横手山スキー場
- のぞき
- のぞき
- のぞき
- 渋峠
- 渋峠
- 渋峠
- 白根火山
- 白根火山
- スノーモンキーパーク
- 奥志賀高原ホテル
- 大沼池入口
- 大沼池入口
- 大沼池入口
- 発哺入口
- 発哺入口
- 発哺温泉
- 発哺温泉
- 高天ヶ原
- 高天ヶ原
- 高天ヶ原
- 高天ヶ原寮前
- 高天ヶ原寮前
- 一の瀬
- 一の瀬
- 一の瀬
- 一の瀬スキー場
- 一の瀬スキー場
- 一の瀬スキー場
- 一の瀬寮
- 一の瀬寮
- 一の瀬寮
- プリンスホテル西館
- プリンスホテル西館
- プリンスホテル西館
- プリンスホテル南館
- プリンスホテル南館
- プリンスホテル南館
- 奥志賀高原ホテル
- 池ノ平
- プリンスホテル東館
- プリンスホテル東館
- プリンスホテル東館
- 焼額山第一ゴンドラ
- 焼額山第一ゴンドラ
- 焼額山第一ゴンドラ
- 焼額山テレインパーク
- 焼額山テレインパーク
- 焼額山テレインパーク
- 奥志賀ゴンドラ前
- 奥志賀ゴンドラ前
- 奥志賀ゴンドラ前
- 奥志賀寮前
- 奥志賀寮前
- 道の駅やまのうち
- 道の駅やまのうち
- 道の駅やまのうち
- 草津温泉
- 草津温泉
- 池ノ平
- 田ノ原（臨停）
- 善光寺大門
- 善光寺大門
- 田ノ原（臨停）
- 田ノ原（臨停）
- 長野駅東口
- 長野駅東口
- 長野駅東口
- 長野駅東口
- 杉野沢
- 杉野沢
- いもり池
- いもり池
- 妙高高原池の平
- 妙高高原池の平
- 赤倉観光ホテル入口
- 赤倉観光ホテル入口
- 赤倉温泉スキー場
- 赤倉温泉スキー場
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
9 findings, ordered by severity.
Show every finding
- Warning225 instances
225 of 225 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)
- Warning75 instances
75 of 75 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)
- 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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · 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)
- Info3 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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 90 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 137 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 90 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 81 / 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-express/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.