Feed status · checked 2026-07-19
Maniwa City Community Bus Maniwa-kun (真庭市コミュニティバス「まにわくん」)
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
337 of 337 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
33 of 33 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 3 kinds of issue across 2094 instances (0 error, 2092 warning, 2 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.
- 北房・久世ルート (pink)
- 新庄・久世ルート (teal)
- 蒜山・久世ルート (green)
| Route | Type | Line color |
|---|---|---|
| 北房・久世ルート | Bus | pink |
| 新庄・久世ルート | Bus | teal |
| 蒜山・久世ルート | Bus | green |
This feed has 337 stops.
List every stop
- 高岡上
- 高岡上
- 高岡
- 高岡
- 大笠
- 大笠
- 藤田
- 藤田
- 清常上
- 清常上
- 清常
- 清常
- 平田
- 平田
- 定
- 定
- 中津井
- 中津井
- 下中津井
- 下中津井
- 蟹川上
- 蟹川上
- 蟹川
- 蟹川
- 呰部
- 呰部
- 北房小学校前
- 北房小学校前
- 安末
- 安末
- 北房中学校前
- 北房中学校前
- 畑ヶ中
- 畑ヶ中
- 谷尻
- 谷尻
- 井尾口
- 井尾口
- 中田原
- 中田原
- 北房インター
- 北房インター
- 五名
- 五名
- 荒迫
- 荒迫
- 山田
- 山田
- 水田校口
- 水田校口
- 水田新町
- 水田新町
- 水田下町
- 水田下町
- 境入口
- 境入口
- 湯川
- 湯川
- 湯神
- 湯神
- 美川橋
- 美川橋
- 鹿の峰
- 鹿の峰
- 大柳
- 大柳
- サツキ橋
- サツキ橋
- 余河内
- 余河内
- やこうげ
- やこうげ
- 鹿田
- 鹿田
- 勇山寺
- 勇山寺
- 畝
- 畝
- 下方
- 下方
- 落合中学校前
- 落合中学校前
- 木山鳥居前
- 木山鳥居前
- 天神前
- 天神前
- 落合総合センター
- 落合総合センター
- 落合小学校前
- 落合小学校前
- 栄町
- 栄町
- プラムタウン真庭
- プラムタウン真庭
- プラムタウン真庭
- 真庭高校前
- 真庭高校前
- 米沢町十字路
- 米沢町十字路
- 落合上町
- 落合上町
- 金田病院前
- 金田病院前
- 美作落合駅
- 美作落合駅
- 落合インター
- 落合インター
- 上市瀬
- 上市瀬
- 開田
- 開田
- 福田橋
- 福田橋
- 中村
- 中村
- 紙屋
- 紙屋
- 富尾下
- 富尾下
- 富尾
- 富尾
- 真庭消防署前
- 真庭消防署前
- 落合病院
- 落合病院
- 梨瀬
- 梨瀬
- 高橋
- 高橋
- 新庄村役場前
- 新庄村役場前
- 道の駅新庄前
- 道の駅新庄前
- 長床
- 長床
- 大所
- 大所
- 羽仁
- 羽仁
- 野尾
- 野尾
- 平島上
- 平島上
- 平島
- 平島
- 平島下
- 平島下
- 河田口
- 河田口
- 当政
- 当政
- 美甘こども園前
- 美甘こども園前
- 美甘小学校前
- 美甘小学校前
- 美甘振興局前
- 美甘振興局前
- 只口
- 只口
- 首切
- 首切
- 出雲瀧
- 出雲瀧
- 太井の坂
- 太井の坂
- 湯谷
- 湯谷
- 田口
- 田口
- 延風
- 延風
- 八反
- 八反
- 四季桜
- 四季桜
- 塚本
- 塚本
- 神代
- 神代
- 上支富田
- 上支富田
- 支富田
- 支富田
- 重則
- 重則
- 荒田
- 荒田
- 荒田橋
- 荒田橋
- 上江川
- 上江川
- 江川
- 江川
- 勝山大橋
- 勝山大橋
- 羽仁下
- 羽仁下
- 荒田下
- 荒田下
- ゆめタウン前
- ゆめタウン前
- 蒜山高原（休暇村前）
- 蒜山高原（休暇村前）
- 湯船口
- 湯船口
- 蒜山高原センター前
- 蒜山高原センター前
- 上福田
- 上福田
- おおくに歯科医院前
- おおくに歯科医院前
- 堂の前
- 堂の前
- 富先
- 富先
- 中福田
- 中福田
- 中福田下
- 中福田下
- 富掛田
- 富掛田
- 富山根上
- 富山根上
- 富山根
- 富山根
- 蒜山中学校前
- 蒜山中学校前
- 蒜山振興局(蒜山図書館)
- 蒜山振興局(蒜山図書館)
- 渕ノ上
- 渕ノ上
- 吉森
- 吉森
- 飯守
- 飯守
- 道目木
- 道目木
- 花園
- 花園
- スポーツセンター前
- スポーツセンター前
- 馬橋
- 馬橋
- 上在所
- 上在所
- 山根
- 山根
- 原林口
- 原林口
- 栃ノ木
- and 87 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.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 81.2 | first check |
| 2026-07-19 | 81.2 | 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
5 findings, ordered by severity.
Show every finding
- Warning2079 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)
- Warning337 instances
337 of 337 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)
- Warning33 instances
33 of 33 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)
- 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 (opens the validator rules on an external site)
- Info2 instances
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 (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 86 / 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 60 / 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/maniwa-city-maniwakun/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.