Feed status · checked 2026-10-15
室戸市コミュニティバス「むろはぴ号」
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-14
Cataloged in Kochi, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/murotocity/feeds/GTFS-Murotocity_Bus/files/feed.zip?rid=current
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.4, validator 8.0.1.
Checked for changes 6 hours ago; last changed 15 days ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
室戸市コミュニティバス「むろはぴ号」’s published feed lists 8 bus routes, 50 scheduled trips and 193 stops. Its service dates run from 2026-10-01 through 2027-09-30. The published file last changed on 2026-09-30.
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
193 of 193 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.
Fixing this covers all 193 stops in the feed.
⏱ 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
50 of 50 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 50 trips in the feed.
⏱ 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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 350 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 2 kinds of issue across 2078 instances (0 error, 2078 warning, 0 informational).
Service data covers the next 350 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.
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.
This feed has 193 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 入木線 (green)
- 佐喜浜線 (green)
- 室津・河内線 (green)
- 奥郷線 (green)
- 崎山台地線 (green)
- 東の川線 (green)
- 西の川線 (green)
- 西山台地線 (green)
| Route | Type | Line color |
|---|---|---|
| 入木線 | Bus | green |
| 佐喜浜線 | Bus | green |
| 室津・河内線 | Bus | green |
| 奥郷線 | Bus | green |
| 崎山台地線 | Bus | green |
| 東の川線 | Bus | green |
| 西の川線 | Bus | green |
| 西山台地線 | Bus | green |
List every stop
- 佐喜浜車庫
- 佐喜浜郵便局前
- 佐喜浜郵便局前
- 佐喜浜南口
- 佐喜浜南口
- 佐喜浜支所前
- 佐喜浜支所前
- 根丸
- 根丸
- 根丸公民館
- 佐喜浜中学校東口
- 佐喜浜中学校東口
- 入木入口
- 入木入口
- 入木中
- 入木集会所
- 入木東口
- 中里集会所
- 中里集会所
- 中里
- 中里
- 舟場口
- 舟場口
- 舟場
- 保能母口
- 保能母口
- 中尾(佐喜浜)
- 中尾(佐喜浜)
- 鬼戸
- 鬼戸
- 山口下
- 山口下
- 山口上
- はまゆう園
- 河内
- 河内
- 鬼ヶ峠
- 鬼ヶ峠
- 大の川橋
- 大の川橋
- 大久保
- 大久保
- 長野
- 長野
- 稲石上
- 稲石上
- 稲石下
- 稲石下
- 室津郷公会堂
- 室津郷公会堂
- JA室戸支所
- JA室戸支所
- やすらぎ
- やすらぎ西口
- 東大谷口
- 東大谷口
- むろとぴあ
- 室戸市役所前
- 室戸市役所前
- 古戸商店街
- 中道寺
- 両栄橋
- 津寺さん
- 港の上
- 後免
- 後免
- 恵美須神社
- 水尻
- 室戸
- 室戸中央病院
- 元橋
- 元橋
- 上の内
- 上の内
- 東郷口
- 東郷口
- 西川下
- 西川下
- 西川中
- 西川中
- 西川上
- 西川上
- 奥郷
- 浮津西町
- 浮津西町
- 室戸中学校前
- 室戸中学校前
- 向江
- 向江
- 職員住宅前
- 職員住宅前
- 金剛頂寺入口
- 金剛頂寺入口
- 崎山台地
- 崎山台地
- 崎山台地
- 崎山集会所
- 崎山集会所
- 崎山南
- 吉良川屯所
- 吉良川学校通
- 吉良川学校通
- まちなみ駐車場
- 吉良川西町
- 吉良川西町
- 吉良川中町
- 吉良川中町
- 吉良川東町
- 吉良川東町
- 宮の内
- 宮の内
- 内の川下
- 内の川下
- 内の川上
- 内の川上
- 川長集会所
- 川長集会所
- 川長中
- 川長中
- 川長上
- 川長上
- 日南橋
- 日南橋
- 日南
- 日南
- ひなたぼっこ
- ひなたぼっこ
- 東ノ川橋
- 東ノ川橋
- 吉良川橋西詰
- 吉良川橋西詰
- 馬路
- 馬路
- 脇の内下
- 脇の内下
- 脇の内上
- 脇の内上
- 珍地下
- 珍地下
- 珍地上
- 珍地上
- 中の川
- 花まるひろば前
- 高樋橋
- 高樋橋
- 小山
- 小山
- 黒戸
- 原池
- 原池
- マック
- 室戸市役所
- 細松
- 細松
- 大平下
- 大平下
- 大平上
- 室戸小学校前
- 室戸小学校前
- 西山台地口
- 西山台地口
- 磯原南
- 磯原南
- 磯原集会所
- 磯原集会所
- 磯原入口
- 磯原入口
- 長野入口
- 長野入口
- 西地集会所
- 西地集会所
- 太田
- 太田
- 平山
- 中尾(西山)
- 中尾(西山)
- 枦山分岐
- 枦山分岐
- 室戸診療所
- 東町商店街口
- 東町商店街口
- 岩戸神社前
- 岩戸神社前
- 奈良師東
- 奈良師東
- 奈良師集会所口
- 奈良師集会所口
- 森口接骨院
- 森口接骨院
- 崎山北
- 葛
- 奈良師西
- 奈良師西
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 82.2 | first check |
| 2026-10-03 | 82.2 | no change |
| 2026-10-04 | 82.2 | no change |
| 2026-10-05 | 82.2 | no change |
| 2026-10-06 | 82.2 | no change |
| 2026-10-07 | 82.2 | no change |
| 2026-10-08 | 82.2 | no change |
| 2026-10-09 | 82.2 | no change |
| 2026-10-10 | 82.2 | no change |
| 2026-10-11 | 82.2 | no change |
| 2026-10-12 | 82.2 | no change |
| 2026-10-13 | 82.2 | no change |
| 2026-10-14 | 82.2 | no change |
| 2026-10-15 | 82.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-15 (14 checks) | 82b74bb9afd8 | 2027-09-30 | Current rubric: see the trend above |
| 2026-09-30 to 2026-10-01 (2 checks) | 82b74bb9afd8 | 2027-09-30 | B, 82.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-09-29 (63 checks) | b632bea58e7d | 2026-10-01 | F, 53.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-23 to 2026-07-24 (2 checks) | b632bea58e7d | 2026-10-01 | C, 77.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
4 findings, ordered by severity.
Show every finding
- Warning2073 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning193 instances
193 of 193 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning50 instances
50 of 50 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 350 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 349 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 88 / 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.
Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Kochi
Other scorecards in Kochi, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/murotocity-gtfs-murotocity-bus/2026-10-15.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-10-15. 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.