GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Matsusaka City Community Transport (松阪市コミュニティ交通)

Based on the feed this agency publishes

Service mode Bus

77.0 / 100

unchanged since 2026-07-18

Catalogued in Mie, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Matsusaka City's community transport network in central Mie.

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

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

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

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

Correctness81.5 / 100

The MobilityData validator flagged 4 kinds of issue across 3489 instances (0 error, 3487 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience52.2 / 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.

1 accessibility depth signal

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (M2鈴の音バス 市街地循環線, M4鈴の音バス 三雲松阪線).

    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.

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 Matsusaka City Community Transport (松阪市コミュニティ交通)'s feed
RouteTypeLine color
M1鈴の音バス 市街地循環線Busblue (no shape in feed)
M2鈴の音バス 市街地循環線Busred (no shape in feed)
M5鈴の音バス 大口線Busteal (no shape in feed)
M4鈴の音バス 三雲松阪線Busgreen (no shape in feed)
M3鈴の音バス 幸中央線Buswhite (no shape in feed)
N1嬉野おおきんバス AルートBusgreen (no shape in feed)
N1嬉野おおきんバス BルートBusgreen (no shape in feed)
N2たけちゃんハートバス 三雲線Busgreen (no shape in feed)
M12機殿・朝見地区コミュニティバスBusgreen (no shape in feed)
M11黒部・東地区コミュニティバスBusgreen (no shape in feed)

This feed has 228 stops.

List every stop
  • 一志団地
  • 多田クリニック
  • 五主
  • 五主中
  • 五主団地
  • 岡田
  • 星合
  • 鵲地区コミュニティセンター
  • 鵲地区コミュニティセンター
  • 笠松
  • 桜町第二集会所
  • 桜町第二集会所
  • 小舟江
  • 小舟江
  • オークワ三雲店
  • 西肥留
  • 肥留
  • 南小野江・辻本屋前
  • 小野江新町
  • 武四郎誕生地前
  • 松浦武四郎記念館
  • 松浦武四郎記念館
  • 甚目
  • 舞出
  • 桜町中央
  • 桜町中央
  • 嬉野新屋庄
  • 嬉野見永
  • 嬉野野田
  • 朝田南
  • 朝田南
  • 才田
  • 才田
  • 和屋団地
  • 和屋
  • 立田
  • 朝田
  • 大宮田
  • 桜町郵便局東
  • 桜町郵便局東
  • 古井
  • 西野々
  • 佐久米
  • 上七見
  • 下七見
  • 新屋敷
  • 魚見
  • 魚見
  • 保津
  • 六根
  • 腹太
  • さくら保育園前
  • さくら保育園前
  • 中河原
  • 井口中
  • 新開
  • 川島
  • 蓮花寺
  • 東久保
  • ＪＡくろべ
  • 東地区コミュニティセンター
  • こども広場
  • こども広場
  • 第二隣保館
  • ぎゅーとら大黒田店
  • 幸生
  • 辻の内
  • 辻の内
  • 高須西（後藤口）
  • 高須西（後藤口）
  • 高須町公民館
  • 高須旭一集会所
  • 網屋
  • 西黒部地区コミュニティセンター
  • 正眼院前
  • 松名瀬神社
  • 松名瀬町公民館
  • 花岡小学校口
  • 花岡小学校口
  • まとかた大西クリニック
  • 陽光寺横駐車場
  • 東黒部地区コミュニティセンター
  • 東黒部地区コミュニティセンター
  • 出間
  • 中田整形前
  • 中田整形前
  • 宝塚町
  • 宝塚町
  • アドバンスモール松阪
  • 宝塚古墳公園前
  • 宝塚古墳公園前
  • ＪＲ松阪駅
  • 山室入口
  • 山室入口
  • マックスバリュ学園前店
  • 駅部田山の世古
  • 駅部田山の世古
  • 駅部田五月橋
  • 駅部田五月橋
  • 旭ヶ丘
  • 田村町六才公園前
  • 田村町六才公園前
  • 西林
  • 西林
  • 幸地区コミュニティセンター前
  • 幸地区コミュニティセンター前
  • 久保中学校
  • 松阪工業グランド前
  • 松阪工業グランド前
  • 新町４丁目
  • 新町４丁目
  • 新町１丁目
  • 新町１丁目
  • 内五曲町
  • 内五曲町
  • 天白(回転場)
  • 田中自動車工業前
  • トライアル松阪店
  • 新田
  • ＪＡくろべ店
  • 五反田町一丁目
  • 五反田町一丁目
  • 松阪競輪場前
  • 松阪競輪場前
  • 東小野江
  • 第二小学校前
  • 築港
  • 愛宕町東
  • 愛宕町東
  • 平生町
  • 平生町
  • 日野町（ベルタウン）
  • 日野町（ベルタウン）
  • パティオひの街
  • パティオひの街
  • 済生会病院
  • 近鉄松阪駅
  • マックスバリュ中央店
  • 松阪警察署前
  • 松阪警察署前
  • 中央町
  • 中央町
  • マックスバリュ郷津店前
  • マックスバリュ郷津店前
  • 大口郵便局前
  • 大口郵便局前
  • 愛知機械前
  • セントラルグラスファイバー前
  • セントラルグラスファイバー前
  • よいほモール
  • よいほモール
  • セントラル硝子・松和自動車学校前
  • セントラル硝子・松和自動車学校前
  • 松阪港
  • 西町
  • 西町
  • 松阪中消防署前
  • 松阪中消防署前
  • イオンタウン松阪船江（松阪公民館）
  • 松ヶ崎
  • 松ヶ崎
  • アピタ松阪三雲店
  • 米ノ庄
  • 三渡橋口
  • 三渡橋口
  • 小津
  • 小津
  • よいほモール北
  • よいほモール北
  • 三雲地域振興局
  • 上小川
  • 花園口
  • 上出
  • 小原
  • 嬉野宇気郷地区コミュニティセンター
  • 殿出橋
  • 出合
  • 下出
  • 合ケ野
  • 市役所前
  • 市役所前
  • 谷
  • 大久保
  • 矢下橋
  • 矢下集会所
  • 矢下
  • 井置橋
  • 宮野
  • 宮野橋
  • 中郷地区コミュニティセンター前
  • 中郷郵便局
  • 市民病院
  • 森本集会所
  • 森本
  • 滝之川
  • 下古場
  • 釜生田
  • 井之上
  • エイトタウン
  • 八田
  • 八田川原
  • 堀之内
  • クラギ文化ホール
  • クラギ文化ホール
  • 豊地
  • 下之庄
  • 新出
  • 上野
  • 神ノ木台
  • 嬉野中学校
  • 松阪北消防署前
  • 嬉野社会福祉センター（嬉野地域振興局）
  • 嬉野医院
  • МＥＧＡドン・キホーテＵＮＹ嬉野店
  • パワーセンター松阪
  • Ａコープうれしの
  • ココカラファイン嬉野店中川駅北
  • 嬉野中川新町２丁目
  • 嬉野中川新町２丁目
  • 中川駅東口
  • 島田口
  • 島田
  • 中尾
  • 薬王寺
  • 薬王堂病院
  • 嬉野一志町
  • 城南住宅口
  • 城南住宅口

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 77.02026-07-19: 77.0
Show the numbers
CheckScoreChange
2026-07-1877.0 first check
2026-07-1977.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
  • Warning3456 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

  • Warning228 instances

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

  • Warning134 instances

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

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

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

Matsusaka City Community Transport (松阪市コミュニティ交通) 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/matsusaka-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.