Feed status · checked 2026-07-19
Kitaena Kotsu (北恵那交通)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
317 of 317 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
307 of 307 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 255 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 7 kinds of issue across 17994 instances (0 error, 17976 warning, 18 informational).
Service data covers the next 255 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
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (SK, SK, SM, K, K, 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.
- T (blue)
- KB (teal)
- SK (green)
- SK (green)
- S (green)
- SM (purple)
- Y (yellow)
- K (orange)
- K (orange)
- B (teal)
- C (pink)
- E (yellow)
- N (gray)
- F (red)
- M (brown)
| Route | Type | Line color |
|---|---|---|
| T | Bus | blue |
| KB | Bus | teal |
| SK | Bus | green |
| SK | Bus | green |
| S | Bus | green |
| SM | Bus | purple |
| Y | Bus | yellow |
| K | Bus | orange |
| K | Bus | orange |
| B | Bus | teal |
| C | Bus | pink |
| E | Bus | yellow |
| N | Bus | gray |
| F | Bus | red |
| M | Bus | brown |
This feed has 317 stops.
List every stop
- 美乃坂本駅前
- 美乃坂本駅前
- 中洗
- 中津川工業高校前
- 丸岩峠
- 丸岩
- 辻原口
- 岩井戸
- 岩井戸
- 五ツ峯
- 五ツ峯
- 玄済口
- 矢渕
- 恵那西山
- 西山住宅前
- 津戸
- 恵那追分
- 山手町
- 山手町
- 大平
- 宮ノ辻
- 一中前
- 恵那尾崎
- 女夫岩前
- 中津川橋
- 中津川橋
- 三菱工場前
- 三菱工場前
- 尾鳩口
- 尾鳩口
- 西宮町
- 西宮町
- 淀川
- 淀川
- 中津川駅前
- 中津川駅前
- 中津川駅前
- 中津川駅前
- 中津川駅前
- 中津川市民病院
- 松源寺
- 後田中
- 後田クラブ前
- 後田口
- 後田口
- 上手賀野
- 上手賀野
- 手賀野
- 西小学校前
- 西小学校前
- 中京学院大学
- 中京学大口
- 手賀野公園
- 手賀野公園
- 井戸上
- 付知峡口
- 付知中学校前
- 回生堂
- 下付知
- 田瀬橋
- 田瀬橋
- 向田瀬
- 向田瀬
- 下野
- 下野
- 福岡総合事務所前
- 福岡総合事務所前
- 高山
- 高山
- 夜明けの森
- 夜明けの森
- 山の田川
- 山の田川
- 玉蔵橋
- 玉蔵橋
- 中津高校下
- 中津高校下
- 下倉屋
- 上大門
- 大門町
- 一の宮
- 藤山
- 新田
- 竹内医院前
- 竹内医院前
- 桜屋町
- 秋津
- 上見屋
- 中田
- 若宮前
- 黒川谷
- 黒川谷
- 稲荷橋
- 稲荷橋
- 狩宿
- 狩宿
- 芝ヶ瀬
- 芝ヶ瀬
- 島田橋
- 島田橋
- 樋の口
- 樋の口
- 深笹住宅前
- 深笹住宅前
- 馬場
- 馬場
- 長根
- 長根
- 病院前
- 病院前
- 関戸
- 関戸
- 並松
- 並松
- 上並松
- 上並松
- 上苗木
- 上苗木
- 苗木
- 苗木
- 新谷
- 新谷
- 城山
- 城山
- 恵那山ウェストン公園前
- 川上
- ます池前
- 滝ケ沢
- 川上橋
- 尾ケ岩
- 王子製紙前
- MP前
- 社宅前
- 社宅前
- 中村上
- 中村上
- 八幡神社前
- 八幡神社前
- クラブ下
- クラブ下
- 佼成会前
- 佼成会前
- 中津川市役所
- 中津川合同庁舎前
- 昭和橋
- 実戸浄水場前
- 三管橋
- 宗泉寺
- 宗泉寺口
- 合の根口
- 恵下橋
- 清水刈
- 宮前
- 公民館前
- 三菱社宅前
- 松田橋
- 一色
- 付知峡倉屋温泉
- 北恵那交通前
- 北恵那交通前
- 子野川
- 子野川
- 丸山
- 丸山
- 三五沢
- 三五沢
- 堀割
- 堀割
- 月柿
- 月柿
- 与坂
- 与坂
- 診療所下
- 診療所下
- 落合
- 落合
- 見晴口
- 見晴口
- 大久手口
- 大久手口
- 清水平
- 清水平
- 嫁射沢
- 嫁射沢
- 轟谷
- 轟谷
- 大沢橋
- 大沢橋
- 大沢橋
- 大沢橋
- 大島屋前
- 大島屋前
- 吾妻屋前
- 吾妻屋前
- 山口総合事務所下
- 山口総合事務所下
- 大又口
- 大又口
- 神社前
- 神社前
- 青木口
- 青木口
- 弥栄橋
- 弥栄橋
- 坂下診療所
- 坂下駅前
- 島平
- 島平
- 体育館前
- 体育館前
- 島橋
- 島橋
- 小田
- 蔵田寺
- 島井田
- 黄川橋
- 黄川橋
- 椿沢橋
- 白山町
- 小野沢
- 小野沢
- 上野口
- 下野口
- 下野口
- 田瀬坂
- だて洞口
- 南小学校
- 南小学校
- 白沢
- 白沢
- 中畑
- 中畑
- 尾ヶ平
- 尾ヶ平
- 広島野
- 広島野
- 袖谷橋
- 袖谷橋
- 万賀
- 加子母福崎公園
- 加子母福崎公園
- 加子母総合事務所前
- 木曽路口
- 木曽路口
- 釜橋
- 釜橋
- 熊洞
- 留橋
- 留橋
- 立岩
- and 67 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 | 75.5 | first check |
| 2026-07-19 | 75.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
10 findings, ordered by severity.
Show every finding
- Warning17971 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)
- Warning317 instances
317 of 317 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)
- Warning307 instances
307 of 307 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)
- 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)
- Warning2 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Validator rule: stop_without_stop_time · 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)
- Info10 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)
- Info6 instances
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)
- 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 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 255 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 317 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 255 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/kitaena-kotsu/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.