Feed status · checked 2026-07-18
Shimada City Community Bus (島田市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Shizuoka, 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 41 minutes ago; last changed 41 minutes ago.
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
455 of 455 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
136 of 136 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 256 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 4 kinds of issue across 4485 instances (0 error, 4480 warning, 5 informational).
Service data covers the next 256 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.
- 伊久身線 (blue)
- 伊久身線（向谷系統） (blue)
- 川根温泉線 (teal)
- 相賀線 (green)
- 大津線 (orange)
- 湯日線 (red)
- 田代の郷温泉線 (pink)
- 六合南線 (black)
- 島田駅東線 (green)
- 大代線 (brown)
- 菊川神谷城線 (red)
- 金谷循環線 (red)
- 笹間渡笹間線 (red)
| Route | Type | Line color |
|---|---|---|
| 伊久身線 | Bus | blue |
| 伊久身線（向谷系統） | Bus | blue |
| 川根温泉線 | Bus | teal |
| 相賀線 | Bus | green |
| 大津線 | Bus | orange |
| 湯日線 | Bus | red |
| 田代の郷温泉線 | Bus | pink |
| 六合南線 | Bus | black |
| 島田駅東線 | Bus | green |
| 大代線 | Bus | brown |
| 菊川神谷城線 | Bus | red |
| 金谷循環線 | Bus | red |
| 笹間渡笹間線 | Bus | red |
This feed has 455 stops.
List every stop
- 幸町
- 幸町
- 幸町
- 幸町
- 天徳寺
- 大草上
- 大草上
- 大草公会堂
- 大草公会堂
- 慶寿寺入口
- 大草住宅
- 大草住宅
- 尾川
- 尾川
- ぎんもくせい
- ぎんもくせい
- 永福荘
- 永福荘
- 落合上
- 伊久美小学校
- 伊久美小学校
- 大津小学校
- 落合
- 落合
- 上野田公会堂
- 上野田公会堂
- 上野田
- 上野田
- 島田市立総合医療センター
- 元島田
- 元島田
- 保健福祉センター入口
- 保健福祉センター入口
- 島田年金事務所
- 島田年金事務所
- 島田年金事務所
- 島田年金事務所
- ぴ～ファイブ西
- ぴ～ファイブ西
- ぴ～ファイブ西
- ぴ～ファイブ西
- 本通三丁目東
- 本通三丁目東
- 本通三丁目東
- 本通三丁目東
- 小川
- 小川
- 市役所西
- 市役所西
- 市役所西
- 市役所西
- 島田郵便局
- 島田郵便局
- 島田郵便局
- 島田郵便局
- 第二中学校
- 中央公園・ばらの丘
- 中央公園・ばらの丘
- ばらの丘一丁目
- ばらの丘二丁目
- 落合春日神社
- 本村
- 原の平西
- 原の平
- やまびこ
- やまびこ
- ふれあいセンター
- 下湯日西
- 下湯日西
- 下湯日
- 下湯日
- 沼伏西
- 沼伏西
- 沼伏
- 沼伏
- 沼伏東
- 沼伏東
- 色尾西
- 色尾西
- 月坂一丁目西
- 月坂一丁目西
- 月坂一丁目
- 月坂一丁目
- 月坂二丁目
- 月坂二丁目
- 犬間橋
- 犬間橋
- 初倉消防署
- 初倉消防署
- 色尾
- 色尾
- 旧初上
- 旧初上
- 旧初
- 旧初
- 旧初下
- 旧初下
- 谷口辻
- 谷口辻
- 谷口下
- 谷口下
- 谷口橋
- 谷口橋
- 道悦島
- 道悦島
- 六合中学校
- やまゆり
- やまゆり
- 六合消防署
- 六合消防署
- 六合駅
- 六合駅
- 島田工業高校
- 島田工業高校
- 栃山
- 栃山橋
- 栃山橋
- 御仮屋
- 御仮屋
- 本通七丁目東
- 本通七丁目東
- 島田商業高校
- 島田商業高校
- 本通六丁目
- 本通六丁目
- 本通五丁目
- 本通五丁目
- 長島
- 長島
- 伊太和里の湯
- 田代環境プラザ
- 玉雲寺西
- 上伊太公会堂
- 上伊太下
- 小山田橋
- 伊太団地
- 伊太団地南
- 伊太団地南
- 島田樟誠高校
- 向谷元町
- 川口東
- 川口東
- 道悦四丁目
- 道悦四丁目
- 六合小学校
- 六合小学校
- 細島橋
- 細島橋
- 北島公園入口
- 北島東公園入口
- 陣屋橋西
- 全仲寺東
- 東町四丁目
- さくら入口
- 六合東小学校東
- 伊久身幼稚園上
- 伊久身幼稚園上
- 六合東小学校南
- 細島
- 消防団詰所北
- 島田駅南口
- 島田南幼稚園
- 島田南幼稚園
- 南町公会堂
- 南町公会堂
- 宝来町
- 宝来町
- 旭町西
- 旭町西
- 旭町中
- 旭町中
- 旭町東
- 旭町東
- 川口
- 川口
- 御仮屋南
- 御仮屋南
- 八六橋
- 八六橋
- 千歳橋
- 千歳橋
- 元島田公園東
- 元島田公園東
- 元島田西
- 元島田西
- 本通一丁目
- 栗島公民館
- 岡穂平公民館
- 五和製茶前
- 宮ノ上
- 山の家
- 山の家
- 御堂沢
- 四分一
- 童子沢入口
- なでしこ公民館
- 影島
- 向川公民館
- 堤間団地東
- 堤間団地東
- KADODE OOIGAWA
- 牛尾北
- 横岡新田
- 島田金谷インター入口北
- 北鵜網
- 北鵜網
- 金谷北地域交流センター
- 夢づくり会館
- エコトープ前
- エコトープ前
- 日切
- 金谷消防署
- 金谷消防署
- 番生寺
- 番生寺
- 番生寺会館前
- 番生寺会館前
- 金谷中入口西
- 金谷中入口西
- 金谷中入口
- 金谷中入口
- 金谷庁舎前
- 鵜網
- 鵜網
- 栄代橋西
- 栄代橋西
- 栄町公会堂前
- 栄町
- 中町
- 中町
- 本町
- 本町
- 田町
- 金谷駅前
- ふじのくに茶の都ミュージアム
- 猪土居北
- 金谷茶業研究拠点
- 金谷茶業研究拠点
- 神座宮前
- 神座宮前
- 猪土居
- 猪土居
- 諏訪原城跡
- 菊翠茶農協前
- 菊川の里会館
- 松島
- 神谷城保育園前
- 神谷城西公民館前
- 浅川橋南
- 石神
- and 205 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
6 findings, ordered by severity.
Show every finding
- Warning4416 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)
- Warning455 instances
455 of 455 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)
- Warning136 instances
136 of 136 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)
- Warning64 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)
- Info3 instances
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)
- Info2 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: platform_without_parent_station · 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 256 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 256 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 83 / 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/shimada-community-bus/2026-07-18.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-18. 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.