Feed status · checked 2026-07-19
Kinokawa City Community Bus (紀の川市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.2, validator 8.0.1.
Checked for changes 4 hours ago; last changed 4 hours ago.
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
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category
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
367 of 367 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
72 of 72 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
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.
Add the required column named in the finding to the flagged file. · 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_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.
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 621 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 2502 instances (3 error, 2496 warning, 3 informational).
Service data covers the next 621 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 (地域巡回バス 21西貴志コース, 地域巡回バス 30桃山鞆渕コース, 【予約制】地域巡回バス 31桃山鞆渕コース, 紀の川コミュニティバス 西（左）回りコース).
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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 地域巡回バス 10名手上那賀支所コース | Bus | blue (no shape in feed) |
| 地域巡回バス 11川原西脇コース | Bus | green (no shape in feed) |
| 地域巡回バス 12赤尾藤井コース | Bus | yellow (no shape in feed) |
| 地域巡回バス 13長田竜門コース | Bus | pink (no shape in feed) |
| 地域巡回バス 14北勢田コース | Bus | pink (no shape in feed) |
| 地域巡回バス 15三谷コース | Bus | teal (no shape in feed) |
| 地域巡回バス 16黒土高野コース | Bus | white (no shape in feed) |
| 地域巡回バス 17打田貴志川コース | Bus | yellow (no shape in feed) |
| 地域巡回バス 20東貴志丸栖コース | Bus | purple (no shape in feed) |
| 地域巡回バス 21西貴志コース | Bus | orange (no shape in feed) |
| 地域巡回バス 30桃山鞆渕コース | Bus | red (no shape in feed) |
| 【予約制】地域巡回バス 31桃山鞆渕コース | Bus | red (no shape in feed) |
| 地域巡回バス 32細野貴志川コース | Bus | yellow (no shape in feed) |
| 【予約制】地域巡回バス 33細野貴志川コース | Bus | yellow (no shape in feed) |
| 紀の川コミュニティバス 西（左）回りコース | Bus | orange (no shape in feed) |
| 紀の川コミュニティバス 東（右）回りコース | Bus | teal (no shape in feed) |
This feed has 367 stops.
List every stop
- 紀の川市那賀支所
- 名手駅前
- 西元町
- 那賀中学校前
- 那賀中学校前
- 青洲の里前
- 青洲の里前
- 福垣内
- 福垣内
- 切畑
- 切畑
- ＪＡ直売所前
- ＪＡ直売所前
- 林ヶ峰
- 林ヶ峰
- ふうの丘前
- ふうの丘前
- 名手上
- 名手上北
- 平野北
- 平野南
- 佃
- 名手下
- 猪岡
- 江川農業会館前
- 西野山北
- 神戸
- 麻生津大橋南
- 麻生津大橋南
- 麻生津中
- 西脇グリーンタウン前
- 西脇
- 西脇西
- 荒見東
- 荒見東
- 井田
- 井田
- 紀の川市粉河支所・粉河ふるさとセンター
- ＪＡ粉河支所前
- 粉河駅
- 粉河駅
- 西貴志コミュニティセンター
- 西貴志コミュニティセンター
- 天北
- 這上
- 秋葉前
- 秋葉前
- 粉河寺
- 粉河寺西
- 粉河寺西
- 猪の垣
- 猪の垣
- 藤井
- 藤井北
- 中津川南
- 広域農道北長田
- 広域農道北長田
- 長山団地
- 北長田中
- 北長田
- 北長田
- 北志野
- 北志野
- 南志野
- 南志野集会所前
- 南志野南
- 赤尾
- 赤尾南
- 広野北
- 広野北
- 打田国道口
- 打田国道口
- 西山口
- 西山口
- 那賀病院
- 打田駅
- 紀の川市役所
- 巡回粉河
- 巡回穴伏
- 名手公民館前
- 葛谷
- 西山丹生脇
- 西山丹生脇
- 岸宮
- 岸宮
- 尼寺
- 北山
- 北山
- 丸栖北
- 丸栖北
- 那賀総合センター前
- 丹生橋東
- 上野井団地前
- 馬宿
- ＪＡ川原事業所前
- 川原保育所前
- 川原郵便局前
- 東川原
- 西川原
- 堂田辻
- 川原橋
- 庚申前
- 広域農道上丹生谷
- 中ノ才児童館前
- 中ノ才南
- 秋葉台
- エバーグリーン団地前
- 荒見
- 杉原
- 竜門小学校東
- 船戸山
- 船戸山
- 杉原西
- 風市
- 風市西
- 遠方橋
- 遠方東
- 遠方西
- 窪
- 打田南
- 打田
- 打田
- ＪＡ営農センター前
- 船戸跨線橋北詰
- 船戸跨線橋北詰
- 北大井
- 四日市
- 四日市
- 北中
- 神領北
- 神領北
- 北勢田ハイテクパーク
- 荒見中
- 登尾
- 枇杷谷
- 枇杷谷
- 西三谷
- 西三谷
- 岩出市役所
- 巡回中三谷
- 巡回中三谷
- 中三谷
- 中三谷
- 高畝団地前
- 差熊池
- 差熊池
- 紀の川市役所前
- 紀の川市役所前
- 竜門橋南詰
- 宮
- 岩出駅
- 岩出
- 岩出
- 那賀総合庁舎前
- 那賀総合庁舎前
- 岡田北
- 西井阪
- 西井阪
- 尾崎北
- 尾崎北
- 北畑野上
- 東国分児童公園南
- 下井阪駅東
- 下井阪駅東
- オーストリート前
- 桃源郷口
- 八坂神社前
- 段
- 市場
- 紀の川市桃山支所
- 下井阪
- 下井阪
- 北神田
- 三船神社前
- 桃源郷運動公園下
- 三和公民館前
- きらめきセンター
- 小林
- 小林西
- 尼岡橋
- 尼岡橋
- 桃山第２工業団地
- 桃山第２工業団地
- 曽池前
- 国分寺東
- 国分寺東
- 貴志川大橋東詰
- 貴志川大橋東詰
- 貴志川大橋東詰
- 貴志川大橋東詰
- ショッピングタウン前
- ショッピングタウン前
- 紀の川市貴志川支所
- 紀の川市貴志川支所
- 貴志駅
- 貴志駅
- 山口団地
- 消防器具庫前
- 農業試験場入口
- 篭池前
- 貴志川スポーツ公園前
- 山田ダム
- 東三谷
- 東三谷
- 銚子ノ口集会所前
- 神縄掛
- 野田原集会所前
- 蛍の里
- 三宝寺集会所前
- 光長集会所前
- 細野キャンプ場前
- 垣内
- 最上公民館前
- めっけもん広場前
- めっけもん広場前
- 古和田
- 古和田
- 打田駅西
- 打田駅西
- 公立那賀病院
- 西行法師像前
- 西行法師像前
- 百合山
- 百合山
- 滝の平
- 五百谷口
- 中の宮
- 犬の墓
- 大原口
- 大原
- 善田集会所前
- 桃山小学校跡前
- 黒川
- 高原
- 百合
- 細野口
- 彦谷口
- 和田
- 大西
- 新子
- 湯ノ本
- 鞆渕保育所前
- 鞆渕駐在所前
- 鞆渕八幡前
- 北原
- 段新田
- 出会橋
- 鳥渕
- 下志賀
- 庄前峠
- and 117 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 70.0 | first check |
| 2026-07-19 | 70.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Error3 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2472 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)
- Warning367 instances
367 of 367 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)
- Warning72 instances
72 of 72 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)
- Warning21 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)
- Warning2 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.)
Validator rule: 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.)
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)
- Info3 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.)
Validator rule: 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).
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)
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 621 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 621 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 66 / 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/kinokawa-city-community-bus/2026-07-19.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-19. 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.