Feed status · checked 2026-07-23
いなべ市福祉バス
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Mie, 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
438 of 438 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
115 of 115 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 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
- 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 3 kinds of issue across 3211 instances (0 error, 3209 warning, 2 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
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 | red (no shape in feed) |
| アイバス 市之原線 | Bus | teal (no shape in feed) |
| アイバス 平古線 | Bus | gray (no shape in feed) |
| アイバス 十社線 | Bus | gray (no shape in feed) |
| アイバス 治田線 | Bus | orange (no shape in feed) |
| アイバス 山郷線 | Bus | pink (no shape in feed) |
| アイバス 貝野線 | Bus | blue (no shape in feed) |
| アイバス 中里線 | Bus | orange (no shape in feed) |
| アイバス 立田線 | Bus | blue (no shape in feed) |
| アイバス 坂本線 | Bus | gray (no shape in feed) |
| アイバス 石榑線 | Bus | teal (no shape in feed) |
| アイバス 三里丹生川線 | Bus | red (no shape in feed) |
| アイバス 梅戸井線 | Bus | gray (no shape in feed) |
This feed has 438 stops.
List every stop
- 市之原平
- 市之原農村公園
- 市之原農村公園
- 市之原公民館
- 市之原公民館
- 坂東新田
- 坂東新田
- 上笠田宇野公民館
- 上笠田宇野公民館
- 上笠田東
- 上笠田東
- 笠田新田観音堂
- 笠田新田観音堂
- 員弁西小学校
- 員弁西小学校
- 下笠田
- 下笠田
- 楚原
- 楚原
- 楚原駅
- 御薗
- 御薗
- みその団地
- みその団地
- 平古集会所
- 平古南
- 平古南
- 畑新田
- 畑新田
- 松之木西
- 松之木西
- 岡
- 暮明口
- 松之木南
- 松之木南
- 長宮
- 長宮
- 旧ＪＡ大泉支店
- 旧ＪＡ大泉支店
- 大泉駅
- 東一色
- 東一色
- 大泉
- 大泉
- 西方集落センター
- 西方集落センター
- 北金井東
- 北金井東
- 了雲寺
- 了雲寺
- 北金井北
- 北金井北
- 大泉新田西
- 大泉新田西
- 員弁郵便局
- 員弁郵便局
- 楚原北
- 楚原北
- ヨシヅヤ
- 小笠原内科
- わたなべ整形
- 畑新田八幡社
- 員弁体育館
- いなべ公園口
- 員弁庁舎
- 川原
- 川原
- 川原分校跡
- 川原分校跡
- 御母堂
- 御母堂
- 川原口
- 川原口
- 田辺宮前
- 田辺宮前
- 田辺
- 田辺
- 二之瀬北
- 二之瀬
- 塩崎
- 塩崎
- 畑毛北
- 畑毛北
- 畑毛
- 畑毛
- 向平公民館
- 向平公民館
- 下平
- 下平
- 下平口
- 下平口
- 飯倉
- 飯倉
- 北勢中学校
- 北勢中学校
- 阿下喜北町
- マックスバリュ
- 新町
- 宮之段
- 新町上
- 長頭子
- 無正野
- 奥村
- 奥村
- 奥村東
- 奥村東
- 奥村口
- 奥村口
- 麓村中
- 麓村中
- 中山
- 治田こども園
- 治田こども園
- ＪＡ治田支店
- ＪＡ治田支店
- 垣内
- 垣内
- 一之坂
- 一之坂
- 別名
- 別名
- 東村東
- 東村東
- 新貝
- 新貝
- 日下病院
- 日下病院
- 阿下喜口
- 阿下喜口
- 小山
- 小山
- 六石
- 六石
- 麻生田
- 麻生田
- 麻生田駅
- ＪＡ山郷支店
- ＪＡ山郷支店
- 麻生田交差点北
- 麻生田交差点北
- 楚里
- 其原グラウンド
- 山郷小学校
- 平野新田
- 平野地蔵
- 皷
- 北中津原
- 行順寺
- 南中津原
- 其原神社
- 其原
- 昭電自治会館
- 山郷こども園
- 藤沢
- 藤沢
- 貝野神社
- 東貝野倉庫
- 西貝野
- 西貝野
- 伊勢治田駅
- 西貝野倉庫
- 西貝野倉庫
- 小原一色口
- 小原一色口
- 小原一色
- 翠明院
- かなえ
- かなえ
- 小豆尾
- 小豆尾
- 米野
- 米野
- 米野口
- 米野口
- 上之山田
- 上之山田
- 上相場
- 上相場
- 浜相場
- 浜相場
- 旧JA中里支店（郷土資料館前）
- 旧JA中里支店（郷土資料館前）
- 長尾
- 長尾
- 日内
- 日内
- 東日内
- 東日内
- 日内口
- 日内口
- 下相場
- 川合
- 川合
- 中川合
- 中川合
- 下川合
- 下川合
- 下川合口
- 下川合口
- 下野尻
- 下野尻
- マックスバリュ東
- マックスバリュ東
- 宮前
- 宮前
- 商工会館
- 商工会館
- 古田
- 古田
- 古田集会所
- 古田集会所
- 古田口
- 古田口
- 旧立田小学校
- 旧立田小学校
- 立田郵便局
- 立田郵便局
- 篠立
- 篠立
- 明行寺
- 明行寺
- 篠立口
- 篠立口
- 立田公園
- 立田公園
- 篠立きのこ園
- 舞谷野
- 舞谷野
- 冷川
- 冷川
- 平野
- 平野
- 山口
- 山口
- 山口東
- 山口東
- 本郷社
- 本郷社
- 本郷
- 本郷
- 東本郷
- 東本郷
- 藤原郵便局
- 藤原郵便局
- 藤原文化センター
- ＪＡ白瀬支店
- ＪＡ白瀬支店
- 市場
- 市場
- 藤原中学校
- and 188 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
5 findings, ordered by severity.
Show every finding
- Warning3192 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)
- Warning438 instances
438 of 438 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)
- Warning115 instances
115 of 115 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)
- Warning17 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)
- 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)
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.
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 86 / 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 60 / 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/inabecity-fukushibus/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.