GTFS Scorecard
← All agencies

Feed status · checked 2026-10-21

本巣市営バス

Based on the official feed source on file

Service mode Bus

75.3 / 100

unchanged since 2026-10-20

Cataloged in Gifu, Japan.

Covers 252 daysAccessibility gapsRealtime not yet published

Source feed: https://api.gtfs-data.jp/v2/organizations/motosucity/feeds/shieibus/files/feed.zip?rid=current

本巣市営バス is the public schedule named by the repository. This registry item represents one feed record.

Heads-up: The score rose 24 points in one step, from 49 on 2026-10-13 to 73 on 2026-10-14. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-10-14). This can be a brief vendor export glitch; watch the next update before acting.

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.4, validator 8.0.1.

Checked for changes 3 hours ago; last changed 7 days ago.

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.

About this feed

本巣市営バス’s published feed lists 7 bus routes, 53 scheduled trips and 161 stops. Its service dates run from 2026-10-15 through 2027-06-30. The published file last changed on 2026-10-14.

Top things to fix

Fix 01

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

161 of 161 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.

Fixing this covers all 161 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

53 of 53 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 53 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. See this feed's finding-clearance log.

  3. Fix 03

    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. See this feed's finding-clearance log.

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 252 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

Correctness77.5 / 100

The MobilityData validator flagged 5 kinds of issue across 1505 instances (0 error, 1503 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 252 days.

Rider experience52.3 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 3 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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 161 stops.

Skip to route and stop data

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.

  • 本巣市市営バス本巣北部線 (green)
  • 本巣市市営バス本巣・糸貫線 (red)
  • 本巣市市営バス弾正線 (blue)
  • 本巣市市営バス真桑線 (purple)
  • 本巣市市営バス根尾宇津志線 (teal)
  • 本巣市市営バス根尾能郷線 (yellow)
  • 本巣市市営バス根尾松田・奥谷線 (brown)
Routes in 本巣市営バス's feed
RouteTypeLine color
本巣市市営バス本巣北部線Busgreen
本巣市市営バス本巣・糸貫線Busred
本巣市市営バス弾正線Busblue
本巣市市営バス真桑線Buspurple
本巣市市営バス根尾宇津志線Busteal
本巣市市営バス根尾能郷線Busyellow
本巣市市営バス根尾松田・奥谷線Busbrown
List every stop
  • 本巣公民館
  • 本巣駅
  • JA本巣支店
  • 織部の里もとす
  • 木知原駅
  • 木知原集荷場
  • 長谷極又口
  • 長谷竹浦口
  • 川内公民館
  • 木倉公民館
  • 木倉金坂口
  • 日当公民館
  • 上金原
  • 金原公民館
  • 下金原
  • 鍋原公民館
  • 根尾川ガーデン
  • 佐原公民館
  • 佐原公民館
  • 神海上新田
  • 神海駅
  • 本巣診療所
  • 外山郵便局
  • 林製材所
  • 山口公民館
  • 山口集荷場
  • 向道集落センター
  • 本巣郵便局
  • 大和園
  • バロー本巣文殊店
  • モレラ岐阜
  • ぬくもりの里
  • 富有柿の里
  • 富有柿の里
  • 宝珠
  • 宝珠
  • 宝珠ハイツ口
  • 宝珠ハイツ口
  • 宝珠ハイツ公園
  • 宝珠ハイツ公園
  • 宝珠ハイツ
  • 宝珠ハイツ
  • 徳山団地
  • 上新町
  • 総合運動場
  • 文殊団地
  • 西之門
  • 本巣小学校
  • 市民スポーツプラザ
  • 長屋神社前
  • 長屋神社前
  • 上高屋
  • 下高屋
  • 有里
  • 数屋
  • 新屋敷
  • 更屋敷公民館
  • なかしま医院
  • 随原
  • 見延
  • 桜ヶ丘
  • 本郷
  • 中野
  • フレンドリーおりべ
  • 小弾正
  • 南出
  • 浅木
  • 政田
  • 清水
  • みつば
  • イオンタウン本巣
  • イオンタウン本巣
  • LCワールド本巣
  • 溝口
  • 天神前住宅
  • 天神前住宅
  • 真正すこやかセンター
  • まくわクリニック
  • 旧真正分庁舎
  • 下真桑南
  • 下真桑
  • 大門東
  • 大門東
  • 本巣松陽高校南
  • 北方真桑駅
  • みどり公園
  • みどり公園
  • 大塚古墳公園
  • 宗慶東
  • 北方バスターミナル
  • 仏生寺
  • 堀部クリニック
  • 天神
  • 下石原
  • 北部公園
  • 糸貫内科クリニック
  • 樽見駅前
  • 宇津志
  • 日当駅前
  • 日当
  • 平野
  • 高尾
  • 山崎
  • 門脇（高尾地区）
  • 高尾宮前
  • 江浪
  • 水鳥宮前
  • 水鳥
  • みどり団地
  • 開運橋
  • 板所
  • 根尾学園前
  • 市場西
  • 診療所前
  • 樽見
  • 根尾分庁舎前
  • 市場
  • 神所
  • 上神所
  • 中
  • 越卒
  • 上越卒
  • 大井
  • 八谷
  • 八谷集会所前
  • 長嶺
  • 上長嶺
  • 天神堂
  • 長島発電所前
  • 長島
  • 黒津口
  • 能郷
  • 能郷上原
  • 上樽見
  • 下タ島
  • 西板屋橋
  • 西板屋
  • 板屋村中
  • 東板屋
  • 口谷口
  • 口谷
  • 奥谷
  • 中元
  • 上洞
  • トッサス
  • 西小鹿
  • 東小鹿
  • 上東小鹿
  • 下松田
  • 松田
  • 上松田
  • 門脇
  • 道の駅うすずみ桜の里・ねお
  • あさぎ苑公民館
  • もとまるパーク
  • 本巣市役所
  • おんさい広場
  • おんさい広場
  • 中島・ゲンキー北
  • 糸貫体育センター・モレラ南口
  • 小柿

Over time

Overall score across the last 20 checks — unchanged since 2026-10-20.

2026-10-02: 53.52026-10-03: 53.12026-10-04: 52.72026-10-05: 52.32026-10-06: 51.82026-10-07: 51.42026-10-08: 51.02026-10-09: 50.62026-10-10: 50.22026-10-11: 49.82026-10-12: 49.32026-10-13: 48.92026-10-14: 73.12026-10-15: 75.32026-10-16: 75.32026-10-17: 75.32026-10-18: 75.32026-10-19: 75.32026-10-20: 75.32026-10-21: 75.3
Show the numbers
CheckScoreChange
2026-10-0253.5 first check
2026-10-0353.1 down 0.4
2026-10-0452.7 down 0.4
2026-10-0552.3 down 0.4
2026-10-0651.8 down 0.5
2026-10-0751.4 down 0.4
2026-10-0851.0 down 0.4
2026-10-0950.6 down 0.4
2026-10-1050.2 down 0.4
2026-10-1149.8 down 0.4
2026-10-1249.3 down 0.5
2026-10-1348.9 down 0.4
2026-10-1473.1 up 24.2
2026-10-1575.3 up 2.2
2026-10-1675.3 no change
2026-10-1775.3 no change
2026-10-1875.3 no change
2026-10-1975.3 no change
2026-10-2075.3 no change
2026-10-2175.3 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-14 to 2026-10-21 (8 checks)0e5126ddd5dc2027-06-30Current rubric: see the trend above
2026-10-02 to 2026-10-13 (12 checks)a5f4614de0532026-10-14Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)a5f4614de0532026-10-14F, 53.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-09-29 (63 checks)6136ef40cf032027-03-31C, 75 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-23 to 2026-07-24 (2 checks)6136ef40cf032027-03-31C, 75 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-20.

Same feed file as 2026-10-20; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

What changed over time

On 2026-10-02 this feed started at grade F. On 2026-10-14 the grade moved from F to C. As of 2026-10-21 it holds grade C.

A plain-language history of this feed, newest first.

  • 2026-10-14 Grade went F to C, freshness rose 98 points.

Everything we checked

8 findings, ordered by severity.

Show every finding
  • Warning1469 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

  • Warning161 instances

    161 of 161 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning53 instances

    53 of 53 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning32 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules

  • 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules

  • 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 for missing_recommended_field · See MobilityData GTFS Validator rules

  • 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 for unknown_column · See MobilityData GTFS Validator rules

  • 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 for scorecard_no_feed_contact · See MobilityData GTFS Validator rules

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 252 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 252 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.

Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Gifu

Other scorecards in Gifu, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

本巣市営バス: GTFS feed quality grade C, 75.3 of 100, checked 2026-10-21. GTFS 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/motosucity-shieibus/2026-10-21.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-10-21. 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.