Feed status · checked 2026-09-05
Kumano Gobo Nankai Bus Kumano Area (熊野御坊南海バス 熊野エリア)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Wakayama, 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.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
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
329 of 329 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
206 of 206 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
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
- 329 of 329 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
- Feed evidence
- 206 of 206 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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.
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 207 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 7544 instances (0 error, 7533 warning, 11 informational).
Service data covers the next 207 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
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (15 新勝線, 16 新勝線, 71 相筋線, 74 相筋線, 73 松山高田線, 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.
This feed has 329 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.
- 11 新勝線 (teal)
- 12 新勝線 (teal)
- 15 新勝線 (gray)
- 16 新勝線 (gray)
- 17 新勝線 (pink)
- 18 新勝線 (pink)
- 25 新勝線 (purple)
- 26 新勝線 (purple)
- 51 川丈線 (red)
- 52 川丈線 (red)
- 53 川丈線 (yellow)
- 54 川丈線 (yellow)
- 63 小口線 (teal)
- 64 小口線 (teal)
- 65 小口線 (teal)
- 66 小口線 (teal)
- 31 那智山線 (yellow)
- 32 那智山線 (yellow)
- 南紀白浜空港リムジンバス (white)
- 71 相筋線 (pink)
- 74 相筋線 (pink)
- 72 広角住宅線 (brown)
- 75 広角住宅線 (brown)
- 73 松山高田線 (teal)
- 76 松山高田線 (teal)
| Route | Type | Line color |
|---|---|---|
| 11 新勝線 | Bus | teal |
| 12 新勝線 | Bus | teal |
| 15 新勝線 | Bus | gray |
| 16 新勝線 | Bus | gray |
| 17 新勝線 | Bus | pink |
| 18 新勝線 | Bus | pink |
| 25 新勝線 | Bus | purple |
| 26 新勝線 | Bus | purple |
| 51 川丈線 | Bus | red |
| 52 川丈線 | Bus | red |
| 53 川丈線 | Bus | yellow |
| 54 川丈線 | Bus | yellow |
| 63 小口線 | Bus | teal |
| 64 小口線 | Bus | teal |
| 65 小口線 | Bus | teal |
| 66 小口線 | Bus | teal |
| 31 那智山線 | Bus | yellow |
| 32 那智山線 | Bus | yellow |
| 南紀白浜空港リムジンバス | Bus | white |
| 71 相筋線 | Bus | pink |
| 74 相筋線 | Bus | pink |
| 72 広角住宅線 | Bus | brown |
| 75 広角住宅線 | Bus | brown |
| 73 松山高田線 | Bus | teal |
| 76 松山高田線 | Bus | teal |
List every stop
- 自然プール前
- 自然プール前
- 相賀
- 相賀
- 出張
- 出張
- 大宮橋
- 大宮橋
- 高田
- 高田
- 相須
- 相須
- 椋の井
- 椋の井
- 谷口
- 谷口
- 赤木
- 赤木
- 赤木上地
- 赤木上地
- 橋本
- 橋本
- 長井口
- 長井口
- 小和瀬
- 小和瀬
- 小口
- 小口
- 川関
- 川関
- 杉の木
- 杉の木
- 牧野々
- 牧野々
- 井関（那智勝浦）
- 井関（那智勝浦）
- 井関駐在所前
- 井関駐在所前
- 市野々
- 市野々
- 市野々小学校前
- 市野々小学校前
- 南谷
- 南谷
- 二の瀬橋
- 二の瀬橋
- 大門坂
- 大門坂
- 熊野古道
- 熊野古道
- 那智の滝前
- 那智の滝前
- 那智山
- 太地駅
- 太地駅
- 串本 大水崎
- 串本 大水崎
- 広角（高野坂）
- 広角（高野坂）
- 串本駅
- 南紀白浜空港
- 南紀白浜空港
- 橋杭岩マリオット
- 橋杭岩マリオット
- すさみマリオット
- すさみマリオット
- 高森
- 高森
- 高田局前
- 高田局前
- 小口隧道口
- 小口隧道口
- 三輪崎駅前
- 三輪崎駅前
- 中央通り
- 中央通り
- 浮島北
- 浮島北
- オークワ仲之町店前
- オークワ仲之町店前
- オークワ駅前店前
- オークワ駅前店前
- 熊野地
- 熊野地
- 大浜展望駐車場
- 大浜展望駐車場
- 松山団地前
- 松山団地前
- 松山公園前
- 松山公園前
- 南丸山橋
- 南丸山橋
- 三輪崎
- 三輪崎
- 三輪崎
- イオン新宮店前
- イオン新宮店前
- 丸山（新宮）
- 丸山（新宮）
- 田鶴原
- 田鶴原
- 王子橋（王子町）
- 王子橋（王子町）
- 松山
- 松山
- かじの内科前
- かじの内科前
- 高野坂
- 高野坂
- 広角北
- 広角北
- 下田三丁目
- 下田三丁目
- 緑丘
- 緑丘
- 黒潮公園前
- 黒潮公園前
- 緑丘会館前
- 緑丘会館前
- 市役所前
- 市役所前
- 保健センター前
- 保健センター前
- 谷王子
- 谷王子
- 馬町
- 馬町
- 薬師町
- 薬師町
- 権現前
- 権現前
- 下相筋
- 下相筋
- 中相筋
- 中相筋
- 上相筋
- 上相筋
- 光洋中学校前
- 光洋中学校前
- 促進住宅前
- 人権教育センター
- 人権教育センター
- 浮島の森
- 浮島の森
- 井の沢
- 井の沢
- さとう眼科みね内科前
- さとう眼科みね内科前
- 下田
- 下田
- 清水元
- 清水元
- 東仙寺前
- 東仙寺前
- 梅の木
- 梅の木
- 梅の木団地前
- 梅の木団地前
- 運転免許センター
- 運転免許センター
- 運転免許センター
- 広角市営住宅前
- ポロッキー＆ウォラスタ前
- ポロッキー＆ウォラスタ前
- 新宮駅
- 新宮駅
- 新宮駅
- 新宮駅
- 新宮駅
- 蜂伏
- 蜂伏
- 蜂伏通り
- 蜂伏通り
- 蜂伏みさき園
- 蜂伏みさき園
- 市立医療センター
- 木の川
- 木の川
- 佐野下地
- 佐野下地
- 上地
- 上地
- 佐野上地
- 佐野上地
- 佐野
- 佐野
- 佐野松原
- 佐野松原
- 佐野松原
- 阿須賀神社前
- 阿須賀神社前
- 王子橋（佐野）
- 王子橋（佐野）
- 出見世
- 出見世
- 宇久井駅
- 宇久井駅
- 港口
- 港口
- 建石前
- 建石前
- 狗子の川
- 狗子の川
- 赤色の浜
- 赤色の浜
- 那智駅
- 浜の宮
- 浜の宮
- 汐入橋
- 汐入橋
- 新宮城跡前
- 新宮城跡前
- 天満
- 天満
- 須崎
- 須崎
- 朝日町
- 朝日町
- 勝浦局前
- 勝浦局前
- 紀伊勝浦駅
- 近大新宮高校前
- 近大新宮高校前
- 大浜海岸
- 大浜海岸
- 大浜
- 大浜
- 熊野地会館前
- 熊野地会館前
- 蓬莱三丁目
- 蓬莱三丁目
- 丹鶴ホール前
- 丹鶴ホール前
- 蓬莱会館前
- 蓬莱会館前
- 旧道三輪崎駅前
- 三輪崎郵便局前
- 三輪崎小学校前
- 佐野会館前
- 佐野会館前
- 佐野保育所前
- 佐野保育所前
- 新高正門前
- 新高正門前
- 越路
- 越路
- 桧杖
- 桧杖
- 速玉大社前
- 速玉大社前
- and 79 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
9 findings, ordered by severity.
Show every finding
- Warning7285 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)
- Warning329 instances
329 of 329 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 (opens the GTFS Schedule reference on an external site)
- Warning206 instances
206 of 206 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 (opens the GTFS Schedule reference on an external site)
- Warning148 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 (opens the validator rules on an external site)
- Warning99 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.)
Finding code: missing_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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 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 (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.)
Finding code: 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
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 207 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 207 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 71 / 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/kumano-gobo-nankai-bus-kumano/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.