GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Yasu City Onori-Yasu Bus (野洲市コミバス おのりやす)

Based on the feed this agency publishes

Service mode Bus

70.9 / 100

First scorecard for this agency

Catalogued in Shiga, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Yasu City's Onori-Yasu community bus.

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

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

160 of 160 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

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

49 of 49 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

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.

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

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

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

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

Correctness67.5 / 100

The MobilityData validator flagged 7 kinds of issue across 1975 instances (0 error, 1973 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience52.4 / 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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • おのりやす あやめコース (teal)
  • おのりやす 安治コース (teal)
  • おのりやす 希望が丘コース (gray)
  • おのりやす 祇王・中里コース (yellow)
  • おのりやす 三上コース (green)
  • おのりやす 篠原コース (red)
  • おのりやす 中央循環コース (pink)
  • おのりやす 希望が丘コース (gray)
  • おのりやす 祇王・中里コース (yellow)
  • おのりやす 三上コース (green)
  • おのりやす 篠原コース (red)
  • おのりやす 中央循環コース (pink)
Routes in Yasu City Onori-Yasu Bus (野洲市コミバス おのりやす)'s feed
RouteTypeLine color
おのりやす あやめコースBusteal
おのりやす 安治コースBusteal
おのりやす 希望が丘コースBusgray
おのりやす 祇王・中里コースBusyellow
おのりやす 三上コースBusgreen
おのりやす 篠原コースBusred
おのりやす 中央循環コースBuspink
おのりやす 希望が丘コースBusgray
おのりやす 祇王・中里コースBusyellow
おのりやす 三上コースBusgreen
おのりやす 篠原コースBusred
おのりやす 中央循環コースBuspink

This feed has 160 stops.

List every stop
  • 三ツ坂
  • 三ツ坂
  • 南桜
  • 妙光寺公民館
  • 向山
  • 虫生神社前
  • 野洲駅南口
  • 野洲北中学校前
  • 野洲市健康スポーツセンター
  • 野洲市健康福祉センター
  • 野洲市役所
  • 江部西
  • 野洲中学校
  • 野洲中学校
  • 野洲図書館
  • 野洲西町
  • 野洲西町
  • 野洲東町
  • 野洲病院東
  • 野洲病院前
  • 野洲病院前
  • 家棟団地
  • 矢放神社前
  • 八夫口
  • 山出前
  • 近江富士１丁目
  • 近江富士１丁目
  • 行畑
  • 行畑
  • ゆきはたこども園前
  • ゆきはたこども園前
  • 吉川
  • 吉川北
  • 和田
  • 和田
  • 大篠原簡易郵便局前
  • 松林北
  • 野洲市役所西
  • 近江富士会館前
  • 近江富士５丁目
  • 近江富士２丁目
  • 近江富士２丁目
  • 大篠原
  • 大篠原
  • 大畑
  • 大畑
  • 乙窪
  • 乙窪口
  • 乙窪口
  • あやめ
  • 乙窪工業団地北口
  • 乙窪工業団地北口
  • 河川公園口
  • 河川公園口
  • 花緑公園
  • 花緑公園
  • 川尻
  • 祇王駐在所
  • 祇王幼稚園
  • 喜合
  • 北桜
  • 北桜口
  • 北桜口
  • 北自治会館前
  • アル・プラザ前
  • アル・プラザ前
  • 北野小学校前
  • 北比江
  • 北比江
  • 希望が丘文化公園前
  • 希望が丘文化公園前
  • 錦織寺前
  • 久野部
  • 久野部
  • 光善寺
  • 五条自治会館前
  • 五反田
  • 五反田
  • 小堤
  • 湖南病院
  • 安治自治会館前
  • 五之里
  • 小林住宅前
  • 小林住宅前
  • 小比江自治会館前
  • コミセンひょうず前
  • コミセンみかみ（御上神社口）
  • 小南口
  • 小南自治会館前
  • 桜生自治会館前
  • さくら墓園前
  • さざなみホール駐車場前
  • 生和神社前
  • さざなみホール前比留田
  • 七間場
  • 七間場
  • 篠原駅
  • 篠原小学校前
  • 市民交流センター前
  • 北部合同庁舎前
  • 下堤
  • 下町
  • 新上屋
  • 森林センター前
  • 市三宅
  • 須原自治会館前
  • 総合教育センター前
  • 総合教育センター前
  • 総合体育館駐車場
  • 総合体育館東口
  • 高木
  • 高木口
  • 竹生
  • 中主小学校前
  • 中主中学校前
  • 辻町
  • 辻町
  • 市三宅口
  • 市三宅口
  • 堤自治会館前
  • 出町口
  • 銅鐸博物館前
  • 銅鐸博物館前
  • 冨波乙公民館前
  • 冨波会館前
  • 冨波会館前
  • 冨波野住宅前
  • ドリームファーム前
  • 中北
  • 長島自治会館前
  • 井口自治会館前
  • 中畑
  • 中畑
  • 永原住宅前
  • 永原住宅前
  • 成橋
  • 西河原五丁目
  • 西河原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

10 findings, ordered by severity.

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

  • Warning160 instances

    160 of 160 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

  • Warning49 instances

    49 of 49 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

  • Warning20 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

  • Warning17 instances

    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

  • Warning5 instances

    Two or more routes share the same name.

    Riders can't tell the routes apart in apps.

    Fix: Give each route a distinct short or long name. (One field per route.)

    Validator rule: duplicate_route_name · 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.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · 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.)

    Validator rule: missing_recommended_field · Read the fix guide · 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.)

    Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

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 68 / 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.

Yasu City Onori-Yasu Bus (野洲市コミバス おのりやす) GTFS data quality grade: C

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/yasu-city-onori-yasu-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.