Feed status · checked 2026-09-05
Matsumoto Station and Bus Terminal 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
462 of 462 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
588 of 588 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
- 462 of 462 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
- 588 of 588 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 8 kinds of issue across 17079 instances (0 error, 16949 warning, 130 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
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.
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.
This feed has 462 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.
| Route | Type | Line color |
|---|---|---|
| 信大横田循環線 | Bus | orange (no shape in feed) |
| 横田信大循環線 | Bus | orange (no shape in feed) |
| 浅間線 | Bus | red (no shape in feed) |
| 新浅間線 | Bus | black (no shape in feed) |
| 美ヶ原温泉線 | Bus | green (no shape in feed) |
| 北市内線 | Bus | teal (no shape in feed) |
| 岡田線 | Bus | white (no shape in feed) |
| アルプス公園線 | Bus | white (no shape in feed) |
| 鹿教湯温泉線 | Bus | gray (no shape in feed) |
| 空港今井線 | Bus | teal (no shape in feed) |
| 大久保工場団地・神林線 | Bus | green (no shape in feed) |
| 山形線 | Bus | white (no shape in feed) |
| 寿台線 | Bus | pink (no shape in feed) |
| 松原線 | Bus | white (no shape in feed) |
| 内田線 | Bus | white (no shape in feed) |
| 並柳団地線 | Bus | purple (no shape in feed) |
| 四賀線 | Bus | white (no shape in feed) |
List every stop
- 松本バスターミナル
- 松本バスターミナル
- 松本バスターミナル
- 松本バスターミナル
- 松本バスターミナル
- 本町
- 本町
- 大名町
- 大名町
- 蟻ヶ崎高校前
- 蟻ヶ崎高校前
- 正麟寺口
- 宮渕東
- 丸の内中学校前
- 開松
- 放光寺
- 種畜場口
- 種畜場口
- 城山老健施設前
- アルプス公園
- 蟻ヶ崎台
- 蟻ヶ崎五丁目
- 北蟻ヶ崎
- 北蟻ヶ崎
- 深志ヶ丘
- 深志ヶ丘
- 城山公園口
- 城山公園口
- 鷹匠町
- 国府町
- 国府町
- 松本駅お城口
- 松本駅お城口
- 松本駅お城口
- 松本駅お城口
- バスターミナル北
- バスターミナル北
- 秀峰学校前
- 秀峰学校前
- 秀峰学校前
- 秀峰学校前
- 秀峰学校前
- 秀峰学校前
- 松本市美術館
- 松本市美術館
- 市民芸術館
- 市民芸術館
- 筑摩小学校口
- 筑摩小学校口
- 西筑摩
- 西筑摩
- 本町五丁目
- 上土町
- 大手大通り
- 大手大通り
- 飯田町
- 清水
- 清水
- 清水
- 桜橋
- 桜橋
- 桜橋
- 桜橋
- 元町
- 元町
- 元町
- 横田
- 横田
- 横田
- 北元町
- 北元町
- 自動車学校前
- 自動車学校前
- 南浅間
- 南浅間
- 南浅間公民館前
- 南浅間公民館前
- 松本第一高校
- 松本第一高校
- 浅間温泉入口
- 浅間温泉入口
- 浅間温泉入口
- 水汲
- 水汲
- 追分
- 追分
- 追分
- 追分
- 追分
- 大学西門
- 大学西門
- 信州大学前
- 信州大学前
- 元原町
- 元原町
- 萩町
- 萩町
- 安原町
- 安原町
- 新町
- 新町
- 片端
- 白金町
- 白金町
- 中原町
- 中原町
- 松岡口
- 松岡口
- 松岡
- 松岡
- 岡田東区
- 岡田出張所前
- 岡田出張所前
- 仲町
- 仲町
- 岡田町
- 岡田町
- 山城口
- 山城口
- 中条
- 中条
- 鎌田
- 鎌田
- 鎌田
- 鎌田
- 征矢野口
- 征矢野口
- 高宮
- 高宮
- 高宮南
- 高宮南
- 石芝町
- 石芝町
- 野溝口
- 野溝口
- 二子橋
- 二子橋
- 下二子
- 下二子
- 神林高速バス停前
- 神林高速バス停前
- 町神東
- 町神東
- 神林
- 神林
- 上二子口
- 上二子口
- 菅野中学校前
- 菅野中学校前
- 松本短大口
- 松本短大口
- やまびこドーム前
- やまびこドーム前
- 小俣
- 小俣
- 空港東区
- 空港東区
- 信州まつもと空港
- 松本空港入口
- 松本空港入口
- 信州スカイパーク体育センター
- 信州スカイパーク体育センター
- 北耕地口
- 北耕地口
- 下今井
- 下今井
- 洞
- 洞
- 山城
- 山城
- 伊深
- 伊深
- 組合下
- 組合下
- 峠口
- 峠口
- 稲倉
- 稲倉
- 小日向
- 小日向
- 小日向橋
- 小日向橋
- 両島口
- 両島口
- 両島
- 両島
- 笹部
- 笹部
- 五月町
- 五月町
- 月見町
- 月見町
- 笹部団地
- 北栗東
- 北栗東
- 北栗南
- 北栗南
- 南栗口
- 南栗口
- 擬宝珠
- 擬宝珠
- 下和田
- 下和田
- 和田町郵便局
- 和田町郵便局
- 和田
- 和田
- 観音寺口
- 観音寺口
- 殿
- 殿
- 和田橋場
- 和田橋場
- 臨空工業団地
- 臨空工業団地
- アイシティ２１前
- アイシティ２１前
- 竹田原
- 竹田原
- 下竹田
- 下竹田
- 竹田
- 竹田
- 記念碑前
- 記念碑前
- 山形村役場
- 山形村役場
- 山形学校前
- 山形学校前
- 小坂口組合前
- 小坂口組合前
- 山形診療所前
- 山形診療所前
- 中大池
- 中大池
- 上大池
- 上大池
- 車庫前
- 車庫前
- 大橋通り南
- 大橋通り南
- 東町
- 塩屋小路入口
- 塩屋小路入口
- 上馬出し
- 上馬出し
- 和泉町
- 和泉町
- 西岡田
- 西岡田
- and 212 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
11 findings, ordered by severity.
Show every finding
- Warning16821 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)
- Warning588 instances
588 of 588 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)
- Warning462 instances
462 of 462 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)
- Warning73 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)
- Warning47 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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)
- 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)
- Info114 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)
- Info14 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 66 / 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-station-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.