Feed status · checked 2026-07-23
Toyama Yatsuo Community Bus (富山市 八尾コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Toyama, 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.
Checked for changes 70 minutes ago; last changed 70 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
The realtime feed's last update was about 3 hours old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
⏱ A vendor support ticket; treat it as a feed outage.worth about +50 points in its category
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
153 of 153 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
87 of 87 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
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.
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
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_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.
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 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 2564 instances (0 error, 2560 warning, 4 informational).
Service data covers the next 251 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.
Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable.
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.
- 八尾環状線（右回り） (teal)
- 大長谷線（正間行き） (orange)
- 大長谷線（大長谷温泉行き） (orange)
- 大長谷線（八尾駅行き） (orange)
- 桐谷・茗ケ原線（1便） (pink)
- 桐谷・茗ケ原線（2便～4便） (pink)
- 保内線（冬季便） (orange)
- 八尾環状線（左回り） (teal)
- 八尾高校線（杉原公民館行き） (pink)
- 八尾高校線（八尾駅行き） (yellow)
- 八尾高校線（八尾高校行き） (yellow)
- 八尾高校線（八尾高校行き） (pink)
- 杉原線（ゆうゆう館循環）右回り (green)
- 杉原線（ゆうゆう館循環）左回り (green)
- 保内線（右回り） (orange)
- 保内線（左回り） (orange)
- 八尾中核線（KOKUSAIELECTRIC止まり） (teal)
- 八尾中核線（右回り） (teal)
- 八尾中核線（左回り） (teal)
- 八尾中核線（団地北経由KOKUSAIELECTRIC行き） (teal)
- 室牧線（細滝行き） (yellow)
- 室牧線（八尾駅行き） (yellow)
- 野積線（西松瀬行き） (teal)
- 野積線（八尾駅行き） (teal)
- 黒瀬谷線（宮越行き） (pink)
- 黒瀬谷線（八尾駅行き） (pink)
| Route | Type | Line color |
|---|---|---|
| 八尾環状線（右回り） | Bus | teal |
| 大長谷線（正間行き） | Bus | orange |
| 大長谷線（大長谷温泉行き） | Bus | orange |
| 大長谷線（八尾駅行き） | Bus | orange |
| 桐谷・茗ケ原線（1便） | Bus | pink |
| 桐谷・茗ケ原線（2便～4便） | Bus | pink |
| 保内線（冬季便） | Bus | orange |
| 八尾環状線（左回り） | Bus | teal |
| 八尾高校線（杉原公民館行き） | Bus | pink |
| 八尾高校線（八尾駅行き） | Bus | yellow |
| 八尾高校線（八尾高校行き） | Bus | yellow |
| 八尾高校線（八尾高校行き） | Bus | pink |
| 杉原線（ゆうゆう館循環）右回り | Bus | green |
| 杉原線（ゆうゆう館循環）左回り | Bus | green |
| 保内線（右回り） | Bus | orange |
| 保内線（左回り） | Bus | orange |
| 八尾中核線（KOKUSAIELECTRIC止まり） | Bus | teal |
| 八尾中核線（右回り） | Bus | teal |
| 八尾中核線（左回り） | Bus | teal |
| 八尾中核線（団地北経由KOKUSAIELECTRIC行き） | Bus | teal |
| 室牧線（細滝行き） | Bus | yellow |
| 室牧線（八尾駅行き） | Bus | yellow |
| 野積線（西松瀬行き） | Bus | teal |
| 野積線（八尾駅行き） | Bus | teal |
| 黒瀬谷線（宮越行き） | Bus | pink |
| 黒瀬谷線（八尾駅行き） | Bus | pink |
This feed has 153 stops.
List every stop
- 石戸
- 道畑
- 宮ノ下
- 水口
- 川倉口
- 川倉
- 広畑
- 西松瀬
- 東町
- 日東メディック前
- 上井田
- 喜楽鉱業前
- アクティブファーマ前
- ユースキン製薬前
- 河村産業所前
- 香栄興業前
- 杉田
- 滅鬼（西）
- 旧八尾中学校前
- 滅鬼
- 久婦須橋
- 奥田（東）
- 団地北
- 中井田
- 井田
- 井田
- 小泉定
- 福島第二
- 雇用促進住宅下
- 聞名寺下
- 村杉
- ゆうゆう館
- 葛坂橋
- 八十島
- 宮腰
- 布谷口
- 布谷
- 旧広畑小学校前
- 赤石
- 聞名寺前
- 川倉不動前
- 野積園前
- 大下
- 三ツ松口
- 三ツ松
- 島地
- 上高善寺
- 八尾スノーセンター前
- 茗ヶ原公民館前
- 八尾ふらっと館前
- 卯花地区センター前
- 公園前
- 公園前
- 眼鏡橋
- 黒瀬谷地区センター前
- 福島第三
- 高善寺公民館前
- アルビス八尾店前
- 上高善寺（西）
- 仁歩地区センター前
- 大長谷地区センター前
- おわら資料館前
- 野積地区センター前
- 室牧地区センター
- 大杉（西）
- 福島第三（北）
- 黒田公民館分館前
- 八尾大橋詰
- 梅苑町公民館前
- 鏡町
- 曳山展示館前
- 曳山展示館前
- 西新町
- 八尾駅
- 西新町口
- 上新町口
- 横町
- 今町
- 八尾小学校前
- 角間公民館前
- 梅谷橋
- 上笹原公民館前
- 掛畑
- 上掛畑
- 公民館前
- 上黒瀬
- 桐谷口
- 桐谷
- 杉原公民館前
- 大杉公民館前
- 大杉
- 杉田会館前
- 杉田東部公民館前
- 薄島
- 深谷北部
- 福島第一
- Aコープウインズ前
- 八尾高校前
- 小長谷
- 小長谷南口
- 下新村口
- 旧樫尾小学校前
- 樫尾
- 岩屋
- 本法寺下
- 高熊
- 十三石橋
- 高熊ふれあいセンター前
- 谷橋
- 谷内
- 室牧地区センター前
- 中村
- 上野
- 柚木
- 大開
- 杉田東
- 八尾行政サービスセンター前
- 西葛坂
- 三和
- 新名
- 天の平
- 乗嶺
- 下仁歩
- 中仁歩
- 上仁歩
- 入谷
- 正間
- 川戸
- 内名口
- 内名
- 田ノ頭
- 望岳台
- 西ヶ原
- 東原
- 庵谷
- 大長谷温泉
- 水谷
- SMK前
- 団地センター前
- ユニゾン前
- 富士通前
- 保内公民館前
- KOKUSAI ELECTRIC前
- 上新田グリーンタウン公園前
- 中新田公民館前
- 下新田公民館下交差点
- 三田消防器具庫前
- 奥田
- 翠尾
- 田中（西円寺前）
- 本郷公民館前
- 高善寺（保内小学校前）
- 八尾コミュニティセンター前
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
12 findings, ordered by severity.
Show every finding
- Error1 instance
The realtime feed's last update was about 3 hours old when sampled.
A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)
Validator rule: scorecard_rt_feed_lapsed
- Warning2518 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)
- Warning153 instances
153 of 153 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)
- Warning87 instances
87 of 87 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)
- Warning8 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- 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
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Validator rule: big_gap_in_service · 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 251 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.
Realtime reliability
The realtime feed responded on 100.0% of 1 checks, with 10856s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
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 67 / 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 50 / 100
- 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/toyama-yatsuo-community-bus/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.