Feed status · checked 2026-07-23
さつきバス (可児市)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Gifu, 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_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
98 of 98 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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.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_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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 251 days.
- Published accessibility data
- Accessibility information is stated for 100% 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 4501 instances (0 error, 4499 warning, 2 informational).
Service data covers the next 251 days.
100% of stops state wheelchair accessibility (68% marked accessible, 32% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (68% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (さつきバス 1中心循環線, さつきバス 2中心循環線, さつきバス 7桜ヶ丘線, さつきバス 8桜ヶ丘線, さつきバス 3西部線, and more).
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
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.
- さつきバス 1中心循環線 (pink)
- さつきバス 2中心循環線 (pink)
- さつきバス 9兼山線 (blue)
- さつきバス 5東部線 (brown)
- さつきバス 6東部線 (brown)
- さつきバス 7桜ヶ丘線 (green)
- さつきバス 8桜ヶ丘線 (green)
- さつきバス 3西部線 (red)
- さつきバス 4西部線 (red)
| Route | Type | Line color |
|---|---|---|
| さつきバス 1中心循環線 | Bus | pink |
| さつきバス 2中心循環線 | Bus | pink |
| さつきバス 9兼山線 | Bus | blue |
| さつきバス 5東部線 | Bus | brown |
| さつきバス 6東部線 | Bus | brown |
| さつきバス 7桜ヶ丘線 | Bus | green |
| さつきバス 8桜ヶ丘線 | Bus | green |
| さつきバス 3西部線 | Bus | red |
| さつきバス 4西部線 | Bus | red |
This feed has 114 stops.
List every stop
- 伊川
- 伊川
- 皐ケ丘１丁目
- 皐ケ丘１丁目
- 皐ケ丘９丁目
- 皐ケ丘９丁目
- 皐ケ丘６丁目
- 皐ケ丘６丁目
- 皐ケ丘４丁目
- 皐ケ丘４丁目
- 桜ケ丘５丁目
- 桜ケ丘５丁目
- 桜ケ丘４丁目
- 桜ケ丘４丁目
- 桜ケ丘３丁目
- 桜ケ丘３丁目
- 桜ケ丘１丁目
- 桂ケ丘１丁目
- 桂ケ丘１丁目
- 桂ケ丘２丁目
- 桂ケ丘２丁目
- 桂ケ丘３丁目
- 桂ケ丘３丁目
- ぎふワールド・ローズガーデン
- 桜ケ丘地区センター
- 桜ケ丘地区センター
- 兼山橋
- 六角堂
- 元役場前
- 元役場前
- 城戸坂
- 城戸坂
- 下渡橋
- 下渡橋
- 兼山郵便局前
- 兼山郵便局前
- 若葉台口
- 若葉台口
- 若葉台中央
- 若葉台中央
- 春里地区センター
- 可児とうのう病院
- 井之鼻
- 井之鼻
- 可児川苑
- 坂戸西
- 坂戸西
- 坂戸東
- 坂戸東
- ヨシヅヤ可児店
- 鳥屋場橋西
- 鳥屋場橋西
- 鳥屋場橋
- 鳥屋場橋
- 鳥屋場
- 鳥屋場
- 中央通り
- 中央通り
- 村木
- 村木
- 広見
- 広見
- 羽生ケ丘
- 羽生ケ丘
- 羽生ケ丘４丁目
- 羽生ケ丘４丁目
- 羽生ケ丘５丁目
- 羽生ケ丘５丁目
- 沢渡南
- 沢渡南
- 羽生ケ丘１丁目
- 羽生ケ丘２丁目
- 広眺ケ丘１０丁目
- 広眺ケ丘１０丁目
- 広眺ケ丘７丁目
- 広眺ケ丘７丁目
- 広眺ケ丘５丁目
- 広眺ケ丘５丁目
- 広眺ケ丘２丁目
- 広眺ケ丘２丁目
- 広見地区センター
- 山岸
- 山岸
- ドン・キホーテＵＮＹ可児店
- 前波公民館
- ラスパ御嵩
- 秋葉台
- やすらぎ館前
- 三峰
- 福寿苑
- 日本ライン今渡駅
- 福祉センター
- 文化創造センター
- 東上屋敷西
- 東上屋敷西
- 沓井
- 沓井
- 市役所
- 図書館
- 図書館
- 可児駅
- 西可児駅
- 舟岡
- 舟岡
- 舟岡公民館
- 舟岡公民館
- 徳野
- 徳野
- 緑ケ丘２丁目
- 緑ケ丘３丁目
- 緑ケ丘３丁目
- 旧中恵土消防車庫
- 東上屋敷
- 東上屋敷
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
6 findings, ordered by severity.
Show every finding
- Warning4425 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)
- Warning98 instances
98 of 98 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)
- Warning73 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)
- 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
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 100% 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 251 days.
- Accessible Not yet
- States wheelchair access on 100% 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 251 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 77 / 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/kanicity-satsukibus/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.