GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Mitoyo City Community Bus (三豊市コミュニティバス)

Based on the feed this agency publishes

Service mode Bus

74.9 / 100

unchanged since 2026-07-18

Catalogued in Kagawa, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Mitoyo City's community bus network; counted as 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

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

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

Correctness76.8 / 100

The MobilityData validator flagged 6 kinds of issue across 6159 instances (0 error, 6148 warning, 11 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

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

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

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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.

Skip to route and stop data

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

  • ０１ (green)
  • ０２ (red)
  • ０３ (red)
  • ０４ (green)
  • ０５ (gray)
  • ０６ (pink)
  • ０７ (teal)
  • ０８ (teal)
  • ０９ (blue)
  • １０ (yellow)
  • １１ (yellow)
  • １２ (gray)
Routes in Mitoyo City Community Bus (三豊市コミュニティバス)'s feed
RouteTypeLine color
０１ 高瀬線Busgreen
０２ 高瀬仁尾線Busred
０３ 山本線Busred
０４ 三野線Busgreen
０５ 財田高瀬線Busgray
０６ 高瀬観音寺線Buspink
０７ 豊中仁尾線Busteal
０８ 詫間線Busteal
０９ 荘内線Busblue
１０ 詫間三野線Busyellow
１１ 仁尾線Busyellow
１２ 財田観音寺線Busgray

This feed has 372 stops.

List every stop
  • いこいの郷公園
  • しのはら医院
  • そがわ医院
  • たかせ天然温泉
  • たしろ医院
  • ふれあいパークみの
  • まるお眼科
  • みずた内科
  • みとよ市民病院
  • みの荘長寿の湯
  • ゆめタウン
  • ゆめタウン
  • ゆめタウン
  • 西上
  • カフェルポ
  • ピカソ三野店
  • ピカソ浜田店
  • ピカソ浜田店
  • ピカソ詫間店
  • ピカソ詫間店
  • ピカソ詫間店
  • マルナカ山本店
  • マルナカ山本店
  • 三豊市役所
  • 三豊市役所
  • 三豊中学校前
  • 三豊総合病院
  • 三宅歯科医院
  • 三井之江前
  • 三ツ池
  • 三反地
  • 三野町生涯学習センター
  • 三野町保健センター
  • 三野保育所前
  • 上栂
  • 上之荘
  • 上高野児童館
  • 下土井
  • 下原
  • 下河内
  • 下司
  • 中央公民館前
  • 中央公民館前
  • 中谷
  • 中元
  • 中屋敷
  • 中浦
  • 中河内
  • 中辻
  • 中姫中央
  • 中郷
  • 丸井北
  • 久保の下
  • 二ノ宮中
  • 二ノ宮農構センター
  • 五条眼科
  • 五条眼科
  • 五歩田
  • 五ツ街道
  • 井手向
  • 井出
  • 仁老浜
  • 仁尾小学校前
  • 仁尾町文化会館
  • 仁尾こども園
  • 仁尾南
  • 市民センター仁尾
  • 仁尾庁舎駐車場
  • 仁尾マリーナ口
  • 仁尾郵便局
  • 伊砂子
  • 佐文
  • 八幡
  • 八幡神社
  • 六ツ松
  • 六ツ松
  • 前田
  • 前田
  • 前側
  • 加茂下
  • 加茂下
  • 加茂［高瀬高校口］
  • 加茂［高瀬高校口］
  • 北原
  • 北立石
  • 千代
  • 南立石
  • 南郷［三豊市詫間町］
  • 南郷［三豊市高瀬町］
  • 原下
  • 友信
  • 古江
  • 吉津小学校口
  • 吉田
  • 吉原公民館前
  • 名部戸
  • 向谷
  • 吹毛ノ山
  • 善通寺市役所前
  • 四ツ足
  • 四国こどもとおとなの医療Ｃ前
  • 土井［三豊市豊中町］
  • 土井［三豊市山本町］
  • 城下
  • 塩生
  • 大興寺口
  • 大吉
  • 大北
  • 大地
  • 大水上神社
  • 大浜
  • 地域交流館荘内
  • 大浜南
  • 大坪
  • 大西医院
  • 大門
  • 大見
  • 大見
  • 大見幼稚園前
  • 大原
  • 大新田
  • 大麻荒神
  • 大野原中央公民館
  • 大野原中学校口
  • 天道
  • 天王
  • 安藤内科医院
  • 宗吉
  • 室本
  • 室本北口
  • 宮脇
  • 宮谷
  • 宮坂
  • 宮坂
  • 宮奥
  • 家の浦
  • 寺地
  • 寺地
  • 寺家下
  • 小久保
  • 小浜
  • 小山
  • 小野歯科医院
  • 小野歯科医院
  • 小路
  • ヤマモト典礼会館
  • 山本庁舎
  • 山地
  • 山地外科医院
  • 山才
  • 岡崎
  • 岩崎病院
  • 岩崎病院
  • 峠
  • 川上総合センター
  • 川原尻
  • 市民会館前［善通寺市］
  • 市民会館前［善通寺市］
  • 市民センター三野
  • 市営野球場前
  • 帰来
  • 帰来集会場
  • 平林医院
  • 庵上
  • 恵美
  • 成行
  • 新名
  • 新名
  • 新町
  • 新浜東
  • 新浜西
  • 新的場
  • 新的場南
  • 新開橋
  • 早北
  • 明神
  • 曽保
  • 曽保中筋
  • 曽保浦の谷
  • 朝日
  • 木の本
  • 末
  • 本谷
  • 本村上
  • 本村中
  • 本村［三豊市詫間町］
  • 本村［三豊市高瀬町］
  • 本山小学校前
  • 本山小学校前
  • 本山駅
  • 本山寺
  • 本庄
  • 杉庄
  • 東久保谷
  • 東浜
  • 東善
  • 東香田
  • 松崎北浦
  • 松崎東
  • 松崎西
  • 松崎団地
  • 桑山１０区
  • 桑山１３区
  • 桑山１４区
  • 桑山１７区
  • 桑山１区
  • 桑山４区
  • 桑山５区
  • 森
  • 森安
  • 森川整形外科病院
  • 森川整形外科病院
  • 椛ノ木
  • 楠浜
  • 樫谷
  • 橋本病院
  • 正本
  • 正宗
  • 比地小学校前
  • 比地大小学校前
  • 比地大駅
  • 比地大郵便局
  • 水出
  • 永生病院
  • 永生病院
  • 江藤
  • 池田外科医院
  • 池の向
  • 池ノ谷
  • 河中
  • 河中
  • 河内公民館
  • 泉平
  • 波止
  • 津ノ前自治会館
  • 浜田
  • 浦側
  • 父母ヶ浜
  • 片山
  • 物産館
  • 琴中前
  • 琴浦
  • 琴平駅
  • 琴電琴平駅
  • 環の湯
  • 生里
  • 生里南
  • 田の口
  • 田井
  • 田淵会場
  • and 122 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-07-18: 74.92026-07-19: 74.9
Show the numbers
CheckScoreChange
2026-07-1874.9 first check
2026-07-1974.9 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

9 findings, ordered by severity.

Show every finding
  • Warning6124 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

  • Warning372 instances

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

  • Warning185 instances

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

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

  • Warning1 instance

    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

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

    Validator rule: platform_without_parent_station · 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 77 / 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.

Mitoyo City Community Bus (三豊市コミュニティバス) 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/mitoyo-city-community-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.