Feed status · checked 2026-09-05
Matsumoto Regional Link Bus (松本市 地域連携バス)
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
561 of 561 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
360 of 360 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
- 561 of 561 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
- 360 of 360 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 573 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 7 kinds of issue across 9488 instances (0 error, 9380 warning, 108 informational).
Service data covers the next 573 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
5 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
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 561 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.
- 合庁ライナー (pink)
| Route | Type | Line color |
|---|---|---|
| タウンスニーカー北コース | Bus | pink (no shape in feed) |
| タウンスニーカー東コース | Bus | green (no shape in feed) |
| タウンスニーカー南コース | Bus | blue (no shape in feed) |
| 南部循環線 | Bus | white (no shape in feed) |
| 合庁ライナー | Bus | pink |
| 松本・島内線 | Bus | pink (no shape in feed) |
| 南松本・山形線 | Bus | orange (no shape in feed) |
| 梓川・波田線 | Bus | teal (no shape in feed) |
| 村井・山形線 | Bus | green (no shape in feed) |
| 朝日・波田線 | Bus | green (no shape in feed) |
| 奈川・安曇線 | Bus | gray (no shape in feed) |
| 四賀循環線 | Bus | pink (no shape in feed) |
| 波田循環バス | Bus | white (no shape in feed) |
| ほしみ線 | Bus | pink (no shape in feed) |
| 入山辺線 | Bus | gray (no shape in feed) |
| 中山線 | Bus | green (no shape in feed) |
| 浅間・大村線 | Bus | teal (no shape in feed) |
List every stop
- 上立田公民館
- ＪＡあづみ梓川支所
- 梓川診療所
- 梓川支所
- 梓川小学校
- 杏
- 大妻口
- カインズホーム梓川店
- 松本駅アルプス口
- 倭北
- 倭公園前
- 丸田団地
- 押出
- 波田文化センター
- 波田文化センター
- 波田駅
- 渚町
- 渚町
- アイシティ２１
- 下竹田
- 竹田
- 記念碑前
- 記念碑前
- 山形村役場
- 山形小学校
- 上竹田
- 唐沢
- サラダマーケット
- 留林
- なぎさライフサイト
- 旧中波田出張所
- 中波田
- 中波田
- 波田郵便局
- 松本市立病院
- 会吉車庫
- 会吉
- 下会吉
- まぶね
- 中横川
- 横川
- 丸の内病院
- 中屋敷
- 原山口
- 原山橋
- 山崎
- 金井
- 中川
- 中川消防団詰所
- 召田
- 豊泉橋
- 矢久
- 蛇原橋
- 蛇原橋
- 長越
- 藤池
- 会田口
- 四賀の里クリニック
- 四賀支所
- 中学校前（会田）
- 会田郵便局前
- 柳屋前
- 浄雲寺下
- 板場
- 堀米新田
- 沢屋
- 油坂
- 反町農協前
- 大門
- 矢室
- 化石館
- 反町
- 板場口
- 取出
- 穴沢温泉口
- 合同庁舎
- 保福寺下町
- 保福寺口
- 花見（松本市殿野入）
- 殿野入
- 宮前
- 赤怒田組合前
- 赤怒田
- 小瀬
- 福寿草公園前
- 錦部
- 錦部
- 一之瀬脳神経外科病院
- 川浦
- 保平上
- 保平
- 奥神谷
- 神谷
- 下神谷
- 坂ノ曽
- 野麦峠スキー場
- 運動広場前
- 奈川高原入口
- 浮世絵博物館・歴史の里
- 曽倉
- 寄合渡
- 丸中前
- 大平
- 曽倉沢
- 追平
- 金原
- 金原下
- ながわ山彩館
- 学校前
- 堀米南
- 文化センター夢の森前
- 古宿
- 学校口
- 黒川渡
- ＪＡスタンド横
- 奈川温泉
- 小黒川橋
- 下道
- 黒川渡下
- 古宿下
- 信濃荒井
- 中地川
- 田ノ萱上
- 田ノ萱
- 入山口
- 奈川渡ダム
- 五嶺沢
- 鵬雲崎
- 水殿ダム
- 水殿ダム
- 梨の木平
- 田川公民館
- 宮の沢
- 稲核仲町
- 稲核
- 稲核口
- 稲核ダム
- 安曇小中学校前
- 安曇支所前
- 安曇支所前
- 島々徳本峠入口
- 島々徳本峠入口
- 野沢
- 発電所前
- 発電所前
- 松本駅お城口
- 松本駅お城口
- 松本駅お城口
- 大野田遊園地前
- 前渕
- 前渕
- 新島々
- 原橋西
- 原消防詰所
- 穴沢
- 原橋東
- 太子殿
- 横手
- 上浅間
- バスターミナル北
- バスターミナル北
- 山田口
- 湯坂
- 野球場北
- 野球場西
- 変電所東
- 大村北
- 大宮神社
- 大村消防詰所
- かりがねサッカー場西
- 南郷福祉ひろば東
- 南郷福祉ひろば
- 惣社北
- 惣社公民館
- デリシア惣社店
- 桜橋東
- まつもと医療センター
- 村井駅
- 医師会医療センター南分室
- 中町・蔵シック館
- 松本短大北
- 神戸
- 旧菅野簡易郵便局
- 菅野小学校南
- 菅野
- やまびこドーム
- やまびこドーム
- 笹賀出張所南
- はかり資料館
- 下小俣北
- 巾下
- 空港東区
- 空港東区
- 松本空港入口
- 松本空港入口
- 信州スカイパーク体育センター
- 信州スカイパーク体育センター
- 北耕地口
- 下今井
- 下今井
- 藤岡前
- 今井小学校
- 今井道の駅
- 龍興寺
- イオンタウン山形
- 中大池
- 山形診療所
- ローズガーデン
- チビッコ広場
- 埴原南公民館
- 二重堀の松
- 古屋敷
- 埴原東公民館
- 宮の下
- 伊織霊水(美術館北)
- 北中島
- 南中島公民館
- 尾池公民館
- 棚峯公民館
- 花村商店前
- 柿の窪
- 組合前
- 中山霊園口
- 考古博物館前
- 中山小学校東
- 薬祖神社
- 箱井丸山
- 中山学校前
- 和泉
- 中河原
- 上和泉構造改善センター
- 高田店前
- 地蔵前
- 二山
- 和泉橋
- 日ノ出町
- 神田南
- 神田
- 三才東
- ツルヤ並柳店
- 富士電機前
- 筑摩
- 松商学園口
- 飯田町
- ラーラ松本
- 平瀬川西公民館
- 四ツ谷町
- 八幡原
- 武宮前
- 島内出張所
- and 311 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
10 findings, ordered by severity.
Show every finding
- Warning9317 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)
- Warning561 instances
561 of 561 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)
- Warning360 instances
360 of 360 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)
- Warning33 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)
- Warning29 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.)
Finding code: 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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info103 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)
- 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.)
Finding code: 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.)
Finding code: 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
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 573 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 573 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 74 / 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/matsumoto-regional-bus/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.