Feed status · checked 2026-07-19
Takashima City Community Bus (高島市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Shiga, 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
305 of 305 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
181 of 181 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 8 kinds of issue across 4339 instances (0 error, 4337 warning, 2 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
5 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.
- マキノ高原線 (green)
- 国境線 (teal)
- マキノ北西部線 (orange)
- 総合運動公園線 (yellow)
- 船木線 (red)
- 高島安曇川線 (orange)
- 安曇川中央循環線 (white)
- 下古賀循環線 (white)
- 新旭南循環線 (purple)
- 針畑線 (red)
- 上村能家線 (brown)
- 横谷木地山線 (purple)
- 柏宮前坊線 (green)
- 畑線 (white)
- 武曽・横山線 (white)
- 新旭西循環線 (green)
- 新旭東循環線 (teal)
- 森線 (red)
| Route | Type | Line color |
|---|---|---|
| マキノ高原線 | Bus | green |
| 国境線 | Bus | teal |
| マキノ北西部線 | Bus | orange |
| 総合運動公園線 | Bus | yellow |
| 船木線 | Bus | red |
| 高島安曇川線 | Bus | orange |
| 安曇川中央循環線 | Bus | white |
| 下古賀循環線 | Bus | white |
| 新旭南循環線 | Bus | purple |
| 針畑線 | Bus | red |
| 上村能家線 | Bus | brown |
| 横谷木地山線 | Bus | purple |
| 柏宮前坊線 | Bus | green |
| 畑線 | Bus | white |
| 武曽・横山線 | Bus | white |
| 新旭西循環線 | Bus | green |
| 新旭東循環線 | Bus | teal |
| 森線 | Bus | red |
This feed has 305 stops.
List every stop
- 久保所
- 黒谷
- 桑ノ橋
- 桑原
- 桑原橋
- 小荒路
- 小荒路
- 木津
- 木津浜
- 小川戸谷橋
- 小川針畑橋
- 安養寺
- 安養寺
- 小川松原橋
- 国道西浜
- 国道西浜
- 腰越
- 湖西平前
- 湖西平前
- こどもの国前
- 小中
- 坂の下
- 酒波
- 安養寺西
- 沢
- 沢南口
- ＪＡ西びわこ前
- ＪＡマキノ町前
- ＪＡマキノ町前
- 鹿ケ瀬
- 鹿ケ瀬道
- 地子原
- 下市
- 下市場
- 下小川
- 伊井
- 下開田
- 下柏
- 下古賀
- 下古賀東
- 下立戸
- 下出
- 下拝戸
- 霜降
- 下古川
- 家本原
- 下古屋
- じゃがいもの家
- 市役所前
- 宿鴨
- 消防本部前
- 青冷寺
- 青冷寺
- 白谷
- 白谷長寿苑
- 新旭駅
- 新旭養護学校前
- 五十川
- 五十川
- 新庄（新）
- 新庄大善寺前
- 新庄本町
- 新田
- 新中野団地前
- 新中野団地前
- 新保
- 新保
- 新保南
- 新町
- 世代交流センター前
- 田井
- 五十川住宅前
- 高木浜二丁目
- 高木浜二丁目
- 高島海洋センター前
- 高島高校前
- 高島支所前
- 高島市民病院
- 高島中学校前
- 高島本町
- 田谷
- 田谷
- 路原
- 五十川神社前
- 五十川神社前
- 中学校前
- 土に学ぶ里研修センター
- 出鴨
- 寺久保
- 藤樹記念館前
- 藤樹書院前
- 床鍋橋
- 図書館前
- 栃生口
- 栃生右淵
- 伊黒
- 伊黒
- 富坂口
- 中庄
- 中ノ町
- 中溝
- 西小学校前
- 西浜
- 西浜南
- 西村井
- 西万木
- 西万木今宮神社前
- 池原
- 能家
- 能家口
- 能家分校前
- 野街道
- 野口
- 野田
- 野田北
- 野田口
- 野田口
- 拝戸団地前
- 拝戸団地前
- 箱館山
- 石庭
- アイリッシュパーク前
- 畑
- 針江小池
- 針江公民館前
- 針畑休憩所前
- 東鴨
- 東鴨
- 東新町
- 東新町
- 日爪
- 日吉二宮神社前
- 平井
- 犬丸
- 打明
- 蛭口
- 弘川
- 弘川口
- 弘川高田
- 深溝
- 藤江
- 藤江
- プラント高島店
- 古川
- 井ノ口
- 井ノ口
- 古屋郵便局前
- ふれあいセンター前
- ふれあいセンター前
- 平和堂あどがわ店
- 平ヶ崎
- 平ヶ崎北
- 平良集会所前
- 平良分校前
- 坊村
- 坊村
- 細川
- ホリゾン前
- マキノ駅
- マキノ高原温泉さらさ
- マキノ高原民宿村
- マキノ支所前
- マキノ支所前
- マキノ白谷温泉
- マキノピックランド
- マキノ病院前
- 水尾
- 水尾
- 水鳥観察センター前
- 今市・辻沢
- 今市・辻沢
- 三谷
- 三谷口
- 道の駅マキノ追坂峠
- 南桑原
- 南小学校前
- 南新保口
- 南深清水
- 南船木交差点
- 南船木西口
- 南船木西口
- 南平良
- 今在家
- 南牧野
- 宮野
- 宮前坊上
- 宮前坊下
- 向所
- 武曽
- 武曽口
- 村井
- 森
- もりっこ前
- 今津北小学校前
- 山中
- 藺生東
- 横江
- 横江
- 横江浜
- 横谷
- 横谷口
- 横山
- 米井
- 米井
- リバーサイド
- リバーサイド
- 藁園四の坪
- 今津西町
- 今津西町
- 藁園神社前
- 藁園ふれあい会館前
- 藁園六石丸
- 岩瀬
- 上野
- 麻生
- 上ノ山
- 上ノ山
- 梅ノ木
- 梅原
- 梅原北
- 浦
- 運動公園
- 運動公園
- 家一
- 生杉
- 近江今津駅
- 近江桂
- 麻生口
- 近江高島駅
- 近江中庄駅
- 大床
- 太田蒲生
- 太田北町
- 大田神社前
- 太田中川原
- 太田日光苑
- 太田東出口
- 大沼
- 安曇川駅
- 岡
- 岡
- 岡会議所前
- 岡会議所前
- 岡バイパス交差点
- 岡バイパス交差点
- 小川口
- 小川口
- 音羽
- 音羽上
- 小入谷
- and 55 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 | 69.1 | first check |
| 2026-07-19 | 69.1 | 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
11 findings, ordered by severity.
Show every finding
- Warning4290 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)
- Warning305 instances
305 of 305 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)
- Warning181 instances
181 of 181 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)
- Warning20 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 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)
- Warning5 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)
- Warning2 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)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Validator rule: stops_match_shape_out_of_order · 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 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 64 / 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/takashima-city-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.