Feed status · checked 2026-07-19
Akashi City Tako Bus (明石市たこバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Hyogo, 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
260 of 260 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
446 of 446 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 285 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 10750 instances (0 error, 10440 warning, 310 informational).
Service data covers the next 285 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
14 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (たこバス・1 西明石北ルート, たこバス・2 西明石南ルート, たこバスミニ・3 松陰ルート, たこバスミニ・4 大久保南ルート, たこバス・6 江井ケ島ルート, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- たこバス・1 西明石北ルート (pink)
- たこバス・10 青葉台ルート (teal)
- たこバス・11 清水ルート (pink)
- たこバス・12 西岡東ルート (teal)
- たこバスミニ・13 西岡西ルート (pink)
- たこバスミニ・14 清水西ルート (teal)
- たこバス・15 二見ルート (green)
- たこバス・2 西明石南ルート (green)
- たこバスミニ・3 松陰ルート (teal)
- たこバスミニ・4 大久保南ルート (yellow)
- たこバス・5 谷八木ルート (pink)
- たこバス・6 江井ケ島ルート (pink)
- たこバス・7 西江井ケ島ルート (green)
- たこバスミニ・8 金ヶ崎ルート (pink)
- たこバスミニ・9 錦が丘ルート (purple)
| Route | Type | Line color |
|---|---|---|
| たこバス・1 西明石北ルート | Bus | pink |
| たこバス・10 青葉台ルート | Bus | teal |
| たこバス・11 清水ルート | Bus | pink |
| たこバス・12 西岡東ルート | Bus | teal |
| たこバスミニ・13 西岡西ルート | Bus | pink |
| たこバスミニ・14 清水西ルート | Bus | teal |
| たこバス・15 二見ルート | Bus | green |
| たこバス・2 西明石南ルート | Bus | green |
| たこバスミニ・3 松陰ルート | Bus | teal |
| たこバスミニ・4 大久保南ルート | Bus | yellow |
| たこバス・5 谷八木ルート | Bus | pink |
| たこバス・6 江井ケ島ルート | Bus | pink |
| たこバス・7 西江井ケ島ルート | Bus | green |
| たこバスミニ・8 金ヶ崎ルート | Bus | pink |
| たこバスミニ・9 錦が丘ルート | Bus | purple |
This feed has 260 stops.
List every stop
- ＪＲ魚住駅北口
- ＪＲ魚住駅北口
- ＪＲ魚住駅北口
- ＪＲ魚住駅北口
- ふれあいの里魚住
- ふれあいの里魚住
- 長池
- 県営長坂寺鉄筋住宅
- 県営長坂寺鉄筋住宅
- 金ヶ崎文化センター
- 金崎神社
- 県営金ヶ崎鉄筋団地
- 金ヶ崎ケヤキ公園東
- 北浦
- 亥ノ池北
- 明石南高校北(野々池貯水池)
- 野木病院
- 錦が丘３丁目
- 錦が丘小学校
- 明石愛老園
- 長坂寺会館
- 山の谷池南
- 錦が丘１丁目
- 魚住市民センター
- 魚住市民センター
- 浜西南
- 東岡
- 明南町２丁目
- 明石清水郵便局
- 清水
- 浜西
- 安政池
- 清水団地
- 浜西東
- 魚住市民センター北
- 魚住市民センター北
- 野木病院東
- 長池中
- 明南町１丁目
- 青葉台口
- 青葉台
- 青葉台公園
- 長池北
- 魚住北公園
- 守池住宅
- 魚住小学校
- 魚住小学校南
- 国道南
- 清水ヶ丘
- 明石南高校南
- 明石ヶ丘北
- 明石ヶ丘南
- いずみが丘
- 魚住中学校
- 第２高層住宅
- 清水西口
- 清水西口
- 錦浦小学校
- 錦浦小学校
- 八幡橋
- 八幡橋
- ぼたん寺口
- ぼたん寺口
- 西畑
- 西畑
- 小久保６丁目
- 西台
- ふれあいプラザあかし西
- 寺ノ内
- 寺ノ内
- 二見市民センター
- 山陽東二見駅
- 山陽東二見駅
- 宮前
- 宮前
- 二見消防分署
- 二見消防分署
- 西二見
- 西二見
- イトーヨーカドー前(南口)
- イトーヨーカドー前(南口)
- 山陽西二見駅
- 鳥羽郵便局東
- イトーヨーカドー北
- イトーヨーカドー北
- イトーヨーカドー東
- イトーヨーカドー東
- 美里公園南
- 美里厚生館
- 満福寺
- 大見橋
- ひまわり診療所
- 二見農協前
- 二見農協北
- 山川橋
- トベラ公園前
- 山川西
- 山川北
- 山川公園
- 山川公園東
- 平池北
- ＪＲ土山駅南口
- ＪＲ土山駅南口
- 西二見岡の上
- 西二見岡の上
- 二見北小学校前
- 二見北小学校前
- 二見北郵便局前
- 二見北郵便局前
- 明石回生病院前
- 明石回生病院前
- 望海中学校南
- 望海中学校南
- 明石回生病院南
- 明石回生病院南
- 東二見池ノ上公園
- 東二見池ノ上公園
- 福里南
- 福里南
- 福里中
- 福里中
- 福里北
- 福里北
- 帝釋橋
- 帝釋橋
- 清水川右岸線緑地
- 仁十病院
- 清水ポプラ公園
- ディオ明石店前
- 西明石南町
- 西明石南町
- 中ノ又
- 中ノ又
- 東二見駅北住宅
- 東二見駅北住宅
- 山陽東二見駅北口
- 東二見車庫北
- 東二見車庫北
- 西部文化会館前
- 西部文化会館前
- 明石西高校前
- 明石西高校前
- 浄教寺前公園
- 浄教寺前公園
- 浄教寺北
- 浄教寺北
- 土山変電所前
- 土山変電所前
- 岡の下
- 岡の下
- 出の上
- ＪＲ西明石駅
- ＪＲ西明石駅
- 市営東二見住宅
- 瀬戸川緑道東
- 中畑
- 明石こころのホスピタル
- 山陽藤江駅東
- 藤が丘公民館前
- 山陽藤江駅
- 藤江病院前
- 藤江神社前
- 藤江川南
- 藤江川北
- 卸売市場南
- 卸売市場南
- 中尾
- 甲池公園
- 卸売市場東
- 卸売市場東
- カゲユ池古墳前
- 卸売市場北
- ＪＲ大久保駅南口
- ゆりのき通２丁目
- ゆりのき通２丁目
- 大久保南小学校
- 大久保南小学校
- 大久保中学校南
- 大久保中学校南
- 下山崎
- 下山崎
- 松陰保育所前
- 松陰保育所前
- 鳥羽浄水場南
- 鳥羽浄水場南
- 堀町
- 堀町
- 西開地
- 松陰山手
- 松陰厚生館
- 松陰公園
- マルアイ前
- 憩の家前
- 大久保町公民館前
- 住吉神社
- 谷八木２号公園
- 鳥羽宮東
- 谷八木１号公園
- 焼野池
- 谷八木福井谷公園
- 道屋
- 谷八木堂田公園
- 山陽中八木駅北
- 明石医療センター
- 明石医療センター
- 山陽中八木駅
- 谷八木
- 谷八木
- 谷八木橋
- 谷八木橋
- 沢野南
- 今崎野
- 今崎野
- 谷八木小学校
- 八木遺跡公園
- 八木会館北
- 山陽中八木駅西
- 城ケ谷
- 家ノ北
- 大久保浄化センター南
- 夜間休日応急診療所
- ゆりのき通２丁目北
- 沢野
- 福田
- 江井島皿池西
- 大西脳神経外科病院
- 谷池西
- 山陽江井ヶ島駅
- 東江井
- 江井島サービスコーナー北
- 江井島港
- 江井島港
- ながさわ江井島酒館
- 西江井
- 鳥羽新池公園
- 江井ヶ島綜合市場
- 日工西
- 日工前
- 西八木厚生館
- ＪＲ魚住駅南口
- ＪＲ魚住駅南口
- 西部市民会館北
- 西部市民会館北
- 住吉１丁目
- 住吉１丁目
- 山陽魚住駅
- 山陽西江井ヶ島駅
- 森西
- 野々池中学校
- 江井島病院
- and 10 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 76.4 | first check |
| 2026-07-19 | 76.4 | 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
8 findings, ordered by severity.
Show every finding
- Warning10409 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)
- Warning446 instances
446 of 446 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)
- Warning260 instances
260 of 260 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)
- Warning30 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)
- Info309 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.)
Validator rule: trip_headsign_matches_intermediate_stop · 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 285 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 285 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 80 / 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/akashi-city-tako-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.