Feed status · checked 2026-09-05
Kumano Gobo Nankai Bus Gobo 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
361 of 361 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
82 of 82 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
- 361 of 361 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
- 82 of 82 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 56 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 7 kinds of issue across 3225 instances (0 error, 3219 warning, 6 informational).
Service data covers the next 56 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
4 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.
This feed has 361 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.
- 日高川線 (yellow)
- 阿尾線 (white)
- 日裏線 (purple)
- 日の岬パーク線 (red)
- 印南線 (orange)
- 湯浅線 (brown)
| Route | Type | Line color |
|---|---|---|
| 日高川線 | Bus | yellow |
| 阿尾線 | Bus | white |
| 日裏線 | Bus | purple |
| 日の岬パーク線 | Bus | red |
| 印南線 | Bus | orange |
| 湯浅線 | Bus | brown |
List every stop
- 御坊南海バス前
- 御坊南海バス前
- 御坊南海バス前
- 体育館前
- 体育館前
- 紀伊御坊駅
- 紀伊御坊駅
- 日高病院前
- 日高病院前
- 日高振興局東口
- 日高振興局東口
- 財部
- 財部
- 北財部
- 北財部
- ながおクリニック前
- ながおクリニック前
- 北裏病院前
- 北裏病院前
- 御坊駅
- 御坊駅
- 御坊駅
- 御坊駅
- 紀央館高校前
- 紀央館高校前
- 小松原
- 小松原
- 職業安定所前
- 職業安定所前
- 島
- 島
- ひまわり団地
- ひまわり団地
- 出島
- 出島
- 東吉田
- 東吉田
- 野口橋
- 野口橋
- 藤井
- 藤井
- 道成寺
- 道成寺駅
- 道成寺駅
- 千津
- 千津
- 日高川町役場前
- 日高川町役場前
- 川辺西小北口
- 川辺西小北口
- 柏木歯科前
- 柏木歯科前
- 矢田
- 矢田
- 打谷椿山団地
- 打谷椿山団地
- 打谷
- 打谷
- 中津川口
- 中津川口
- 玄子
- 玄子
- 早藤
- 早藤
- 早蘇中学校前
- 早蘇中学校前
- 下平川
- 下平川
- 中平川
- 中平川
- 上平川
- 上平川
- 吉子
- 吉子
- 坂本橋
- 坂本橋
- ふるさと産品前
- ふるさと産品前
- 小津茂
- 小津茂
- 観音寺橋
- 観音寺橋
- 中津郵便局前
- 中津郵便局前
- 船津
- 船津
- 上滝本
- 上滝本
- 西原
- 西原
- 高津尾
- 高津尾
- 広瀬口
- 広瀬口
- 姉子
- 姉子
- 三十木橋
- 三十木橋
- 原日浦
- 原日浦
- 平岩
- 平岩
- 下越方
- 下越方
- 越方橋
- 越方橋
- 阿田木
- 阿田木
- 鳥原
- 鳥原
- 川原河
- 斉前
- 斉前
- 丸山（御坊）
- 丸山（御坊）
- 富安
- 富安
- 荊木南
- 荊木南
- 荊木
- 荊木
- 古田医院前
- 古田医院前
- 内原駅
- 日高町役場前
- 日高町役場前
- 上野山歯科医院前
- 上野山歯科医院前
- 小中
- 小中
- 日高中学校前
- 日高中学校前
- 下志賀
- 下志賀
- 志賀小学校前
- 志賀小学校前
- 中志賀
- 中志賀
- 小坂
- 小坂
- 比井
- 比井
- 産湯
- 産湯
- 産湯海水浴場前
- 産湯海水浴場前
- 阿尾漁港前
- 阿尾漁港前
- 阿尾
- 阿尾
- 洲野
- 洲野
- 田杭浜
- 御坊市役所前
- 御坊市役所前
- 御坊中央通り
- 御坊中央通り
- 西御坊
- 西御坊
- 小竹八幡神社前
- 小竹八幡神社前
- 天田橋北詰
- 天田橋北詰
- 天田橋
- 天田橋
- 湊
- 湊
- 北浜
- 北浜
- 塩屋小学校前
- 塩屋小学校前
- 中村
- 中村
- 猪野々
- 猪野々
- 北明神川
- 北明神川
- 明神川
- 明神川
- 松尾
- 松尾
- わらびの
- わらびの
- 稲原中学校前
- 稲原中学校前
- 印南原
- 印南原
- 稲原駅
- 稲原駅
- 滝之口公民館前
- 滝之口公民館前
- 滝の口
- 滝の口
- 奈良井下
- 奈良井下
- 中奈良井
- 中奈良井
- 奈良井上
- 奈良井上
- 古井
- 古井
- 見影橋
- 見影橋
- 白河口
- 白河口
- 脇の谷
- 脇の谷
- 松原
- 松原
- 丹生
- 丹生
- 崎の原
- 崎の原
- 皆瀬川
- 皆瀬川
- 小原
- 小原
- 西神の川
- 西神の川
- 田ノ垣内
- 田ノ垣内
- 切目川ダム前
- 切目川ダム前
- 下上洞橋
- 下上洞橋
- 上洞
- 上洞
- 川又口
- 川又口
- 川又神社前
- 川又神社前
- 川又集会センター前
- 川又集会センター前
- 日裏
- 日裏
- 小森
- 小森
- 川又観音口
- 西小松原
- 西小松原
- 御坊警察署前
- 御坊警察署前
- 日高振興局ロマンシティ前
- 日高振興局ロマンシティ前
- 田井
- 田井
- 吉原
- 吉原
- 西吉原
- 西吉原
- and 111 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
10 findings, ordered by severity.
Show every finding
- Warning3131 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)
- Warning361 instances
361 of 361 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)
- Warning83 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)
- Warning82 instances
82 of 82 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)
- Warning4 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)
- 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)
- Info3 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
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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 56 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 56 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 74 / 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 93 / 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-gobo/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.