GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

きそバス (木曽広域連合)

Based on the feed this agency publishes

Service mode Bus

75.8 / 100

First scorecard for this agency

Catalogued in Nagano, Japan.

Covers 97 daysAccessibility gapsRealtime not yet published

きそバス is the public schedule named by the repository. This registry item represents one feed record.

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

Fix 01

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

297 of 297 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

Fix 02

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

87 of 87 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

Fix 03

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.

  1. 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.

  2. 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.

  3. 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 97 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

Correctness78.8 / 100

The MobilityData validator flagged 6 kinds of issue across 4393 instances (0 error, 4381 warning, 12 informational).

Freshness100.0 / 100

Service data covers the next 97 days.

Rider experience52.3 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 7 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.

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("B&Gプール").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in きそバス (木曽広域連合)'s feed
RouteTypeLine color
北部幹線藪原系統Busteal (no shape in feed)
北部幹線木曽駒系統Busteal (no shape in feed)
開田幹線Busgreen (no shape in feed)
西部幹線王滝系統Busorange (no shape in feed)
西部幹線三岳系統Busorange (no shape in feed)
南部幹線坂下系統Buspink (no shape in feed)
南部幹線上松系統Buspink (no shape in feed)

This feed has 297 stops.

List every stop
  • 木曽馬の里入口
  • 木曽馬の里入口
  • 馬橋
  • 馬橋
  • 中沢
  • 中沢
  • 彩菜館
  • 彩菜館
  • 大畑野
  • 藤屋洞
  • 馬追
  • 馬追
  • 夕山荘入口
  • 開田支所
  • 釜飛
  • 荒町
  • 荒町
  • 池の沢
  • 柳又ビューポイント
  • 柳又ビューポイント
  • 柳又
  • 下条センター
  • 管沢
  • 管沢
  • 高宮商店
  • 旭ヶ丘
  • 牧野
  • 探勝園入口
  • 下の原
  • 矢崎橋
  • 矢崎橋
  • 覚明堂
  • 越
  • 嶽見旅館
  • 土橋
  • 西野住宅団地前
  • やまか旅館
  • 下向
  • 田沢医院
  • 古海道
  • 神田宮前
  • 出尻
  • 出尻
  • 木曽福島郵便局
  • 松本信用金庫木曽福島支店
  • 松本信用金庫木曽福島支店
  • 新八沢
  • 新八沢
  • 木曽町中学校入口
  • 沼田野
  • 元橋
  • 元橋
  • 川合
  • 川合
  • 三岳入口
  • 堀田
  • 堀田
  • 三尾
  • 上田口
  • 上田口
  • 日向
  • 道の駅三岳
  • 黒田
  • 橋渡
  • 橋渡上
  • 桑原
  • 上條
  • 小島渕
  • 小島渕
  • 三岳分岐点
  • 三岳分岐点
  • 三岳交流促進センター
  • 七笑
  • 七笑
  • 黒沢
  • 黒沢
  • 三岳大島
  • 長野県製薬
  • 長野県製薬
  • 二子持
  • 二子持
  • 崩越
  • 田島
  • 中越集会所
  • 中越集会所
  • 王滝
  • 王滝
  • 神戸
  • 神戸
  • 木曽市場
  • 道の駅日義木曽駒高原
  • 板敷野
  • 板敷野
  • かけはし大橋
  • かけはし大橋
  • あげまつ大橋
  • あげまつ大橋
  • 十王橋
  • 十王橋
  • いきいき広場
  • いきいき広場
  • 上松駅
  • 下町
  • 下町
  • 北栄町
  • 北栄町
  • 南栄町
  • 南栄町
  • 南栄町
  • 中山道北みかり
  • 元原（南）
  • 中山道南みかり
  • 中山道ねざめ
  • 中学校
  • 県営住宅
  • 滑川
  • 小野
  • 寝覚の床
  • 寝覚の床
  • 小野の滝
  • 小野の滝
  • 荻原
  • 串ヶ下
  • 串ヶ下
  • 元原（北）
  • B&Gプール
  • 立町
  • 立町
  • 倉本駅
  • 倉本駅
  • 桃山
  • 桃山
  • 池の尻
  • 池の尻
  • バス回転場所
  • 上郷養鱒場
  • 上郷
  • 上郷
  • 須原駅
  • グループホームさくら家
  • 原野中町
  • 茶屋町集会所
  • 定勝寺
  • ショッピングセンター
  • 橋場分館
  • 大島
  • 大桑駅
  • 大桑道の駅
  • くわっこ工房
  • 野尻本町
  • 野尻駅
  • 林昌寺
  • 木曽病院
  • 下在１踏切
  • 下在１上
  • 下在２お休所
  • 南木曽町役場
  • 南木曽駅
  • 篠﨑医院前
  • かぶと橋
  • 南木曽石材店前
  • 南木曽会館前
  • 渡島
  • 松沢
  • あすなろ荘入口
  • 灯籠前
  • 田立駅前
  • 大滝川橋
  • 旧担当区前
  • 坂下診療所
  • 弥栄橋
  • 弥栄橋
  • トランザム
  • 三沢
  • 長渡
  • 日義支所
  • 日義上村
  • 日義小学校
  • 尻平沢
  • 中町
  • 本陣
  • 宮ノ越駅入口
  • 宮ノ越駅入口
  • 三師会館
  • 宮ノ越旭町
  • 葵橋
  • 巴淵
  • 山吹橋
  • 吉田
  • 藪原駅
  • 奥原医院前
  • 木祖村役場
  • 木曽町温水プール
  • 木曽町温水プール
  • 門前
  • Aコープ
  • Aコープ
  • 興禅寺
  • 横橋
  • 黒川ダム
  • 横手
  • 上野
  • 団地前
  • 荒神
  • 上田
  • 栗本
  • 相撲場
  • 塩渕
  • 塩渕
  • 木曽駒入口
  • 駒見
  • 駒見
  • 木曽整骨院
  • 木曽整骨院
  • 文化公園入口
  • 文化公園入口
  • 陣立原
  • 木曽駒管理センター
  • 木曽駒管理センター
  • 木曽駒ゴルフ場
  • 神明
  • 神明
  • ユニテック木曽駒
  • 下村
  • 木曽福島駅
  • 木曽福島駅
  • 大原公民館
  • 大原
  • 大原上
  • 信州木曽看護専門学校
  • 信州木曽看護専門学校
  • 木曽福島体育館
  • 漆ヶ平
  • 漆ヶ平
  • 下志水
  • 下志水
  • 中志水
  • 中志水
  • 上志水
  • 上志水
  • 栃本
  • 栃本
  • 八沢
  • 東山
  • 東山
  • 新開島
  • 新開島
  • 渡合
  • 渡合
  • 中谷
  • and 47 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
  • Warning4375 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

  • Warning297 instances

    297 of 297 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

  • Warning87 instances

    87 of 87 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

  • Warning3 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

  • Warning2 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

  • 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

  • Info10 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.)

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • 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

  • 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

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 97 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 97 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 79 / 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.

きそバス (木曽広域連合) GTFS data quality grade: C

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/kisokoikirengo-kiso-bus/2026-07-23.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-23. 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.