GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Konan City Megurukun Bus (湖南市コミバス めぐるくん)

Based on the feed this agency publishes

Service mode Bus

74.5 / 100

First scorecard for this agency

Catalogued in Shiga, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

The Megurukun community bus in Konan, Shiga, distinct from Konan City in Aichi.

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 8 hours ago; last changed 8 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

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

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

Correctness75.8 / 100

The MobilityData validator flagged 8 kinds of issue across 2672 instances (0 error, 2651 warning, 21 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

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

  • めぐるくん 石部循環線 (pink)
  • めぐるくん 妙感寺ルート (teal)
  • めぐるくん 美松台ルート (yellow)
  • めぐるくん 医療センタールート (green)
  • めぐるくん 石部線・東庁舎ルート (teal)
  • めぐるくん 三雲線・東庁舎ルート (pink)
  • めぐるくん イオンタウンルート (pink)
  • めぐるくん 菩提寺線・甲西駅ルート (pink)
  • めぐるくん 菩提寺線・石部駅ルート (green)
  • めぐるくん 下田線・三雲駅ルート (white)
  • めぐるくん 下田線・甲西駅ルート (orange)
  • めぐるくん ひばりヶ丘線 (teal)
  • めぐるくん 甲西南線・三雲小学校ルート (purple)
Routes in Konan City Megurukun Bus (湖南市コミバス めぐるくん)'s feed
RouteTypeLine color
めぐるくん 石部循環線Buspink
めぐるくん 妙感寺ルートBusteal
めぐるくん 美松台ルートBusyellow
めぐるくん 医療センタールートBusgreen
めぐるくん 石部線・東庁舎ルートBusteal
めぐるくん 三雲線・東庁舎ルートBuspink
めぐるくん イオンタウンルートBuspink
めぐるくん 菩提寺線・甲西駅ルートBuspink
めぐるくん 菩提寺線・石部駅ルートBusgreen
めぐるくん 下田線・三雲駅ルートBuswhite
めぐるくん 下田線・甲西駅ルートBusorange
めぐるくん ひばりヶ丘線Busteal
めぐるくん 甲西南線・三雲小学校ルートBuspurple

This feed has 224 stops.

List every stop
  • 菩提寺東三丁目
  • 菩提寺東三丁目
  • 菩提寺小学校
  • 菩提寺小学校
  • 菩提寺駐在所
  • 菩提寺駐在所
  • みどりの村団地
  • みどりの村
  • みどりの村
  • ハイウェイサイドタウン
  • イワタニランド
  • イワタニ北口
  • イワタニ東口
  • 近江台
  • イワタニ南口
  • 三雲が丘
  • 西山団地
  • 西山団地
  • 泉ヶ丘団地
  • 泉ヶ丘団地
  • 泉ヶ丘公園
  • 泉ヶ丘口
  • 泉ヶ丘口
  • 妙感寺
  • 勅使野橋
  • 三雲コミュニティセンター
  • 瑞美ヶ丘
  • 大谷団地
  • 大谷団地
  • 吉永
  • 夏見
  • 東柑子袋
  • 上葦穂神社
  • 南柑子袋
  • 東寺一丁目
  • 夏見診療所
  • 夏見診療所
  • 針西
  • 針西
  • 美松苑
  • 美松苑
  • 赤松台
  • 赤松台
  • ひばりヶ丘
  • 美松台
  • 美松台
  • 美松台北
  • 美松台北
  • 東山台
  • 東山台
  • 甲西駅南口
  • 石部駅北口
  • 若竹西口
  • 若竹西口
  • 一の瀬公園
  • 一の瀬公園
  • 若竹町
  • 若竹町
  • サンヒルズ甲西
  • サンヒルズ甲西
  • 水戸保育園
  • 水戸保育園
  • にごり池
  • にごり池
  • 岩根中央
  • 岩根中央
  • イオンタウン湖南
  • 善水寺
  • 善水寺
  • 岩根
  • 岩根
  • 岩根西口
  • 岩根西口
  • 花園東口
  • 花園東口
  • 岩根小学校
  • 岩根小学校
  • 大池町
  • 大池町
  • 仲町
  • 仲町
  • 西柑子袋
  • 西柑子袋
  • 石部南
  • 石部南
  • 保健センター
  • 保健センター
  • 丸山
  • 丸山
  • 西寺口
  • 西寺口
  • 西寺口
  • 西寺
  • 西寺
  • 西寺新田
  • 西寺新田
  • じゅらくの里
  • じゅらくの里
  • 長寿寺
  • 長寿寺
  • 東寺集会所
  • 東寺集会所
  • 東寺
  • 東寺
  • 近江学園
  • 近江学園
  • 石部南まちづくりセンター
  • 石部南まちづくりセンター
  • 夏見新田
  • 夏見新田
  • 阿星保育所
  • 阿星保育所
  • 石部南口
  • 石部南口
  • 石部南口
  • 宮の森
  • 宮の森
  • 医療センター
  • 医療センター
  • 古宮
  • 古宮
  • 石部交番前
  • 石部交番前
  • 郵便局
  • 郵便局
  • 文化総合センター
  • 文化総合センター
  • 西御旅
  • 西御旅
  • 甲西中学校
  • 甲西中学校
  • 農道柑子袋
  • 美松
  • 美松
  • 下田小学校
  • 下田小学校
  • 下田
  • 下田
  • 下田西
  • 堂の城西公園
  • 中山団地
  • 下田北
  • 下田北
  • 松風苑
  • 桐山
  • 甲西駅北口
  • 緑ヶ丘
  • 日の出ハウス
  • 下田まちづくりセンター
  • 蛭子町
  • 蛭子町
  • 三雲駅
  • 東陶前
  • 東陶前
  • 朝国
  • 朝国
  • 岩根東口
  • 岩根東口
  • 近江大口
  • 近江大口
  • 小砂町
  • 小砂町
  • 市役所東庁舎
  • 市役所東庁舎
  • 団地中央
  • 団地中央
  • 高松町
  • 高松町
  • 北中学校
  • 北中学校
  • 東正福寺
  • 東正福寺
  • 正福寺
  • 正福寺
  • 生田病院
  • 生田病院
  • 北山台南口
  • 北山台南口
  • 北山台南口
  • 石部口
  • 石部口
  • 新道下田
  • 新道下田
  • 下田口
  • 下田口
  • 甲西高校
  • 甲西高校
  • 中山口
  • 中山口
  • 竜王ダイハツ
  • 針
  • 三雲小学校
  • 市役所西庁舎
  • 市役所西庁舎
  • 登り町
  • 登り町
  • 岡出口
  • 岡出口
  • 宝来坂
  • 宝来坂
  • 南幼稚園
  • 南幼稚園
  • 甲西大橋北
  • 甲西大橋北
  • 石部中学校
  • 石部中学校
  • ケアセンター前
  • ケアセンター前
  • ケアセンター
  • 石部高校
  • 石部高校
  • 北山台一丁目
  • 北山台一丁目
  • 北山台二丁目
  • 北山台二丁目
  • 北山台センター
  • 北山台センター
  • 菩提寺コミュニティセンター
  • 菩提寺コミュニティセンター
  • 北山台西口
  • 北山台西口
  • 北山台西口
  • 菩提寺東二丁目
  • 菩提寺東二丁目

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

  • Warning224 instances

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

  • Warning106 instances

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

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

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

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Validator rule: big_gap_in_service · 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

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Validator rule: unknown_file · 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 76 / 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.

Konan City Megurukun 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/shiga-konan-city-megurukun-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.