GTFS Scorecard
← All agencies

Feed status · checked 2026-09-05

Kumano City Bus and Mihama Town Bus (熊野市バス・御浜町自主運行バス)

Based on the official feed source on file

Service mode Bus

80.9 / 100

First scorecard for this agency

Catalogued in Mie, Japan.

Covers 117 daysAccessibility gapsRealtime not yet published

Kumano City's bus network together with Mihama Town's own-operation routes, published as one archive by Kumano City.

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.3, validator 8.0.1.

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.

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

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

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

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.

Feed evidence
236 of 236 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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.

  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 117 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

Correctness85.0 / 100

The MobilityData validator flagged 4 kinds of issue across 2141 instances (0 error, 2137 warning, 4 informational).

Freshness100.0 / 100

Service data covers the next 117 days.

Rider experience60.0 / 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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

This feed has no route shapes, so the map shows its stops only.

This feed has 236 stops.

Skip to route and stop data

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.

Routes in Kumano City Bus and Mihama Town Bus (熊野市バス・御浜町自主運行バス)'s feed
RouteTypeLine color
A熊野古道瀞流荘線Busyellow (no shape in feed)
B飛鳥・五郷線Busgreen (no shape in feed)
C清流・那智黒石の里線Busblack (no shape in feed)
D潮風かほる熊野古道線Busorange (no shape in feed)
E瀞流荘紀南病院線Busteal (no shape in feed)
F紀和・本宮線Busbrown (no shape in feed)
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

6 findings, ordered by severity.

Show every finding
  • Warning2117 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

  • Warning236 instances

    236 of 236 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 · See GTFS Schedule reference

  • Warning52 instances

    52 of 52 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 · See GTFS Schedule reference

  • Warning20 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 · See MobilityData GTFS Validator rules

  • Info2 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.)

    Finding code: platform_without_parent_station · 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.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

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 117 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 117 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 85 / 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.

Kumano City Bus and Mihama Town Bus (熊野市バス・御浜町自主運行バス) GTFS data quality grade: B

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/kumano-city-bus/2026-09-05.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-09-05. 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.