Feed status · checked 2026-09-05
Toyota Oiden Bus (とよたおいでんバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Aichi, 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.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
498 of 498 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
802 of 802 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 498 of 498 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 802 of 802 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 207 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 8 kinds of issue across 24701 instances (0 error, 24586 warning, 115 informational).
Service data covers the next 207 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 (とよたおいでんバス2小原・豊田線, とよたおいでんバス2藤岡・豊田線（西中山経由）, とよたおいでんバス7稲武・足助線, とよたおいでんバス7快速いなぶ, とよたおいでんバス10下山・豊田線, 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.
This feed has 498 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- とよたおいでんバス1藤岡・豊田線（加納経由） (yellow)
- とよたおいでんバス2小原・豊田線 (red)
- とよたおいでんバス2藤岡・豊田線（西中山経由） (teal)
- とよたおいでんバス5旭・豊田線 (white)
- とよたおいでんバス6旭・足助線 (teal)
- とよたおいでんバス7稲武・足助線 (pink)
- とよたおいでんバス7快速いなぶ (white)
- とよたおいでんバス8さなげ・足助線 (blue)
- とよたおいでんバス10下山・豊田線 (red)
- とよたおいでんバス21保見・豊田線 (teal)
- とよたおいでんバス22中心市街地玄関口バス (pink)
- とよたおいでんバス25豊田・渋谷線 (red)
- とよたおいでんバス26土橋・豊田東環状線 (teal)
| Route | Type | Line color |
|---|---|---|
| とよたおいでんバス1藤岡・豊田線（加納経由） | Bus | yellow |
| とよたおいでんバス2小原・豊田線 | Bus | red |
| とよたおいでんバス2藤岡・豊田線（西中山経由） | Bus | teal |
| とよたおいでんバス5旭・豊田線 | Bus | white |
| とよたおいでんバス6旭・足助線 | Bus | teal |
| とよたおいでんバス7稲武・足助線 | Bus | pink |
| とよたおいでんバス7快速いなぶ | Bus | white |
| とよたおいでんバス8さなげ・足助線 | Bus | blue |
| とよたおいでんバス10下山・豊田線 | Bus | red |
| とよたおいでんバス21保見・豊田線 | Bus | teal |
| とよたおいでんバス22中心市街地玄関口バス | Bus | pink |
| とよたおいでんバス25豊田・渋谷線 | Bus | red |
| とよたおいでんバス26土橋・豊田東環状線 | Bus | teal |
List every stop
- 豊田市
- 豊田市
- 豊田市
- 豊田市
- 若宮町５丁目
- 若宮町５丁目
- 栄町
- 栄町
- 平芝坂の上公園前
- 平芝坂の上公園前
- けやきワークス
- 西山公園
- 西山公園
- 医療センター
- こども発達センター
- 若草町
- 若草町
- 上豊田駅南
- 上豊田駅南
- 豊田高校南
- 豊田高校南
- 大鳥居
- 大鳥居
- 亀首金山
- 亀首金山
- 亀首森腰
- 亀首森腰
- 舞木源内
- 舞木源内
- 舞木伊保路
- 舞木伊保路
- 猿投北交流館西
- 猿投北交流館西
- 加納末石
- 加納末石
- 加納
- 加納
- 猿投登山口
- 猿投神郷
- 猿投神社前
- 猿投神社前
- 棒の手広場前
- 棒の手広場前
- 中山口
- ふかみ台団地
- ふかみ台団地
- 深見
- 深見
- 迫
- 迫
- ふじのさと入口
- ふじのさと入口
- 飯野
- 飯野
- 藤岡支所
- 喜多町４丁目
- 喜多町４丁目
- 東豊田
- 東豊田
- 久保町
- 久保町
- 陣中町１丁目
- 陣中町１丁目
- 陣中町
- 陣中町
- 梅坪駅
- 梅坪町
- 梅坪町
- 京町
- 京町
- 上原
- 上原
- 四郷
- 四郷
- 四郷天道
- 四郷山畑
- 亀首
- 舞木
- 舞木
- さなげ台団地口
- さなげ台団地口
- 山の田
- 山の田
- 稲場南
- 稲場南
- 下中山
- 緑化センター
- 後田
- 後田
- 西中山
- 上中山
- 上中山
- 加茂丘高校前
- 加茂丘高校前
- 木瀬口
- 藤岡中学校前
- 藤岡中学校前
- 木瀬中
- 木瀬三箇口
- 大平口
- 大平口
- 寺平口
- 蔵屋敷
- 蔵屋敷
- 北篠平
- 大坂
- 小原大草
- 市場口
- 市場口
- 和紙のふるさと
- 和紙のふるさと
- 永太郎
- 下仁木
- 上仁木
- 豊田スタジアム東
- 豊田スタジアム東
- 広川町７丁目
- 広川町７丁目
- 上野町５丁目
- 上野町５丁目
- 平井町
- 平井町
- 百々町
- 百々町
- 扶桑町
- 扶桑町
- 勘八中根
- 勘八中根
- 勘八
- 勘八
- 石野
- 石野
- 広瀬
- 広瀬
- 広瀬
- 広瀬
- 西広瀬町登り
- 西広瀬町登り
- 犬伏橋
- 犬伏橋
- 富田
- 富田
- 藤沢
- 藤沢
- 加茂橋下
- 加茂橋下
- 下川口
- 下川口
- 梨の木
- 梨の木
- 上川口
- 上川口
- 百月
- 上百月
- 川下
- 簗平
- 日面口
- 笹戸橋
- 笹戸
- 笹戸
- 有間
- 平畑口
- 宇内戸
- 小柳
- 間ヶ島
- 間ヶ島
- 小渡西
- 小渡
- 足助病院
- 足助高校前
- 香嵐渓
- 香嵐渓
- 一の谷口
- 一の谷口
- 足助学校下
- 足助田町
- 足助田町
- 足助
- 林間
- 林間
- 豊岡
- 豊岡
- 久木
- 八桑
- 八桑
- 上八桑
- 上八桑
- 新盛
- 新盛
- 細田口
- 北小田宮前
- 北小田
- 平沢下
- 加塩集会所南
- 加塩集会所南
- あさひ荘前
- 加塩
- 加塩
- 加塩橋
- 榊野
- 押井口
- 杉本
- 白石
- 小渡大橋
- 平沢
- 明川局前
- 明川
- 上明川
- 伊勢神
- 連谷口
- 連谷口
- 小田木
- 小田木中
- 高田木
- 高田木
- 水別
- 水別
- 水別広場
- 北水別
- 北水別
- 上黒田
- 上黒田
- 下黒田
- 下黒田
- 黒田
- 御所貝津
- 笹平口
- 中学校前
- 武節宮前
- 武節町
- 稲武郵便局前
- 稲武
- どんぐりの湯前
- 豊田厚生病院
- 豊田厚生病院
- 浄水駅
- 浄水駅
- 浄水駅北
- 浄水駅北
- 浄水町原山
- 浄水町原山
- 原山東
- 原山東
- 愛環四郷駅
- 斉藤病院
- 斉藤病院
- 猿投コミセン南
- 猿投コミセン南
- 猿投駅
- 猿投駅
- and 248 more (see the full list on the map or in the GeoJSON)
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
11 findings, ordered by severity.
Show every finding
- Warning24504 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning802 instances
802 of 802 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning498 instances
498 of 498 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning65 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning15 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info109 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.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 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.)
Finding code: 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.)
Finding code: 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
One requirement remains for this feed to earn 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 207 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 207 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 68 / 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/toyota-oiden-bus/2026-09-05.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-09-05. 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.