Feed status · checked 2026-07-19
Kuwana City Community Bus K-Bus (桑名市コミュニティバス「Ｋ－バス」)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Mie, 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
312 of 312 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
54 of 54 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 346 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 1756 instances (0 error, 1744 warning, 12 informational).
Service data covers the next 346 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
5 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
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 |
|---|---|---|
| Ｋ－バス東部ルート（Aルート） | Bus | yellow (no shape in feed) |
| Ｋ－バス東部ルート（Ｂルート） | Bus | yellow (no shape in feed) |
| Ｋ－バス西部北ルート（循環Ａ） | Bus | teal (no shape in feed) |
| Ｋ－バス西部北ルート（循環Ｂ） | Bus | teal (no shape in feed) |
| Ｋ－バス北部ルート（循環Ａ） | Bus | teal (no shape in feed) |
| Ｋ－バス北部ルート（循環Ｂ） | Bus | teal (no shape in feed) |
| Ｋ－バス南部西ルート（循環Ａ） | Bus | pink (no shape in feed) |
| Ｋ－バス南部西ルート（循環Ｂ） | Bus | pink (no shape in feed) |
| Ｋ－バス多度ルート（美鹿ルート） | Bus | green (no shape in feed) |
| Ｋ－バス多度ルート（南回り） | Bus | white (no shape in feed) |
| Ｋ－バス多度ルート（北回り） | Bus | yellow (no shape in feed) |
| Ｋ－バス長島ルート（南回り） | Bus | red (no shape in feed) |
| Ｋ－バス長島ルート（北回り） | Bus | teal (no shape in feed) |
| Ｋ－バス南部東ルート（循環Ａ） | Bus | pink (no shape in feed) |
| Ｋ－バス南部東ルート（循環Ｂ） | Bus | pink (no shape in feed) |
This feed has 312 stops.
List every stop
- 桑名駅前
- シティホテル前
- シティホテル前
- くわなメディアライヴ
- くわなメディアライヴ
- 総合福祉会館前
- 総合福祉会館前
- 八間通
- 八間通
- 寺町
- 寺町
- 田町
- 田町
- 船馬町
- 船馬町
- 六華苑
- 六華苑
- 六華苑西
- 六華苑西
- 今中町
- 今中町
- 末広町
- 末広町
- 有楽町
- 有楽町
- 市役所前
- 桑高口
- 桑高口
- 神楽町1丁目
- 霞町2丁目
- 霞町1丁目
- 梅園公園
- 汐見町
- 青葉公園
- 梅園通
- 梅園通
- 大福田寺前
- 大福田寺前
- 山陽町
- 山陽町
- 北別所
- 天神ヶ丘
- 天神ヶ丘
- 大成町
- 大成町
- 播磨郵便局前
- 播磨南
- イオンモール桑名
- イオンモール桑名
- 新西方
- 新西方
- 新西方
- 蓮花寺住宅北
- 蓮花寺住宅北
- 蓮花寺住宅
- 蓮花寺住宅
- 福祉センター
- マザック前
- 額田
- 額田
- 坂井橋
- 坂井橋
- メガドンキ ユニー星川店
- サンシティ
- サンシティ
- 津田学園前
- 嘉例川
- 嘉例川
- 広見ヶ丘
- 大仲新田北
- 大仲新田南
- 桑名工業高校前
- 桑名工業高校前
- 七和住宅口
- 七和住宅口
- 星見ヶ丘6丁目
- 星見ヶ丘6丁目
- 星見ヶ丘南
- 星見ヶ丘南
- スター２１
- スター２１
- 星見ヶ丘9丁目東
- 星見ヶ丘9丁目東
- 法務局前
- 法務局前
- 野田1丁目
- 野田1丁目
- 野田6丁目
- 野田6丁目
- 野田5丁目南
- 野田5丁目南
- 野田5丁目北
- 野田5丁目北
- 大山田団地
- 大山田団地
- 総合運動公園前
- 総合運動公園前
- 陽だまりの丘中
- 陽だまりの丘中
- 陽だまりの丘南
- 陽だまりの丘南
- 陵成中学校前
- 陵成中学校前
- 松ノ木公園前
- 松ノ木南
- 松ノ木南
- 松ノ木東
- 松ノ木東
- 藤が丘南
- 藤が丘南
- 藤が丘中
- 藤が丘中
- 藤が丘北
- 藤が丘北
- 新西方3丁目
- 新西方3丁目
- 新西方中央
- 新西方中央
- 新西方南
- 新西方南
- 名阪桑名インター口
- 参宮通
- 参宮通
- 修徳小学校北
- 東方暁町
- 尾弓田
- 新福島
- 福島
- 福島
- 上之輪
- 明竜町
- 東汰上
- 南高砂町
- 高砂緑地前
- 吉野町
- 北部老人福祉センター
- くわのみ
- 桑栄団地
- 今島町
- 今島町
- 上深谷町
- 上深谷町三砂
- 深谷町北
- 深谷町中
- 深谷町南
- 蛎塚東
- 西汰上
- 大和小学校前
- 播磨駅前北
- 北築地町
- 南築地町
- 桜木町
- 博物館
- 博物館
- 外堀
- 外堀
- 柳原
- 柳原
- 消防署前
- 消防署前
- 円通寺前
- 円通寺前
- 江場中野町
- 江場中野町
- 警察前
- 警察前
- 城南小学校前
- 城南小学校前
- 安永７丁目
- 安永７丁目
- 城南口
- 城南口
- 東金井
- 西金井
- 西金井
- 金井
- 金井
- 桑部東
- 春日台
- 安永消防倉庫
- 安永内科ペインクリニック前
- 了順寺前
- 三ツ矢橋
- 市役所南
- 市役所南
- 前山
- 美鹿
- 滝ヶ橋
- 古野西
- 古野集会所
- 下ヶ平
- 岩壺口
- 北猪飼
- 多度保育所前
- 多度保育所前
- 大門橋
- 大門橋
- 多度大社前
- 多度大社前
- 金谷
- 多度郵便局前
- 多度橋
- 柚井宇賀神社前
- 柚井北
- 大桑クリニック
- 戸津近鉄住宅前
- 多度駅前
- 多度地区市民センター
- 香取北
- 上之郷
- 上之郷七取排水機前
- 油島大橋西詰
- 東福永
- 古敷
- 平賀北
- 平賀南
- 西福永北
- 西福永南
- 大久保
- 猪飼
- 南部コミュニティプラザ前
- ぶでん橋
- 御衣野古浜神社前
- アイリスパーク前
- 御衣野集会所前
- 御衣野東
- 下野代駅北
- 下野代
- 肱江
- 東小山
- 西小山
- 大鳥居西
- 大鳥居東
- 南之郷東
- 南之郷専光坊前
- 南之郷北
- 中須
- 香取南
- 伊曽島駐在所前
- 伊曽島駐在所前
- 伊曽島まちづくり拠点施設前
- 伊曽島まちづくり拠点施設前
- 白坊主山公園
- 野亨寺前
- 松中
- 横満蔵
- 横満蔵
- 長島スポーツランド前
- 長島スポーツランド前
- 伊曽島（名四）
- and 62 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 | 76.5 | first check |
| 2026-07-19 | 76.5 | 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
- Warning1706 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)
- Warning312 instances
312 of 312 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)
- Warning54 instances
54 of 54 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)
- Warning37 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)
- Info9 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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.)
Validator rule: platform_without_parent_station · 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 346 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 346 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 80 / 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/kuwana-city-k-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.