Feed status · checked 2026-07-19
Nagano City Bus and Shared Taxi (長野市営バス・乗合タクシー)
Based on the feed this agency publishes
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.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
931 of 931 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
261 of 261 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 255 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 8712 instances (0 error, 8707 warning, 5 informational).
Service data covers the next 255 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
23 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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 東北ぐるりん号 | Bus | red (no shape in feed) |
| 乗合タクシー篠ノ井循環線 | Bus | teal (no shape in feed) |
| 乗合タクシー大室線 | Bus | teal (no shape in feed) |
| 乗合タクシー松代西条線 | Bus | teal (no shape in feed) |
| 乗合タクシー横田塩崎線 | Bus | teal (no shape in feed) |
| 乗合タクシー綿内線 | Bus | teal (no shape in feed) |
| 乗合タクシー長沼線 | Bus | teal (no shape in feed) |
| 乗合タクシー川中島線 | Bus | teal (no shape in feed) |
| 乗合タクシー篠ノ井共和線 | Bus | teal (no shape in feed) |
| 乗合タクシー安茂里線 | Bus | teal (no shape in feed) |
| 乗合タクシー西長野上松線 | Bus | teal (no shape in feed) |
| 乗合タクシー若里更北線 | Bus | teal (no shape in feed) |
| 中心市街地循環バス ぐるりん号 | Bus | red (no shape in feed) |
| 乗合タクシー川谷線 | Bus | teal (no shape in feed) |
| 乗合タクシー二ツ石線 | Bus | teal (no shape in feed) |
| 乗合タクシー芋井銚子口線 | Bus | teal (no shape in feed) |
| 乗合タクシー篠ノ井新町線 | Bus | teal (no shape in feed) |
| 乗合タクシー牟礼線 | Bus | teal (no shape in feed) |
| 乗合タクシー大豆島線 | Bus | teal (no shape in feed) |
| 乗合タクシー川田保科線 | Bus | teal (no shape in feed) |
| 廃止路線代替バス赤柴線 | Bus | yellow (no shape in feed) |
| 市バス鬼無里線 | Bus | gray (no shape in feed) |
| 市バス新町大原橋線 | Bus | gray (no shape in feed) |
| 市バス高府線 | Bus | gray (no shape in feed) |
This feed has 931 stops.
List every stop
- 篠ノ井
- 篠ノ井駅
- 篠ノ井駅
- 篠ノ井駅
- 篠ノ井横町
- 篠ノ井横町
- 篠ノ井支所
- 篠ノ井西公園
- 篠ノ井西公園
- 篠ノ井総合病院
- 篠ノ井総合病院
- 篠ノ井病院前
- 篠ノ井病院前
- 柴
- 柴
- 若草幼稚園
- 若穂支所
- 若穂支所
- ながの農協西長野支所
- ながの農協西長野支所
- 若穂団地
- 若穂団地
- 若穂団地
- 若穂病院
- 若穂病院
- 若葉町
- 若葉町
- 若葉町東
- 若葉町東
- 小柴見
- 小柴見
- 小柴見北
- 小柴見北
- 小出
- 小森西
- 小森東
- 小路公民館
- 小路公民館
- バスターミナル
- 庄ノ宮
- 庄ノ宮
- 庄ノ宮団地
- 昭和区公民館
- 昭和区公民館
- 昭和団地南
- 昭和団地南
- 松代駅
- 松代駅
- 松代支所
- 象山記念館
- 上駒沢会館
- 上駒沢西
- 上松五差路北
- 上松五差路北
- ハローワーク前
- 上松西
- 上松西
- 上町南
- 上庭
- 信濃吉田駅
- 信濃吉田駅
- 信濃吉田駅入口
- 信濃川田駅
- 信叟寺
- 新諏訪
- 新諏訪
- 新諏訪
- 新諏訪
- 新町団地
- 諏訪神社
- ひがの
- ひがの
- 瀬原田
- 瀬原田
- 瀬原田南
- 瀬原田南
- 星のさと
- 正覚院入口
- 正覚院入口
- 清水
- 清水
- 西横田西
- 西横田西
- 西横田中
- 西横田中
- 西原
- 西寺尾公園
- 西条公民館
- ポンプ小屋
- ポンプ小屋
- 西長野町
- 西長野町
- 西長野町東
- 西長野町東
- 西堀
- 西友古里店
- 西友川中島店
- 西友長野北店
- 青垣公園入口
- 石川老人憩の家
- 石渡南掘
- 赤沼ニュータウン
- 赤沼ニュータウン
- みくみ公民館
- みくみ公民館
- 赤沼下
- 赤沼下
- 赤沼上
- 赤沼上
- 赤沼郵便局
- 赤沼郵便局
- 赤野田
- 川中島駅
- 川中島支所前
- 川中島支所前
- 川中島中学校
- 川中島中学校
- 川田小学校
- 川田小学校
- 善光寺大門
- 善光寺大門
- 善光寺大門
- 善光寺大門
- 善導寺前
- 善導寺前
- みこと川第二集会所
- 大栄団地
- 大栄団地
- 大橋
- 大橋
- 大室駅
- 大室神社前
- 大室神社前
- 大室中
- 大室中
- 大室南
- 大室南
- 大沢組公民館
- 大門公民館[長野市安茂里]
- 大門公民館[長野市安茂里]
- 大門公民館[長野市篠ノ井岡田]
- 大門公民館[長野市篠ノ井岡田]
- 第二団地下
- 第二団地下
- みすず橋
- みすず橋
- みすず橋
- 第二団地上
- 第二団地上
- 辰巳公園
- 段ノ原
- 段ノ原
- 地震観測所入口
- 地震観測所入口
- 地蔵前
- 地蔵前
- 築地
- 築地
- 中屋敷大曲
- 中屋敷大曲
- 中条（篠ノ井）
- 中条（篠ノ井）
- 中組
- 中組公民館
- 中組公民館
- みろくじ集会所
- みろくじ集会所
- 中村神社
- 中沢
- 中町
- 中町
- 中津農協前
- 中島西
- 中島西
- 中島東
- 中島東
- 中氷鉋
- 中氷鉋
- 中氷鉋陣場
- 中氷鉋陣場
- 中氷鉋陣場
- 朝日病院前
- 朝陽駅
- やすらぎの園入口
- Aコープ篠ノ井店
- 長沼支所
- 長沼支所
- 長沼郵便局
- 長沼郵便局
- 長谷・越公民館
- 長谷・越公民館
- 長命寺
- 長野高専正門
- 長野松代総合病院
- 長野松代総合病院
- 津嶋神社
- 津嶋神社
- 津野公会堂
- 津野公会堂
- 追分
- 追分
- 通明小学校前
- 通明小学校前
- ユートピアわかほ
- ユートピアわかほ
- 塚本
- 塚本
- 典厩寺入口
- 島
- 島
- 東さいなみ
- 東横田
- 東横田
- 東横田公民館
- 東横田公民館
- 東横田北
- 東横田北
- 東犀南東公園
- 東篠ノ井公民館
- 東篠ノ井公民館
- 東富竹
- リハビリセンター
- 東部保健センター
- 東部保健センター
- 東福寺
- 東福寺合同庁舎
- 東北中学
- 東北中学
- 東北老人福祉センター
- 湯谷公会堂
- 湯谷公会堂
- 湯谷団地公会堂
- 湯谷団地公会堂
- 湯谷団地中央
- 湯谷団地中央
- 湯谷団地入口
- 湯谷団地入口
- 湯谷団地北
- 湯谷団地北
- りんごの郷入口
- りんごの郷入口
- 湯谷入口
- 湯谷入口
- 当組
- 当組
- 当組下
- 当組下
- 同心町北
- 徳間東
- 内町公会堂
- and 681 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
9 findings, ordered by severity.
Show every finding
- Warning8599 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)
- Warning931 instances
931 of 931 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)
- Warning261 instances
261 of 261 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)
- Warning95 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning12 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)
- 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.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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)
- 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.)
Validator rule: 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
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 255 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 255 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 73 / 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/nagano-city-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.