Feed status · checked 2026-07-19
Kiso Town Public Transport (木曽町公共交通)
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.
Checked for changes 6 hours ago; last changed 6 hours ago.
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
172 of 172 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
22 of 22 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 346 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 4 kinds of issue across 1983 instances (0 error, 1981 warning, 2 informational).
Service data covers the next 346 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
2 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.
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 | red (no shape in feed) |
This feed has 172 stops.
List every stop
- 釜飛
- 池の沢
- 柳又ビューポイント
- 柳又ビューポイント
- 柳又
- 下条センター
- 管沢
- 管沢
- 木曽福島駅
- 木曽福島駅
- 御岳ロープウェイ
- 鹿の瀬温泉
- 木曽温泉
- 関町
- 関町
- 川合
- 川合
- 三岳入口
- 堀田
- 堀田
- 三尾
- 日向
- 道の駅三岳
- 黒田
- 橋渡
- 橋渡上
- 桑原
- 上條
- 小島渕
- 小島渕
- 白川入口
- けやきの湯
- 井原入口
- 三岳倉本
- 新八沢
- 新八沢
- 松本信用金庫木曽福島支店
- 松本信用金庫木曽福島支店
- 木曽福島郵便局
- 矢崎橋
- 上田口
- 六合目中の湯
- 千本松
- 八海山
- 神王原
- 正小屋
- 百間滝入口
- 松尾滝
- 田中支店
- 日の出滝
- 赤岩巣
- かんまん滝口
- 万寿屋
- 開山堂
- 屋敷野
- 一の沢
- 屋敷野口
- 床並
- 糀ヶ下
- 上八沢
- 中八沢橋
- 横手
- 木曽こどもセンター
- 相撲場
- 上田
- 荒神
- 上野
- 木曽町役場本庁
- 木曽青峰高校
- 城山
- 栗本
- 団地前
- 青木町
- 新町
- 万郡下
- 丘の上
- 福島旭町
- 元橋
- 元橋
- 沼田野
- 三師会館
- 木曽病院
- Aコープ
- Aコープ
- 塩渕
- 塩渕
- 八沢
- 本町
- 本町
- 本洞入口
- 三岳分岐点
- 三岳分岐点
- 三岳交流促進センター
- 黒沢
- 黒沢
- 田中
- 黒沢里宮
- 黒沢里宮
- 登山口
- 小坂
- 羽入
- 上町
- 上町
- 木曽町温水プール
- 木曽町温水プール
- 木曽町中学校
- 門前
- 興禅寺
- 横橋
- 黒川ダム
- 信州木曽看護専門学校
- 信州木曽看護専門学校
- 木曽福島体育館
- 漆ヶ平
- 漆ヶ平
- 下志水
- 下志水
- 中志水
- 中志水
- 上志水
- 上志水
- 栃本
- 栃本
- 東山
- 東山
- 新開島
- 新開島
- 渡合
- 渡合
- 中谷
- 中谷
- 溝口
- 溝口
- おもちゃ美術館
- おもちゃ美術館
- 新開吉田
- 新開吉田
- 平栃
- 平栃
- 橋詰
- 橋詰
- 宮前
- 宮前
- 野中橋
- 野中橋
- 新開野中
- 新開野中
- 清博士
- 清博士
- 村木
- 村木
- 村木原
- 村木原
- 芝原
- 芝原
- 岡の平
- 岡の平
- 木曽福島スキー場
- 木曽福島スキー場
- 木曽馬の里入口
- 木曽馬の里入口
- 馬橋
- 馬橋
- 中沢
- 彩菜館
- 彩菜館
- 大畑野
- 藤屋洞
- 馬追
- 馬追
- 夕山荘入口
- 開田支所
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 77.0 | first check |
| 2026-07-19 | 77.0 | 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
7 findings, ordered by severity.
Show every finding
- Warning1973 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)
- Warning172 instances
172 of 172 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)
- Warning22 instances
22 of 22 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)
- Warning7 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)
- 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)
- 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 346 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 346 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 82 / 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/kiso-town-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.