Feed status · checked 2026-07-19
Seto City Community Bus (瀬戸市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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
231 of 231 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
104 of 104 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 6 kinds of issue across 2164 instances (0 error, 2163 warning, 1 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (住民バス, 上之山線, 上半田川線（品野おでかけバス）, 片草線（品野おでかけバス）, 上之山線, 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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| こうはん線 | Bus | yellow (no shape in feed) |
| こうはん線 | Bus | yellow (no shape in feed) |
| 下半田川線 | Bus | teal (no shape in feed) |
| 岩屋堂線（品野おでかけバス） | Bus | white (no shape in feed) |
| 上之山線 | Bus | green (no shape in feed) |
| 上半田川線（品野おでかけバス） | Bus | pink (no shape in feed) |
| 曽野線 | Bus | gray (no shape in feed) |
| 片草線（品野おでかけバス） | Bus | pink (no shape in feed) |
| 本地線 | Bus | purple (no shape in feed) |
| 本地線（本地おでかけバス） | Bus | purple (no shape in feed) |
| 本地線（本地おでかけバス） | Bus | purple (no shape in feed) |
| 下半田川線 | Bus | teal (no shape in feed) |
| 岩屋堂線（品野おでかけバス） | Bus | white (no shape in feed) |
| 住民バス | Bus | gray (no shape in feed) |
| 上之山線 | Bus | green (no shape in feed) |
| 上半田川線（品野おでかけバス） | Bus | pink (no shape in feed) |
| 曽野線 | Bus | gray (no shape in feed) |
| 片草線（品野おでかけバス） | Bus | pink (no shape in feed) |
| 本地線 | Bus | purple (no shape in feed) |
This feed has 231 stops.
List every stop
- 上之山町
- 上之山町
- 八草駅
- 北丘町南
- 北丘団地
- 北丘町北
- 広之田集会所
- 広之田
- 品野台小学校
- 桑下
- 菩提寺前
- 平町
- 平町
- 北山団地
- 名古屋学院大学
- 西新田
- 中平橋
- 寺前橋
- 上半田川町集荷所
- 榎戸
- 上半田川転回場
- 山畑
- 北脇
- 北脇
- 井上病院
- 井上病院
- 曽野口
- 曽野口
- 曽野橋
- 曽野橋
- 曽野
- 曽野
- 曽野稲荷前
- 曽野稲荷前
- 東曽野農業倉庫
- 北グラウンド
- 北グラウンド
- 品野町６丁目
- 品野町６丁目
- 下品野小学校
- 下品野小学校
- 品野
- 中品野
- 西山町１丁目
- 西山町１丁目
- 上品野口
- 中洞
- 城前
- 中町
- 上品野
- 一ノ瀬橋
- 白岩口
- 白岩町
- 片草町民会館
- 新共栄橋北
- 新共栄橋北
- 南山町３丁目
- 南山町３丁目
- 瀬戸市役所
- 保健所前［瀬戸市］
- 新水無瀬橋
- 新水無瀬橋
- 新田町
- 新田町
- デジタルリサーチパークセンター
- 西脇町
- 西脇町
- 幡山西小学校西
- 幡山西小学校西
- 本地会館
- 本地会館
- 西本地
- 西本地
- バロー瀬戸西店
- 西山町南
- 西山町南
- 本地南部集会所
- 井戸金町
- 坂上町西
- 立花
- 愛知医大
- 穴田
- 穴田
- 北山団地中
- 根の鼻町集会所
- 根の鼻町集会所
- 西山町北
- 東山町
- 東山町
- 東山小学校
- 東山小学校
- やまて坂
- やまて坂
- ひまわり台
- ひまわり台
- 陶生病院
- さつき台
- さつき台
- すみれ台
- すみれ台
- コミュニティききょう台
- コミュニティききょう台
- イオン瀬戸みずの店
- 北松山町
- 北松山町
- 小田妻
- 小田妻
- ゆりの台
- ゆりの台
- 本郷町
- 本郷町
- 水野支所
- 水野支所
- 三社大明神
- 三社大明神
- 瀬戸市立図書館
- 水野中橋
- 水野中橋
- 中水野駅
- 十軒家
- 十軒家
- 鹿乗町東
- 鹿乗町東
- 鹿乗町
- 鹿乗町
- 鹿乗町民会館
- 鹿乗町民会館
- 川平町
- 川平町
- 定光寺駅
- 定光寺公園
- 定光寺公園
- 定光寺町民会館
- 定光寺町民会館
- 新瀬戸駅
- 定光寺町東
- 定光寺町東
- 掛川小学校
- 掛川小学校
- 下半田川町
- 下半田川町
- 下半田川町民会館
- 下半田川町民会館
- 妻之神
- 妻之神
- しなのバスセンター
- バロー品野店
- 品野町３丁目西
- 品野町３丁目東
- 水南町
- 水南町
- 窯東山
- 二又池北
- 窯町
- 岩屋堂
- 鳥原町東
- 鳥原町中
- 鳥原町西
- 鳥原橋
- 八幡台西
- 八幡台外周
- 效範公民館前
- 效範公民館前
- はちまん幼稚園
- 八幡台３丁目
- センター地区のりば
- 商店街・タクシーのりば［萩山台側］
- せと在宅福祉センター前
- 光陵中学校前
- 萩山公民館
- ひだまりステーション８丁目
- 商店街・タクシーのりば［原山台側］
- 原山台７丁目児童公園前
- 水野駅
- 水野駅
- 原山台集会所
- 原山小学校前
- 原山台東
- 萩山台北
- 瀬戸駅前
- 西蔵所
- 西蔵所
- 文化センター［瀬戸市］
- 文化センター［瀬戸市］
- 水無瀬中学校
- 水無瀬中学校
- 幡野町北
- 幡野町北
- 東赤重町
- 東赤重町
- やすらぎ会館
- 新郷地域交流センター前
- 新郷地域交流センター前
- みどりのまち病院
- 瀬戸口駅北口
- 瀬戸口駅北口
- 瀬戸口駅
- 瀬戸グリーンセンター
- 幡山支所
- 幡山支所
- 西米泉町
- 西米泉町
- 東米泉町
- 東米泉町
- 石田町
- 石田町
- 今林町
- 今林町
- 共栄通
- 共栄通
- 山口郵便局
- 山口郵便局
- 八幡社前
- 八幡社前
- 萩殿町
- 萩殿町
- 宝ヶ丘町
- 宝ヶ丘町
- 八幡町
- 八幡町
- 山口駅
- 大坪町
- 大坪町
- 上之山町２丁目
- 上之山町２丁目
- サンヒル上之山
- サンヒル上之山
- 愛・パーク
- 愛・パーク
- 共栄橋
- 共栄橋
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 72.7 | first check |
| 2026-07-19 | 72.7 | 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
9 findings, ordered by severity.
Show every finding
- Warning2119 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)
- Warning231 instances
231 of 231 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)
- Warning104 instances
104 of 104 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)
- Warning31 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)
- Warning9 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)
- Warning3 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.)
Validator rule: 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.)
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)
- 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)
- 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.
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 72 / 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/seto-city-community-bus/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.