Feed status · checked 2026-07-19
Kagamino Town Bus (鏡野町営バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Okayama, 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.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
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
248 of 248 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
26 of 26 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
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 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
The MobilityData validator flagged 6 kinds of issue across 1074 instances (0 error, 1069 warning, 5 informational).
Service data covers the next 255 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
3 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- かがみの町営バス 中谷線 (purple)
- かがみの町営バス 郷線 (green)
- かがみの町営バス 越畑線 (orange)
- かがみの町営バス 公保田線 (yellow)
- 津山・富線共同バス (red)
| Route | Type | Line color |
|---|---|---|
| かがみの町営バス 中谷線 | Bus | purple |
| かがみの町営バス 郷線 | Bus | green |
| かがみの町営バス 越畑線 | Bus | orange |
| かがみの町営バス 公保田線 | Bus | yellow |
| 津山・富線共同バス | Bus | red |
This feed has 248 stops.
List every stop
- プラント5
- 芳野公民館前
- 芳野公民館前
- 芳野病院前
- 芳野病院前
- 吉原
- 吉原
- 旧鏡野農協前
- 旧鏡野農協前
- 岡坊
- 岡坊
- ハッピーマート前
- ハッピーマート前
- 寺元
- 寺元
- 鏡野病院
- 竹田
- 竹田
- 夢広場
- 夢広場
- 鏡野中学校前
- 鏡野中学校前
- 瀬戸
- 瀬戸
- 小座
- 小座
- 下入
- 下入
- 中入
- 中入
- 中谷
- 中谷
- 湯指
- 湯指
- 古実里
- 古実里
- 影
- 影
- 高座口
- 高座口
- 高座
- 大成
- 寺山
- 楠谷
- 大倉
- 近衛殿
- 近衛殿
- 忠野
- 忠野
- 古屋橋
- 古屋橋
- 余野上
- 黒地
- 黒地
- 長原
- 長原
- 浜橋
- 浜橋
- 高橋
- 高橋
- 谷口
- 谷口
- 梅谷
- 梅谷
- 大原
- 大原
- 渡
- 渡
- 山口
- 山口
- 東谷
- 東谷
- 富振興センター前（共同バス）
- 中村
- 山城
- 山城
- 男女山橋
- 男女山橋
- 下土居
- 下土居
- 上土居
- 上土居
- 円宗寺東
- 円宗寺東
- 沢田
- 沢田
- 公保田
- 公保田
- 市場
- 市場
- 和田
- 和田
- 土居東
- 土居東
- 貞永寺
- 貞永寺
- 上小座
- 上小座
- 健康づくり公園前
- 健康づくり公園前
- 大郷
- 大郷
- 馬場
- 馬場
- 西馬場
- 西馬場
- 塚谷
- 赤野
- 越畑上
- 越畑中
- 越畑中
- 越畑
- 越畑
- ふるさと村前
- ふるさと村前
- 徳藤
- 徳藤
- 岩屋
- 岩屋
- へこくら橋
- へこくら橋
- 宗重
- 宗重
- 鳥川
- 鳥川
- 中林口
- 中林口
- 大町
- 大町
- 薬師堂前
- 薬師堂前
- 香北農協前
- 香北農協前
- 香北局前
- 香北局前
- 岩滝上
- 岩滝上
- 岩滝
- 岩滝
- 馬橋
- 馬橋
- 日下
- 日下
- 円通寺
- 円通寺
- 藤屋
- 藤屋
- 藤屋下
- 藤屋下
- 香々美上
- 香々美上
- 香々美
- 香々美
- 楮原
- 楮原
- 和田橋
- 和田橋
- 大野橋
- 大野橋
- 円宗寺
- 円宗寺
- 釜の口
- 釜の口
- 原
- 原
- 千代口
- 千代口
- 森原
- 森原
- 下河原
- 下河原
- 東神戸
- 東神戸
- 作楽神社前
- 作楽神社前
- 作楽神社口
- 市営住宅口
- 市営住宅口
- ウエストランド前
- ウエストランド前
- 二宮山西
- 二宮山西
- 美和山古墳前
- 美和山古墳前
- 西中入口
- 西中入口
- 松中公民館前
- 松中公民館前
- 御旅所
- 御旅所
- 小田中局前
- 小田中局前
- 小田中
- 小田中
- 営林署前
- 営林署前
- 裁判所前
- 裁判所前
- 北町
- 北町
- 城北橋
- 城北橋
- 東小学校前
- 東小学校前
- 衆楽園・市役所前
- 衆楽園・市役所前
- 市役所西
- 市役所西
- 山北
- 山北
- 文化センター北口
- 文化センター北口
- 山下
- 山下
- 大手町
- 大手町
- 津山駅
- 南小学校前
- 南小学校前
- 上錦橋
- 上錦橋
- 野辺
- 野辺
- 平尾
- 平尾
- 竹峪
- 竹峪
- 下原上
- 下原上
- 郷農協前
- 郷農協前
- 郷幼稚園口
- 郷幼稚園口
- 河本南
- 河本南
- 河本
- 河本
- 高山
- 高山
- 松原
- 松原
- 崎原
- 崎原
- 寺村
- 寺村
- 寺村
- 瀬戸団地入口
- 瀬戸団地入口
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 73.3 | first check |
| 2026-07-19 | 73.3 | 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
- Warning1003 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 (opens the validator rules on an external site)
- Warning248 instances
248 of 248 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 (opens the GTFS Schedule reference on an external site)
- Warning56 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning26 instances
26 of 26 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 (opens the GTFS Schedule reference on an external site)
- Warning9 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 (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.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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.)
Validator rule: trip_headsign_matches_intermediate_stop · 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.)
Validator rule: 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).
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 (opens the validator rules on an external site)
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 73 / 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/kagamino-town-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.