Feed status · checked 2026-07-23
四万十町コミュニティバス
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Kochi, 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
485 of 485 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
184 of 184 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 252 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 4732 instances (0 error, 4732 warning, 0 informational).
Service data covers the next 252 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
25 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (払川線, 道徳線, 奥呉地線, 折合線, 若井川線, and more).
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.
- 払川線 (orange)
- 道徳線 (orange)
- 奥呉地線 (orange)
- 折合線 (orange)
- 若井川線 (orange)
- 川ノ内線 (orange)
- 神ノ川線 (orange)
- 床鍋線 (orange)
- 東北ノ川線 (orange)
- 飯ノ川線 (orange)
- 葛籠川線 (orange)
- 相去線 (orange)
- 里川線 (orange)
- 芳川線 (orange)
- 戸口・戸川線 (orange)
- 地吉線 (orange)
- 北の川・広井線 (orange)
- 野々川線 (orange)
- 古城線 (orange)
- 大道線 (orange)
- 小野線 (orange)
- 下道線 (orange)
- 打井川線 (orange)
- 中津川線 (orange)
- 下津井線 (orange)
| Route | Type | Line color |
|---|---|---|
| 払川線 | Bus | orange |
| 道徳線 | Bus | orange |
| 奥呉地線 | Bus | orange |
| 折合線 | Bus | orange |
| 若井川線 | Bus | orange |
| 川ノ内線 | Bus | orange |
| 神ノ川線 | Bus | orange |
| 床鍋線 | Bus | orange |
| 東北ノ川線 | Bus | orange |
| 飯ノ川線 | Bus | orange |
| 葛籠川線 | Bus | orange |
| 相去線 | Bus | orange |
| 里川線 | Bus | orange |
| 芳川線 | Bus | orange |
| 戸口・戸川線 | Bus | orange |
| 地吉線 | Bus | orange |
| 北の川・広井線 | Bus | orange |
| 野々川線 | Bus | orange |
| 古城線 | Bus | orange |
| 大道線 | Bus | orange |
| 小野線 | Bus | orange |
| 下道線 | Bus | orange |
| 打井川線 | Bus | orange |
| 中津川線 | Bus | orange |
| 下津井線 | Bus | orange |
This feed has 485 stops.
List every stop
- 下津井奥
- 森ヶ内奥
- 窪川駅
- 北琴平町
- 北琴平町
- みどり市前
- みどり市前
- 本町
- 本町
- 福祉センター前
- 福祉センター前
- しまんとハマヤ前
- 窪川高前
- 窪川高前
- 香月が丘
- 香月が丘
- 窪中前
- 窪中前
- くぼかわ病院前
- くぼかわ病院前
- 見付
- 見付
- 宇ノ谷口
- 宇ノ谷口
- 八千数ゴルフ場前
- 八千数ゴルフ場前
- 西藤ノ川
- 西藤ノ川
- 藤ノ川
- 藤ノ川
- 親ケ内
- 親ケ内
- 本堂
- 本堂
- 東本堂
- 東本堂
- 旧帰全農場前
- 旧帰全農場前
- 黒石
- 黒石
- 襟
- 襟
- 弘見
- 弘見
- 袖の川口
- 袖の川口
- 土居
- 土居
- 奈路
- 奈路
- 奥奈路
- 奥奈路
- 平野
- 平野
- 平野集会所
- 平野集会所
- 平野第二
- 平野第二
- 道徳
- 道徳
- 道徳中
- 道徳中
- 道徳奥
- 新開町
- 新開町
- 神ノ西
- 神ノ西
- 宮ノ向
- 宮ノ向
- 五社
- あずまや
- 払川奥
- 呼坂
- 呼坂
- 東窪川
- 東窪川
- 平串橋
- 平串橋
- 平串橋
- 平串橋
- 平串
- 平串
- 浜ノ川
- 浜ノ川
- 西仁井田
- 西仁井田
- 仁井田農協前
- 仁井田農協前
- 神有
- 神有
- 六反地
- 六反地
- 六反地中
- 山株
- 山株
- 替坂口
- 替坂
- 替坂
- 下呉地
- 下呉地
- りん家
- 下呉地分岐
- 松ノ平
- 松ノ平
- 奥魚ノ川
- 奥魚ノ川
- 奥呉地集会所
- 奥呉地
- 大井野
- 大井野
- 茶屋の駄馬
- 茶屋の駄馬
- 口神
- 口神
- 丸山
- 丸山
- 立目
- 立目
- 天ノ川口
- 天ノ川口
- 天ノ川口
- 天ノ川口
- 天ノ川西
- 南川口
- 南川口
- 川口小前
- 川口小前
- 有ノ木
- 有ノ木
- 瓜生野
- 瓜生野
- 下寺野
- 下寺野
- 中寺野
- 中寺野
- 上寺野
- 上寺野
- 西野地
- 西野地
- 長ウネ
- 長ウネ
- 檜生原
- 檜生原
- 神社前
- 神社前
- 大屋敷
- 大屋敷
- 大越
- 大越
- 折合
- 折合集会所
- 折合奥
- 西原
- 西原
- 若井駅
- 若井駅
- 坂本橋
- 坂本橋
- 高野
- 高野
- 若井川下集会所前
- 若井川下集会所前
- 小学校
- 小学校
- 牛舎跡
- 牛舎跡
- 峰ノ上
- 峰ノ上
- 宮内境
- 宮内境
- 下宮内
- 下宮内
- 中宮内
- 中宮内
- 上宮内
- 上宮内
- 東川角渡
- 東川角渡
- 下西川角
- 下西川角
- 西川角
- 西川角
- 上西川角
- 上西川角
- 志和分
- 志和分
- 小野川
- 小野川
- 七里小学校前
- 七里小学校前
- 上小野川
- 上小野川
- ハイタカ
- ハイタカ
- 中村
- 中村
- 勝賀野
- 勝賀野
- 川ノ内集会所
- 川ノ内(窪川)
- 影野
- 影野
- 雪椿
- 雪椿
- 双津ノ川
- 双津ノ川
- 折目
- 折目
- 青木
- 青木
- 縁ノ島
- 縁ノ島
- 床鍋
- 白皇神社
- 白皇神社
- 東岸橋
- 東岸橋
- 中神ノ川第一
- 中神ノ川第一
- 中神ノ川第二
- 中神ノ川第二
- 水源地
- 奥神ノ川
- 富岡
- 富岡
- 中向川
- 中向川
- 中藤ノ川
- 中藤ノ川
- 飯ノ川
- 飯ノ川
- 飯ノ川奥
- 西ノ川口
- 西ノ川口
- 作屋
- 作屋
- 作屋北
- 作屋北
- 平田分岐
- 平田分岐
- 東洋精密前
- 東洋精密前
- 平田口
- 平田口
- うわぞり
- うわぞり
- 米奥口
- 米奥口
- 川奥集会所
- 奥川奥
- and 235 more (see the full list on the map or in the GeoJSON)
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
7 findings, ordered by severity.
Show every finding
- Warning4717 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)
- Warning485 instances
485 of 485 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)
- Warning184 instances
184 of 184 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)
- Warning14 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)
- 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)
- Info1 instance
This feed includes flexible (demand-responsive) service, and riders are told how to book it.
Dial-a-ride and zone service are described for trip planners, not just fixed routes.
Fix: No action needed. (None.)
Validator rule: scorecard_flex_service
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 252 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 252 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.
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/shimantotown-gtfs-shimantotown-bus/2026-07-23.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-23. 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.