Feed status · checked 2026-07-18
Hakusan City Community Bus (白山市コミュニティバス「めぐーる」)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Ishikawa, 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 3 hours ago; last changed 3 hours 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
335 of 335 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
208 of 208 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 240 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 17569 instances (0 error, 17569 warning, 0 informational).
Service data covers the next 240 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.
- めぐーる つるぎ病院ルート (brown)
- めぐーる上野・阿手ルート (pink)
- めぐーる中央病院ルート (brown)
- めぐーる北ルート (red)
- めぐーる北循環ルート (pink)
- めぐーる北西ルート (purple)
- めぐーる南ルート (yellow)
- めぐーる南循環ルート (pink)
- めぐーる南西ルート (green)
- めぐーる尾口ルート (orange)
- めぐーる東ルート (teal)
- めぐーる松任美川ルート (black)
- めぐーる河内ルート（千丈温泉） (teal)
- めぐーる河内ルート（吉岡） (teal)
- めぐーる白山ルート (green)
- めぐーる美川・湊ルート (gray)
- めぐーる舘畑ルート (blue)
- めぐーる蔵山・林ルート (teal)
- めぐーる西ルート (teal)
- めぐーる診療所・温泉ルート（吉野） (green)
- めぐーる診療所・温泉ルート（白山下） (green)
| Route | Type | Line color |
|---|---|---|
| めぐーる つるぎ病院ルート | Bus | brown |
| めぐーる上野・阿手ルート | Bus | pink |
| めぐーる中央病院ルート | Bus | brown |
| めぐーる北ルート | Bus | red |
| めぐーる北循環ルート | Bus | pink |
| めぐーる北西ルート | Bus | purple |
| めぐーる南ルート | Bus | yellow |
| めぐーる南循環ルート | Bus | pink |
| めぐーる南西ルート | Bus | green |
| めぐーる尾口ルート | Bus | orange |
| めぐーる東ルート | Bus | teal |
| めぐーる松任美川ルート | Bus | black |
| めぐーる河内ルート（千丈温泉） | Bus | teal |
| めぐーる河内ルート（吉岡） | Bus | teal |
| めぐーる白山ルート | Bus | green |
| めぐーる美川・湊ルート | Bus | gray |
| めぐーる舘畑ルート | Bus | blue |
| めぐーる蔵山・林ルート | Bus | teal |
| めぐーる西ルート | Bus | teal |
| めぐーる診療所・温泉ルート（吉野） | Bus | green |
| めぐーる診療所・温泉ルート（白山下） | Bus | green |
This feed has 335 stops.
List every stop
- 黒瀬
- 七郎
- 宮保コミュニティセンター
- 法仏
- 千代野南
- 茶屋一丁目
- 宮丸
- 宮丸
- 道の駅めぐみ白山
- 上小川
- 小川
- 宮永新
- 海浜温泉
- 浜相川
- 相川新
- 中相川
- 東相川
- 蕪城五丁目
- 蕪城団地
- 新成一丁目
- 安田
- 茶屋
- 宮永
- 成3区
- 北安田
- ファーマーズＡコープ北安田店前
- 千代野小学校前
- 千代野第5集会所前
- 蕪城三丁目
- 北成区
- 相木団地
- 北相木6区
- 相木南
- 福増
- 松任駅北口
- 北相木5区
- 新田西
- 新田南
- 八ツ矢
- 南八ツ矢
- 布市
- 徳丸
- 村井団地
- 南松任
- あさひ荘苑
- マルエー松任店
- 浜町
- 美川中学校前
- 蓮池町
- 鹿島町西
- 北國新聞白山印刷センター
- 鹿島町東
- 鹿島平
- 石立
- 松本
- 五歩市
- ファミリーマートＡコープ加賀野店前
- 上河原・宮原
- 宮保
- 米永
- 米永新区
- 中町ほほえみ館
- 美川大橋詰
- 湊町
- 呉竹文庫前
- 大阪屋ショップ松任店
- 湊町3区
- 湊児童館前
- 湊小学校前
- 湊町6区
- 湊町7区
- 湊健康増進センター前
- 湊町十区区民会館前
- 湊町10区
- 小舞子駅
- 湊町5区
- 県道八ツ矢
- 県道八ツ矢
- こども広場前
- 美川大橋詰北
- 永代町
- 美川小学校前
- 和波町
- 和波町東地区公民館前
- 平加町
- 石川ルーツ交流館前
- 本吉町
- 松任駅
- 長屋町
- 末正町
- 水島公民館
- 源兵島
- 福留西
- 下柏野
- 荒屋柏野
- 上柏野
- 一ノ宮コミュニティセンター
- 三宮町
- 学習センター
- 学習センター
- 八幡町
- 石川県ふれあい昆虫館前
- 朝日公民館
- 金劔宮前
- 鶴来支所前
- 鶴来駅前
- つるぎ病院前
- レッツ
- 大国町
- 本鶴来
- 中町
- 緑風台
- 新村病院
- 鶴来高校・ほうらい荘前
- 白山警察署鶴来庁舎前
- 白山町中
- 白山町
- 一の宮
- 今町
- 白山青年の家前
- 鶴来本町四丁目
- 明島台
- 松任高校前
- 松任高校前
- 春の木
- 中村
- 西の村
- 上森島
- 下森島
- 名鉄森島台
- 大竹
- 明法島
- 日向団地
- 行町
- 合同庁舎
- 合同庁舎
- 深瀬新町
- 深瀬新町
- 安養寺
- 富光寺住宅
- 富光寺東
- 柴木
- 新荒屋
- 大阪屋ショップ鶴来店前
- 月橋
- 月橋
- 小柳新
- 日御子団地
- ラスパ白山
- 日御子
- 部入道
- 池田病院
- 熱野
- 曽谷
- 陽羽里駅
- 曽谷東
- 坂尻
- 林コミュニティセンター
- 荒屋
- 市役所
- 知気寺
- 明光四丁目
- 明光一丁目
- 小柳
- 広瀬
- 口直海
- 河内小学校前
- 奥池
- 久保
- 吹上
- 公立松任石川中央病院
- 板尾
- 中金間
- 下折
- 千丈温泉
- ふじが丘
- 下福岡
- かわちこども園
- 上福岡
- きりの里
- 江津
- イオン松任
- 吉岡
- アルビス北安田店前
- 鳥越中学校
- 阿手
- 数瀬
- 三ツ瀬
- 左礫
- 渡津
- 神子清水
- 杉森
- 白山警察署
- 別宮出
- 別宮
- 上出合
- 下出合
- 三坂
- 上野
- 鳥越小学校前
- とりごえ保育園
- 釜清水
- ＪＡ白山手取支店
- 広小路
- 広小路
- 黄門橋
- 中島
- 南白山町
- 石川県浄水場口
- 鶴来本町
- 河原山
- 野々市駅北口
- 上吉谷
- 下吉谷
- 吉野谷診療所
- 横江東
- 浜八田
- 三ツ屋野
- 白山下
- 瀬波
- 下吉野
- 味智の郷
- 上吉野
- 西佐良
- 佐良
- 中宮温泉
- 白山一里野
- 横江
- 尾添
- 白山中宮
- 荒谷
- 瀬戸
- 瀬女
- 沢野
- 女原
- 東二口
- 仏師ケ野
- 尾口市民サービスセンター前
- 白鷺団地
- 瀬戸野
- 木滑新
- 上木滑
- 下木滑
- 市原
- 吉野保育所
- 白嶺小中学校
- 菅波
- パール団地
- 長池
- 清金団地
- and 85 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
- Warning17490 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)
- Warning335 instances
335 of 335 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)
- Warning208 instances
208 of 208 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)
- Warning78 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
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)
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 240 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 240 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 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/hakusan-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.