Feed status · checked 2026-07-23
津野町コミュニティバス「つのバス」
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Kochi, 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.
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
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
283 of 283 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
81 of 81 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
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 161 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 4 kinds of issue across 3445 instances (0 error, 3445 warning, 0 informational).
Service data covers the next 161 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 貝ノ川・東黒川線 (green)
- 久保川・大谷線 (green)
- 桂線 (green)
- 大西・上井田線 (green)
- 勝登呂・舞ノ川線 (green)
- 駄場線 (green)
- 三間川・藤ノ川線 (green)
- 床鍋線 (green)
- 桑ノ川・赤木・西谷線 (green)
- 西黒川線 (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 |
| 桑ノ川・赤木・西谷線 | Bus | green |
| 西黒川線 | Bus | green |
| 大古味・芳生野線 | Bus | green |
| 口目ヶ市線 | Bus | green |
| 日曽の川線 | Bus | green |
| 西倉川線 | Bus | green |
| 谷の内線 | Bus | green |
| 高野線 | Bus | green |
| 中村線 | Bus | green |
This feed has 283 stops.
List every stop
- 里楽
- ディスカ
- 姫野々診療所
- 姫野々診療所
- 上井田口
- 上井田口
- 酒蔵ホール
- 酒蔵ホール
- 久保川橋
- 久保川橋
- 永野
- 永野
- 役場本庁
- 聖音寺前
- 聖音寺前
- 石神奈路
- 石神奈路
- 赤木口
- 赤木口
- 赤木口
- 桑ノ川口
- 桑ノ川口
- 桑ノ川口
- 船野入口
- 船野入口
- 船野入口
- 船野入口
- 船野
- 船野
- 舞ノ川口
- 舞ノ川口
- 舞ノ川口
- 藤ノ川口
- 藤ノ川口
- 黒川口
- 黒川口
- 西谷口
- 西谷口
- ムクノ木
- ムクノ木
- 新土居
- 新土居
- 杉ノ川郵便局前
- 診療所前
- 診療所前
- 診療所前
- 日浦
- 日浦
- 大谷口
- 大谷口
- 大谷橋
- 大谷橋
- 大川下
- 大川下
- 西森商店
- 西森商店
- 大川橋
- 大川橋
- 桃ノ木
- 桃ノ木
- 二ツ家
- 二ツ家
- 白石小学校前
- 白石小学校前
- 重谷
- 重谷
- 大西口
- 大西口
- 東黒川集会所
- 東黒川奥
- 中谷奥
- 貝ノ川集会所
- 貝ノ川上
- 久保川奥
- 久保川集会所
- 農協西支所前
- 農協西支所前
- 楠木山
- 本成
- 杉ノ川
- 大谷集会所
- 大谷中
- 道の駅
- 熊野神社前
- 熊野神社前
- 上桂
- 上桂
- 桂
- 桂
- 上の段
- 上の段
- 竹ヶ谷
- 竹ヶ谷
- 新重谷
- 新重谷
- 新大西橋
- 大西中
- 石鎚神社
- 上井田集会所
- 馬関集会所
- 勝登呂集会所
- 勝登呂奥
- 舞ノ川集会所
- 舞ノ川奥
- 大川
- 駄場中
- 駄場
- 桃ノ木大橋
- 中谷集会所
- 仲野集会所
- 宇津ヶ藪分岐
- 宇津ヶ藪分岐
- 宇津ヶ藪
- 三間川集会所
- 三間川奥
- 正尺
- 正尺
- 葉山中学校
- 葉山中学校
- 藤ノ川集会所
- 藤ノ川奥
- 梶足
- 梶足
- もくもく
- もくもく
- 東倉川集会所
- 東倉川集会所
- 床鍋大橋
- 森の巣箱
- 中谷
- 七曲
- 桑ノ川中集会所
- 白保者
- 桑ノ川上集会所
- 桑ノ川奥
- 赤木町営住宅口
- 赤木集会所
- 西谷集会所
- 西黒川奥
- おとうば口
- 一斗俵奥
- よりざこ
- 新田役場
- 新田
- 新田
- 新田商店街
- 新田商店街
- 保井川
- 保井川
- 下野
- 下野
- 一本橋
- 一本橋
- 奈路橋
- 奈路橋
- 奈路橋
- 畦屋
- 畦屋
- 白砂利
- 白砂利
- 小豆井谷
- 小豆井谷
- 長沢の滝口
- 長沢の滝口
- 古味口
- 古味口
- 旧宮
- 旧宮
- 郷内
- 郷内
- 王在家
- 王在家
- 枝ヶ谷分岐
- 枝ヶ谷分岐
- 新田東口
- 新田東口
- 高原荘前
- 高原荘前
- 力石西
- 力石西
- 力石
- 力石
- 芹川入口
- 芹川入口
- 烏出川
- 烏出川
- 川上橋
- 川上橋
- 大野見分岐
- 大野見分岐
- 教習所前
- 教習所前
- 船戸
- 船戸
- 船戸集会所
- 北川上旧道
- 北川上旧道
- 宮谷
- 宮谷
- 土居の越
- 土居の越
- 北川下
- 北川下
- 番城
- 番城
- 郷麓温泉
- 郷麓温泉
- 大古味
- ケヤキ下
- 虎太郎邸
- 諏訪神社
- 蓬尾
- 大窪
- 口目ヶ市
- 口目ヶ市
- 寺川
- 寺川
- 日曽の川口
- 日曽の川口
- 日曽の川集会所
- 日曽の川集会所
- 奥倉川
- 奥倉川
- 西倉川集会所
- 西倉川集会所
- 西倉川分岐
- 西倉川分岐
- 桑ヶ市
- 岩土
- 岩土
- 谷の内
- 谷の内上
- 木桑川橋
- 木桑川橋
- お大師前
- お大師前
- 木桑口
- 木桑口
- 戸別当トンネル東口
- 戸別当トンネル東口
- 戸別当トンネル西口
- 戸別当トンネル西口
- 大門
- 大門
- 堂ヶ市
- 堂ヶ市奥
- 本谷
- 本谷
- 本谷上
- 高野
- and 33 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
7 findings, ordered by severity.
Show every finding
- Warning3425 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)
- Warning283 instances
283 of 283 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)
- Warning81 instances
81 of 81 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)
- Warning12 instances
Stop has too many matches for shape (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_has_too_many_matches_for_shape' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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)
- 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)
- 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. 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 161 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 161 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 76 / 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/kochi-tsunotown-gtfs-tsunotown-bus/2026-07-23.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-23. 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.