Feed status · checked 2026-09-05
Tsuruga City Community Bus (敦賀市コミュニティバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Fukui, 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.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
317 of 317 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
183 of 183 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 317 of 317 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 183 of 183 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 207 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 4524 instances (0 error, 4522 warning, 2 informational).
Service data covers the next 207 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
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1 東浦線（予約便）, 1 東浦線, 3 中央線, 4 金山線, 8 山公文名線(粟中先回り), 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.
This feed has 317 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 東浦線（予約便） (orange)
- 1 東浦線 (orange)
- 2 常宮線 (green)
- 3 中央線 (pink)
- 4 金山線 (teal)
- 5 松原線 (blue)
- 6 中郷木崎線 (yellow)
- 7 粟野沓見線 (yellow)
- 8 山公文名線(粟中先回り) (brown)
- 8 山公文名線(公文名先回り) (brown)
- 9 温泉線（リラ・ポート先回り） (gray)
- 9 温泉線（泉ヶ丘先回り） (gray)
- 10 東郷線（予約便） (teal)
- 11 愛発線（予約便） (purple)
- 11 愛発線 (purple)
- 12 ぐるっと敦賀周遊バス 観光ルート (red)
- 12 ぐるっと敦賀周遊バス ショッピングルート (red)
| Route | Type | Line color |
|---|---|---|
| 1 東浦線（予約便） | Bus | orange |
| 1 東浦線 | Bus | orange |
| 2 常宮線 | Bus | green |
| 3 中央線 | Bus | pink |
| 4 金山線 | Bus | teal |
| 5 松原線 | Bus | blue |
| 6 中郷木崎線 | Bus | yellow |
| 7 粟野沓見線 | Bus | yellow |
| 8 山公文名線(粟中先回り) | Bus | brown |
| 8 山公文名線(公文名先回り) | Bus | brown |
| 9 温泉線（リラ・ポート先回り） | Bus | gray |
| 9 温泉線（泉ヶ丘先回り） | Bus | gray |
| 10 東郷線（予約便） | Bus | teal |
| 11 愛発線（予約便） | Bus | purple |
| 11 愛発線 | Bus | purple |
| 12 ぐるっと敦賀周遊バス 観光ルート | Bus | red |
| 12 ぐるっと敦賀周遊バス ショッピングルート | Bus | red |
List every stop
- 長沢
- 長沢
- 卸売市場前
- 卸売市場前
- 古田刈
- 古田刈
- 岡山町
- 岡山町
- 堂橋
- 堂
- 堂
- 工業高校前
- 工業高校前
- 山泉
- 和久野
- 和久野
- 下公文名
- 赤崎
- 西公文名
- 西公文名
- 櫛林
- 櫛林
- 萩野町
- 若葉町１丁目
- 若葉町１丁目
- 木崎
- 木崎
- 新松島
- 新松島
- 古田刈中
- 古田刈中
- 山泉中
- 山泉台
- 山泉台
- 東公文名
- 江良
- 小学校口
- 市野々２丁目
- 市野々２丁目
- 西櫛林
- 西櫛林
- 北金山
- 北金山
- 南沓見
- 南沓見
- 呉竹町１丁目
- 呉竹町１丁目
- 呉竹町２丁目
- 呉竹町２丁目
- 長谷
- やまびこ園
- 粟野スポーツセンター
- 五幡
- 五幡
- 御名
- 上御名
- 上御名
- 山入口
- エネ研
- 山
- 山出口
- 上みどりヶ丘
- みどりヶ丘町
- みどりヶ丘町口
- 上公文名
- 上公文名
- 挙野
- 公文名
- 公文名
- 公文名口
- 公文名口
- 和久野口
- 清水町１丁目
- 清水町１丁目
- 舞崎町
- 舞崎町
- 高野口
- 中
- 吉河（敦賀温泉病院）
- 泉ヶ丘病院
- 泉ヶ丘
- 阿曽中
- 泉ヶ丘南口
- 谷入口
- 高野
- リラ・ポート
- 泉ヶ丘口
- 井川（集落センター）
- 三和
- 三和
- 大蔵
- 大蔵
- 中池見口（藤ヶ丘）
- 余座
- 阿曽
- 大蔵中
- 東郷公民館
- 谷口
- 深山寺
- 樫曲
- 樫曲
- 越坂
- 池河内口
- 獺河内
- 田尻
- 葉原下
- 杉津口
- 葉原
- 新保
- 新保中
- 岡山２丁目
- 岡山２丁目
- 道口
- 道口
- 鳩原
- 鳩原
- 小河
- 小河出口
- 小河口
- 小河口
- 市橋
- 市橋
- 杉津
- 疋田
- 疋田
- 疋田下
- 舟川の里
- 疋田上
- 新疋田駅（追分）
- 駄口
- 駄口下
- 奥野中
- 奥野
- 奥野
- 曽々木下
- 横浜
- 曽々木上
- 曽々木
- 曽々木
- 奥麻生
- 新道
- 新道野
- 新麻生口
- 新麻生口
- 宮前橋
- 刀根
- 杉箸口
- 杉箸
- 南大比田
- 敦賀駅
- 敦賀駅
- 敦賀駅
- 敦賀駅
- 敦賀駅
- 氣比神宮
- 博物館通り
- 金崎宮
- 赤レンガ倉庫
- 松原海岸
- 水戸烈士記念館
- お魚通り
- 大鳥居
- 日本海さかな街
- 大比田
- ニューサンピア敦賀
- 小牧かまぼこ
- 元比田
- 白木
- 神楽町
- 神楽町
- 神楽２丁目
- 神楽２丁目
- 中央町２丁目
- 中央町２丁目
- 市立病院前
- 市立病院前
- 新道中
- リラ・グリーン
- ドン・キホーテ
- 金ヶ崎緑地（ムゼウム）
- 市民文化センター
- 松島口
- 松島口
- 沓
- 松原公園口
- 松原公園口
- 手の浦口
- 松原町
- 松原町
- 白銀町
- 白銀町
- 白銀町
- 白銀町
- 気比の松原
- 気比の松原
- 手の浦
- 色ヶ浜
- 体育館前
- 体育館前
- 松葉町
- 西浦学校前
- 浦底
- 花城
- 花城
- 県水産試験場前
- 二村
- 本町２丁目
- 本町２丁目
- 原電前
- 名子
- 縄間
- 立石
- プラザ萬象前
- プラザ萬象前
- 常宮
- あいあいプラザ
- 開団地前
- 開団地前
- 三島団地前
- 三島団地前
- 農協前
- 農協前
- 昭和町
- 昭和町
- 市役所前
- 市役所前
- 市役所前
- 健康センターはぴふる前
- 健康センターはぴふる前
- 北木崎
- 北木崎
- 南平和町
- 南平和町
- 西木崎
- 西木崎
- 運動公園東口
- 運動公園東口
- 運動公園西口
- 運動公園西口
- 原電訓練センター
- 気比神宮前
- 気比神宮前
- 沓見
- 敦賀高校前
- 敦賀高校前
- 平和町
- 三島２丁目
- 三島２丁目
- 合同庁舎
- 合同庁舎
- and 67 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
8 findings, ordered by severity.
Show every finding
- Warning4471 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning317 instances
317 of 317 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning183 instances
183 of 183 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning49 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: missing_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.)
Finding code: 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
One requirement remains for this feed to earn 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 207 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 207 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 78 / 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/tsuruga-city-bus/2026-09-05.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-09-05. 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.