Feed status · checked 2026-07-19
Konan City Bus (香南市営バス)
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
232 of 232 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
162 of 162 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 74 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 3766 instances (0 error, 3766 warning, 0 informational).
Service data covers the next 74 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.
- のいち東部循環線 (blue)
- のいち北部循環線 (blue)
- 吉川・下井線 (blue)
- 吉川・横井線 (blue)
- 山南・徳王子線 (blue)
- 西川線 (blue)
- 土居･赤岡線 (blue)
- のいち･かがみ線 (blue)
- 羽尾・細川線 (blue)
- 羽尾・細川線 (blue)
- のいち中部循環線 (blue)
- 羽尾線 (blue)
- 羽尾線 (blue)
- のいち動物公園線 (blue)
| Route | Type | Line color |
|---|---|---|
| のいち東部循環線 | Bus | blue |
| のいち北部循環線 | Bus | blue |
| 吉川・下井線 | Bus | blue |
| 吉川・横井線 | Bus | blue |
| 山南・徳王子線 | Bus | blue |
| 西川線 | Bus | blue |
| 土居･赤岡線 | Bus | blue |
| のいち･かがみ線 | Bus | blue |
| 羽尾・細川線 | Bus | blue |
| 羽尾・細川線 | Bus | blue |
| のいち中部循環線 | Bus | blue |
| 羽尾線 | Bus | blue |
| 羽尾線 | Bus | blue |
| のいち動物公園線 | Bus | blue |
This feed has 232 stops.
List every stop
- のいち駅
- 香南市役所前
- 山下
- 山下
- 新宮西
- 新宮西
- 鈴木内科前
- 鈴木内科前
- みどり野団地通
- みどり野団地通
- 野市中央病院前
- 野市中央病院前
- 野市中央病院前
- 中山田
- 兎田
- 本村公民館前
- 富家通
- 富家通
- 山北クリニック前
- 香我美小学校前
- 香我美小学校前
- 香我美支所前
- 香我美支所前
- 旧Aコープ前(北)
- 旧Aコープ前(北)
- 旧Aコープ前(西)
- 旧Aコープ前(西)
- 久保田通
- 久保田通
- 香我美中学校前
- 香我美中学校前
- 岩田橋
- 岩田橋
- 中ノ村通
- 中ノ村通
- みどり野東
- みどり野東
- 旧みどり野スーパー前
- 旧みどり野スーパー前
- みどり野3丁目
- みどり野3丁目
- 野市郵便局東
- 野市郵便局東
- 兄弟橋北
- 兄弟橋北
- 仁尾島
- 仁尾島
- 横田商店前
- 横田商店前
- 父養寺北
- 父養寺北
- 西佐古処分場前
- 西佐古処分場前
- 西佐古公民館東
- 西佐古公民館東
- 下分公民館前
- 下分公民館前
- つきみ野入口
- つきみ野入口
- 国吉商店前
- 国吉商店前
- 上分口
- 上分口
- 山ノ神谷
- 白岩団地入口
- 白岩団地入口
- 大日寺
- 大日寺
- ゴスイデン
- ゴスイデン
- アクトランド前
- アクトランド前
- ふれあいセンター前
- ふれあいセンター前
- 東部自動車学校前
- 東部自動車学校前
- 野市整形前
- 野市整形前
- 下井団地通
- 下井団地通
- 樫谷橋
- 樫谷橋
- 天野
- 天野
- 旧吉川庁舎前
- 旧吉川庁舎前
- 福井タバコ店前
- 福井タバコ店前
- 沢田酒店前
- 沢田酒店前
- 千鳥橋
- 千鳥橋
- 昭和橋
- 昭和橋
- 保健センター
- 赤岡運動広場前
- 明神
- 明神
- 岸本小学校前
- 岸本小学校前
- 月見山上り口
- 月見山上り口
- 横井
- 横井
- 横井南
- 横井南
- 藤田整形前
- 藤田整形前
- 山下通
- 山下通
- 新宮通
- 新宮通
- 塚田団地
- 山北郵便局前
- 宇山通
- 下河内
- 的場
- たちばな団地
- 岡・拝原
- 稗地
- 稗地
- 稗地公民館前
- 稗地公民館前
- 堀ノ内
- 堀ノ内
- 堀ノ内北
- 自衛隊前
- 変電所
- 徳王子公民館
- 新店
- 香我美市民館入口
- 吉次通
- 吉次通
- 西光通
- 西光通
- 小畠
- 小畠
- 国兼通
- 国兼通
- 岩鍋
- 岩鍋
- 西川公民館前
- 西川公民館前
- そとば通
- そとば通
- 中西川
- 中西川
- 土居ノ谷
- 土居ノ谷
- 樋の谷橋
- 樋の谷橋
- 椋ガサコ
- 椋ガサコ
- 有宮神社
- 有宮神社
- 高畔
- 東部老人憩いの家
- 東部老人憩いの家
- 土居公民館前
- 土居公民館前
- 赤岡北
- 赤岡北
- 北部集会所前
- しお風前
- 野市保育所前
- のいち眼科前
- 夜須横町
- 夜須横町
- 夜須支所前
- 夜須支所前
- 夜須保育所前
- 夜須保育所前
- 夜須学校前
- 夜須学校前
- 土居山
- 土居山
- 赤松通
- 赤松通
- 備後
- 備後
- 上夜須
- 上夜須
- 下添地
- 下添地
- 添地
- 添地
- 楠神社
- 楠神社
- 夜須川
- 夜須川
- 芝
- 両谷口
- 細川老人里の家
- 細川
- 上光国
- 上光国
- 天王
- 国光集会所
- 中の宮神社前
- 檜屋敷
- 国光
- 峠
- 羽尾
- 行間団地
- 成相
- 成相
- アゴデン
- アゴデン
- つきみ野団地
- 赤岡江見町
- 赤岡江見町
- 赤岡本町
- 赤岡本町
- 赤岡医院前
- 赤岡医院前
- 赤岡横町
- 赤岡横町
- 東中筋北
- 東中筋北
- のいち動物公園
- ワイナリー前
- のいち駅南
- 夜須こども園前
- 野市東町
- 野市東町
- 月見山
- 月見山
- 粟島神社前
- 粟島神社前
- 坪井通
- 坪井通
- 夜須駅
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
8 findings, ordered by severity.
Show every finding
- Warning3754 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)
- Warning232 instances
232 of 232 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)
- Warning162 instances
162 of 162 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)
- Warning9 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
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Validator rule: duplicate_route_name · 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)
- Info1 instance
This feed includes flexible (demand-responsive) service, and riders are told how to book it.
Dial-a-ride and zone service are described for trip planners, not just fixed routes.
Fix: No action needed. (None.)
Validator rule: scorecard_flex_service
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 74 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 74 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 78 / 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-konan-city-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.