Feed status · checked 2026-07-23
飛騨市営バス「ひだまる」
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Gifu, 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
211 of 211 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
109 of 109 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 69 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 6 kinds of issue across 3014 instances (0 error, 3011 warning, 3 informational).
Service data covers the next 69 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 (O12ひだまる 神岡東部線, O18ひだまる 殿循環線, O21ひだまる 桃源郷線, O41ひだまる 宮川線（予約便）, O41ひだまる 宮川線).
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.
- O10ひだまる かみおかぐるりんバス (white)
- O11ひだまる 山之村線 (teal)
- O12ひだまる 神岡東部線 (teal)
- O14ひだまる 吉田線 (yellow)
- O17ひだまる 神原線 (pink)
- O18ひだまる 殿循環線 (brown)
- O19ひだまる 神岡猪谷線 (black)
- O21ひだまる 桃源郷線 (red)
- O22ひだまる 太江線 (yellow)
- O23ひだまる 畦畑線 (gray)
- O31ひだまる 稲越線（予約便） (teal)
- O31ひだまる 稲越線 (teal)
- O32ひだまる 天生線（予約便） (black)
- O32ひだまる 天生線 (black)
- O41ひだまる 宮川線（予約便） (orange)
- O41ひだまる 宮川線 (orange)
| Route | Type | Line color |
|---|---|---|
| O10ひだまる かみおかぐるりんバス | Bus | white |
| O11ひだまる 山之村線 | Bus | teal |
| O12ひだまる 神岡東部線 | Bus | teal |
| O14ひだまる 吉田線 | Bus | yellow |
| O17ひだまる 神原線 | Bus | pink |
| O18ひだまる 殿循環線 | Bus | brown |
| O19ひだまる 神岡猪谷線 | Bus | black |
| O21ひだまる 桃源郷線 | Bus | red |
| O22ひだまる 太江線 | Bus | yellow |
| O23ひだまる 畦畑線 | Bus | gray |
| O31ひだまる 稲越線（予約便） | Bus | teal |
| O31ひだまる 稲越線 | Bus | teal |
| O32ひだまる 天生線（予約便） | Bus | black |
| O32ひだまる 天生線 | Bus | black |
| O41ひだまる 宮川線（予約便） | Bus | orange |
| O41ひだまる 宮川線 | Bus | orange |
This feed has 211 stops.
List every stop
- 飛騨古川駅
- 古川小学校
- 吉城高校口
- 和光園下
- 浄慶寺前
- 太江公民館
- 太江火の見
- 太江上野中
- 文化交流センター前
- 和佐府
- 打保橋
- 下之本・神明神社前
- 重機センター
- 下之本
- 岩井谷
- 山之村小中学校
- 森茂南
- 森茂
- 杉崎
- 杉崎
- 森茂センター
- 旧森茂農協前
- 伊西下
- 伊西上
- 和佐保
- 神岡大橋
- 神岡大橋
- 殿
- 殿
- 江馬館前
- 殿村
- 殿村
- たかはら前
- 古川西小学校
- 道の駅スカイドーム・カミオカラボ
- 神岡小学校
- 神岡振興事務所
- 飛騨市民病院
- 西里
- 西里
- 千歳橋
- 千歳橋
- 濃飛バス神岡営業所
- 谷研修センター前
- 割石温泉
- 西里橋
- 西里橋
- 下今公園
- 下今公園
- JA信包支店前
- 旧飛騨神岡駅
- 梨ヶ根公園前
- 寺林公民館
- 伏方公民館
- 柏原
- 山田細川前
- 上山田公民館
- 山田体育館前
- 西
- 流葉温泉・スキー場
- 流葉温泉・スキー場
- 笹ヶ洞公民館
- 西公民館
- 西公民館
- 流葉口
- 流葉口
- 袖川郵便局前
- 杉越トンネル山田口
- 阿弥陀堂前
- 上小萱
- 野首公民館前
- 飛騨神岡高校前
- 釜崎
- 釜崎
- 弥生町
- すぱーふる桃源郷温泉
- ガッタンゴー旧奥飛騨温泉口駅
- 坂巻
- 坂巻
- 旭ヶ丘
- 旭ヶ丘
- 東雲
- 下麻生野
- 石神
- 奥麻生野
- 神岡城口
- 柏原パーキング
- 神岡・船津座
- 営農センター前
- 営農センター前
- 神岡下数河
- 神岡下数河
- 吉田旧精米所前
- 釜崎公民館前
- 釜崎社会体育館前
- 神岡上数河
- 神岡上数河
- 和佐府橋
- 丸山公民館
- 中吉田
- 上野
- 下野首
- 常蓮寺前
- 伏方薬師堂前
- 堀之内上組
- 堀之内中組
- 寺林平前
- 山之村牧場
- 本町防災公園
- 本町防災公園
- 神岡鉱山口
- 割石温泉口
- 割石温泉口
- 中野公民館
- 漆山
- ガッタンゴー漆山駅
- ガッタンゴー漆山駅
- 西漆山
- 鍋谷
- 土
- 茂住
- 茂住
- 横山
- 中山
- 猪谷駅
- 下野
- 上組作業場
- 新栄町
- 新栄町
- 行真
- 行真
- 太江下野中
- 飛騨市役所・図書館
- 駿河屋前
- 駿河屋前
- 道の駅アルプ飛騨古川
- 野口
- 野口
- 細江駅前
- 細江駅前
- 細江郵便局前
- 細江郵便局前
- 袈裟丸岡前
- 袈裟丸岡前
- 東の谷公園前
- 山王
- 角川駅
- 河合保育園
- ゆうわーくはうす・河合診療所
- 河合振興事務所
- JA河合支店前
- 荒町
- 羽根
- 杉崎下
- 杉崎下
- 大谷口
- 寺村
- 脇谷
- 飛騨古川ふれあい広場
- 寺地公民館
- 二ツ屋口・香愛ローズガーデン
- 有家口
- 中沢上
- 諏訪神社
- 保木
- 林
- 新名口
- 上ヶ島
- なかんじょ川釣り公園口
- 元田中家前
- 元田
- 天生田中前
- 黒淵
- 芦谷
- 曲淵
- 桂上
- 花戸
- 葛牧
- 河合中山
- 柳ヶ瀬
- 宮ノ脇
- 宮ノ前
- 花之木
- 橋本商店前
- 天生集会場
- 平岩研修センター前
- 飛騨警察署前
- 飛騨警察署前
- 小豆沢
- 飛騨まんが王国・おんり～湯
- 塩屋・平成橋
- 打保駅前
- 巣之内
- 西忍
- 宮川小学校
- 宮川診療所
- 牧戸
- 若田前
- 宮川振興事務所・坂上駅前
- 落合
- 棚田の里・種蔵登り口
- 戸谷
- 杉原駅前
- 宮城橋・古川病院口
- 宮城橋・古川病院口
- 白壁土蔵街・飛騨市役所前
- 白壁土蔵街・飛騨市役所前
- 釣瓶橋
- 釣瓶橋
- 宮城保育園
- 古川中学校
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
9 findings, ordered by severity.
Show every finding
- Warning2965 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)
- Warning211 instances
211 of 211 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)
- Warning109 instances
109 of 109 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)
- Warning44 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)
- Warning1 instance
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)
- 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
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Validator rule: big_gap_in_service · 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 69 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 69 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 77 / 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/hidacity-communitybus/2026-07-23.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-23. 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.