Feed status · checked 2026-07-19
Gifu City Community Bus (岐阜市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.
Checked for changes 6 hours ago; last changed 6 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
1032 of 1032 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
203 of 203 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 6 kinds of issue across 7926 instances (0 error, 7924 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (にっこりバス, みわっこバス, eバス, すまいるバス, さんさんバス, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 加納めぐりバス (black)
- 西ぎふ・くるくるバス (black)
- にっこりバス (orange)
- みわっこバス (red)
- eバス (red)
- みどりっこバス (green)
- ほっとバス (green)
- あいあいバス (green)
- ３７３バス (black)
- 境川らくちゃんバス (red)
- ながらうかいバス (black)
- 芥見岩っこバス (brown)
- すまいるバス (pink)
- さんさんバス (red)
- 厚見・茜部ぐるりふれあいバス (blue)
- ひのっこバス (red)
- 長森ふれあいバス (teal)
- 七郷・木田バス (green)
- ぐるっとバス (green)
- おべにバス (red)
| Route | Type | Line color |
|---|---|---|
| 加納めぐりバス | Bus | black |
| 西ぎふ・くるくるバス | Bus | black |
| にっこりバス | Bus | orange |
| みわっこバス | Bus | red |
| eバス | Bus | red |
| みどりっこバス | Bus | green |
| ほっとバス | Bus | green |
| あいあいバス | Bus | green |
| ３７３バス | Bus | black |
| 境川らくちゃんバス | Bus | red |
| ながらうかいバス | Bus | black |
| 芥見岩っこバス | Bus | brown |
| すまいるバス | Bus | pink |
| さんさんバス | Bus | red |
| 厚見・茜部ぐるりふれあいバス | Bus | blue |
| ひのっこバス | Bus | red |
| 長森ふれあいバス | Bus | teal |
| 七郷・木田バス | Bus | green |
| ぐるっとバス | Bus | green |
| おべにバス | Bus | red |
This feed has 1032 stops.
List every stop
- 名鉄柳津駅
- 柳津地域事務所
- 北塚会館
- カラフルタウン北口
- 下佐波1丁目
- もえぎの里
- スーパービバホーム
- ファミリー歯科・黒田内科クリニック南
- くまざき内科前
- 且格小学校前
- ＪＡ日置江支店前
- 天野
- 田中歯科医院前
- うおよし前
- 大脇森北冷機前
- 岐阜聖徳学園大学
- 岐阜南病院北・㈱カネヒロ前
- 高桑コミュニティ会館
- 坂巻
- ＪＲ岐阜駅南口
- 宮下
- カラフルタウン南口
- カラフルタウン
- 南塚4丁目
- 梅松
- 諏訪山口
- 河村病院東
- たなかクリニック前
- コートスマイル前
- 加納北広江町
- 加納北広江町
- 日の出町
- へあーさろんまつお前
- 本町
- 本郷いこい広場
- 本郷いこい広場
- イオン柳津店南口
- 蓮池6丁目
- 東塚1丁目
- 松波総合病院
- 栄町
- 東塚3丁目
- 加納中広江町
- 加納中広江町
- 柳津あおやま眼科クリニック
- 蓮池2丁目（石窯パン工房ドゥマン前）
- イオン柳津店
- 竹内医院南
- ワコー自動車前
- サカヤス前
- 南鶉3丁目
- 江崎歯科東
- 鶉小学校東
- 中鶉4丁目
- 中山道・水薬師・大手御門
- 中山道・水薬師・大手御門
- 笠松病院・岐阜市地域包括支援センター境川
- スーパー三心東
- うずら歯科
- 東鶉7丁目バス停
- 津島神社前（鶉）
- 鶉公民館前
- 岐阜信用金庫・カネスエ中鶉店
- 堀江畳店前
- JA鶉支店前
- 清水野
- 附属小・中学校
- 附属小・中学校
- かねまつ整形外科前
- 宮上ふれあい会館西
- 中佐波
- やまだ整形外科・内科クリニック、柳津生涯学習センター
- 高齢者福祉センター
- おおくま歯科前
- 加納小学校・加納東公民館
- 加納小学校・加納東公民館
- 加納城址
- 加納城址
- 加納公園
- 加納公園
- 南部コミセン
- バロー長良店
- バロー長良店
- 雄総台西
- 雄総台東
- 長良台
- おぶさ
- おぶさ公民館前
- 雄総緑町2丁目
- 雄日ヶ丘公園西
- 雄日ヶ丘公園東
- 加納中学校
- 中川原
- 雄総緑町４丁目
- 鵜飼大橋北
- 雄総柳町
- 雄総桜町
- サンライフ岐阜
- 長良東
- 長良東
- 田中接骨院
- 長良高校前
- 長良宮口町
- 加納中通り
- 加納中通り
- 長良東郷町
- 長良大路
- 長良北町
- ピアゴ長良店
- ピアゴ長良店
- ピアゴ長良店
- 福光東3丁目
- 福光東3丁目
- 長良高見
- 子正賀西
- 友瀬・子正賀
- 加納花ノ木町
- 岐山高校南
- 西山（長良）
- 長良福泉
- 清水ヶ丘
- 眞福禅寺前
- 松籟荘
- 長良竜東町2丁目
- 長良竜東町4丁目
- 長良医療センター
- 北保健センター
- 加納鉄砲町5丁目
- 加納鉄砲町5丁目
- 猿田彦神社前
- 猿田彦神社前
- 加納高校
- 加納高校
- 加納堀田町2丁目
- 加納堀田町2丁目
- メガドンキ前
- メガドンキ前
- 加納西小学校・公民館
- 加納西小学校・公民館
- 加納神明町・児童センター
- 加納神明町・児童センター
- バロー岩田店
- 岩田東３丁目
- 岩田（東）
- 神池
- 神池
- 三信町
- 流公園
- 岩田坂南町
- 小坂町
- 岩田坂北町
- 加納愛宕町
- 加納愛宕町
- 畑中
- 桜町
- ミカド前
- 石原産婦人科前
- 嵯峨
- 中野畑
- 自由ヶ丘1
- 自由ヶ丘2
- 自由ヶ丘3
- 自由ヶ丘4
- 朝日大学病院前
- 自由ヶ丘5
- 諏訪山1
- しいのみ公園東
- 諏訪山2
- 諏訪山3
- 岩田（西）
- 朝日町
- 八幡町
- 八幡神社前
- 芥見小学校北
- 愛宕住宅前（山田商会前）
- 東芥見・ＪＡ芥見支店
- 下芥見
- 市民病院前
- ＮＴＴ本荘
- ＮＴＴ本荘
- 本荘公民館
- 本荘公民館
- 本荘西公園西
- 本荘西公園西
- ヘルスバンク敷島店
- ヘルスバンク敷島店
- 岐南工業高校
- 岐南工業高校
- 科学館前
- 科学館前
- 県美術館北
- 県美術館北
- 図書館美術館駐車場前
- 図書館美術館駐車場前
- 宇佐住吉町
- 宇佐住吉町
- 宇佐東町
- 宇佐東町
- 神明神社北
- 神明神社北
- 早徳病院東
- 早徳病院東
- 岐阜産業会館
- 岐阜産業会館
- 金花堂鍼灸整骨院前
- 金花堂鍼灸整骨院前
- 福寿公園前
- 福寿公園前
- 片田神社前
- 片田神社前
- 笠原鋼鉄前
- 笠原鋼鉄前
- みさとこども園前
- みさとこども園前
- 三里小学校前
- 三里小学校前
- 丸川荘前
- 丸川荘前
- 三里診療所前
- 三里診療所前
- 清本町５丁目
- 清本町５丁目
- カネスエ
- カネスエ
- たかはし整形外科前
- たかはし整形外科前
- オーキッドパーク
- オーキッドパーク
- 敷島町３丁目
- 敷島町３丁目
- 本荘公園西
- 本荘公園西
- こばと幼稚園
- こばと幼稚園
- 嵯峨野前
- 嵯峨野前
- 岐阜電材前
- 岐阜電材前
- 本荘中学校前
- ふじの湯・まさき接骨院
- ふじの湯・まさき接骨院
- 正木北公園前
- 石黒クリニック前
- 石黒クリニック前
- 鷺山北公園
- 鷺山北公園
- 鷺山保育所
- 鷺山保育所
- 早田飯店前
- 早田飯店前
- and 782 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 | 72.6 | first check |
| 2026-07-19 | 72.6 | 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
9 findings, ordered by severity.
Show every finding
- Warning7571 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)
- Warning1032 instances
1032 of 1032 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)
- Warning350 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)
- Warning203 instances
203 of 203 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)
- 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
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
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
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 72 / 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/gifu-city-community-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.