Feed status · checked 2026-07-23
大口町コミュニティバス
Based on the feed this agency publishes
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.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
151 of 151 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
74 of 74 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 312 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 5 kinds of issue across 1169 instances (0 error, 1167 warning, 2 informational).
Service data covers the next 312 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
3 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
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.
- 基幹ルート平日朝便 (pink)
- 基幹ルート毎日運行便 (red)
- 基幹ルート平日夕便 (pink)
- 北部ルート平日朝便 (gray)
- 北部ルート産業団地朝便 (gray)
- 北部ルート毎日運行便 (green)
- 北部ルート平日夕便 (gray)
- 北部ルート産業団地夕便 (gray)
- 中部ルート平日朝便 (yellow)
- 中部ルート毎日運行便 (orange)
- 中部ルート平日夕便 (yellow)
- 南部ルート平日朝便 (gray)
- 南部ルート毎日運行便 (purple)
- 南部ルート平日夕便 (gray)
| Route | Type | Line color |
|---|---|---|
| 基幹ルート平日朝便 | Bus | pink |
| 基幹ルート毎日運行便 | Bus | red |
| 基幹ルート平日夕便 | Bus | pink |
| 北部ルート平日朝便 | Bus | gray |
| 北部ルート産業団地朝便 | Bus | gray |
| 北部ルート毎日運行便 | Bus | green |
| 北部ルート平日夕便 | Bus | gray |
| 北部ルート産業団地夕便 | Bus | gray |
| 中部ルート平日朝便 | Bus | yellow |
| 中部ルート毎日運行便 | Bus | orange |
| 中部ルート平日夕便 | Bus | yellow |
| 南部ルート平日朝便 | Bus | gray |
| 南部ルート毎日運行便 | Bus | purple |
| 南部ルート平日夕便 | Bus | gray |
This feed has 151 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
8 findings, ordered by severity.
Show every finding
- Warning1154 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)
- Warning151 instances
151 of 151 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)
- Warning74 instances
74 of 74 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)
- 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)
- 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)
- Warning1 instance
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.)
Validator rule: missing_recommended_field · 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 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 312 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 312 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/oguchitown-communitybus/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.