Feed status · checked 2026-07-18
Kai City Bus (甲斐市民バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Yamanashi, 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 1 hours ago; last changed 1 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
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
166 of 166 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
25 of 25 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 +6 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 256 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 63 instances (0 error, 25 warning, 38 informational).
Service data covers the next 256 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)
- 竜王～双葉線 (red)
- 敷島北部線(平見城・下福沢方面) (teal)
- 敷島北部線(大明神・安寺方面) (pink)
- 敷島北部線(清川～敷島仲町線) (yellow)
- 双葉北部線 (orange)
- 敷島～双葉線(竜王駅⇔双葉地区⇔ラザウォーク) (teal)
| Route | Type | Line color |
|---|---|---|
| 敷島～双葉線(竜王駅⇔敷島地区⇔ラザウォーク) | Bus | blue |
| 竜王～双葉線 | Bus | red |
| 敷島北部線(平見城・下福沢方面) | Bus | teal |
| 敷島北部線(大明神・安寺方面) | Bus | pink |
| 敷島北部線(清川～敷島仲町線) | Bus | yellow |
| 双葉北部線 | Bus | orange |
| 敷島～双葉線(竜王駅⇔双葉地区⇔ラザウォーク) | Bus | teal |
This feed has 166 stops.
List every stop
- 米沢
- 駒沢
- 滝沢
- 金剛地公民館
- 宇津谷
- 宇津谷
- 双葉西小学校
- オギノ双葉SC
- オギノ双葉SC
- よってけし響が丘
- よってけし響が丘
- 双葉SA
- 双葉SA
- 登美希望ヶ丘
- 登美希望ヶ丘
- コメリ
- コメリ
- さつき野団地
- さつき野団地
- 敷島中学校
- 敷島中学校
- 甲斐市役所敷島庁舎
- 敷島総合文化会館
- 山梨交通敷島営業所
- 敷島B＆G海洋センター
- 敷島B＆G海洋センター
- 志麻の湯
- 志麻の湯
- 志麻の湯
- 敷島団地
- 大久保
- 島上条
- JR竜王駅南口
- 敷島(滝坂下)
- 敷島(滝坂下)
- 滝坂上
- 滝坂上
- 登美仲宿
- 登美仲宿
- 登美上宿
- 登美上宿
- 双葉高原団地
- 双葉高原団地
- 双葉東小学校
- 登美
- 登美
- イツモア双葉SC
- イツモア双葉SC
- イツモア双葉SC
- イツモア双葉SC
- 下今井
- 下今井
- JR塩崎駅入口
- JR塩崎駅入口
- 大下条南
- 大下条南
- 双葉ふれあい文化館
- 双葉ふれあい文化館
- ラザウォーク甲斐双葉
- 山梨中央銀行竜王支店
- 山梨中央銀行竜王支店
- 甲斐市役所竜王庁舎
- 甲斐市役所竜王庁舎
- 竜王中学校
- 竜王中学校
- JA玉幡集荷場
- JA玉幡集荷場
- オギノ西八幡店
- オギノ西八幡店
- 玉幡四つ角
- 玉幡四つ角
- 下八幡
- 下八幡
- アマノパークス竜王店
- アマノパークス竜王店
- ザ・ビッグ甲斐敷島店
- ザ・ビッグ甲斐敷島店
- 榎
- 榎
- 榎局
- 榎局
- あやめの里
- あやめの里
- 富竹新田３・４区
- 富竹新田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
9 findings, ordered by severity.
Show every finding
- Warning166 instances
166 of 166 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)
- Warning25 instances
25 of 25 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)
- Warning14 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)
- Warning11 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)
- Info29 instances
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.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info16 instances
About 16 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info6 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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)
- Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · 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 256 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 256 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 86 / 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 59 / 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/kai-city-bus/2026-07-18.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-18. 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.