GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

Toyama Oyama Community Bus (富山市 大山コミュニティバス)

Based on the feed this agency publishes

Service mode Bus

67.2 / 100

First scorecard for this agency

Catalogued in Toyama, Japan.

Covers 251 daysAccessibility gaps

Toyama City's Oyama community bus. The official catalog also publishes keyless TripUpdates and VehiclePositions.

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 70 minutes ago; last changed 70 minutes ago.

Measured 4 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 6 snapshots.
  • 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

Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.

The realtime feed's last update was about 3 hours old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.

⏱ A vendor support ticket; treat it as a feed outage.worth about +50 points in its category

Fix 02

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

68 of 68 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 03

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.

⏱ A default or per-trip field in your export.worth about +15 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. Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.

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

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

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 251 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
One or more realtime feeds were reachable; live-arrival coverage is not known.

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

Correctness69.0 / 100

The MobilityData validator flagged 8 kinds of issue across 1020 instances (0 error, 1017 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 251 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

  • 2 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 quality50.0 / 100

Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable.

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.

  • 市営大山コミュニティバス　小坂線（小坂行き） (orange)
  • 市営大山コミュニティバス　小坂線（大山会館前行き） (orange)
  • 市営大山コミュニティバス　楜ヶ原線（樫ノ木行き） (gray)
  • 市営大山コミュニティバス　楜ヶ原線（大山会館前行き） (gray)
  • 市営大山コミュニティバス　楜ヶ原線（福沢公民館前行き） (gray)
  • 市営大山コミュニティバス　西小俣循環線 (teal)
  • 市営大山コミュニティバス　才覚地線（中地山行き） (brown)
  • 市営大山コミュニティバス　才覚地線（老人センター前行き） (brown)
Routes in Toyama Oyama Community Bus (富山市 大山コミュニティバス)'s feed
RouteTypeLine color
市営大山コミュニティバス　小坂線（小坂行き）Busorange
市営大山コミュニティバス　小坂線（大山会館前行き）Busorange
市営大山コミュニティバス　楜ヶ原線（樫ノ木行き）Busgray
市営大山コミュニティバス　楜ヶ原線（大山会館前行き）Busgray
市営大山コミュニティバス　楜ヶ原線（福沢公民館前行き）Busgray
市営大山コミュニティバス　西小俣循環線Busteal
市営大山コミュニティバス　才覚地線（中地山行き）Busbrown
市営大山コミュニティバス　才覚地線（老人センター前行き）Busbrown

This feed has 68 stops.

List every stop
  • 大山会館前
  • 大山会館前
  • おおやま病院前
  • おおやま病院前
  • 岡田
  • 小見小学校前
  • 小見地区センター前
  • 樫ノ木
  • 上大浦
  • 上岡田
  • 上新町
  • 上瀬戸
  • 上滝駅前
  • 上滝駅前
  • 上滝中学校前
  • 上滝中学校前
  • 亀谷
  • 川端町
  • 川端町
  • 楜ヶ原
  • 楜ヶ原口
  • 新町
  • 小坂
  • 才覚地
  • 下小坂
  • 下双嶺
  • 白樺の湯・歴史民俗資料館前
  • 新上野
  • 新大上
  • 石渕
  • 瀬戸
  • 大川寺口
  • 瀧谷口
  • 津毛
  • 中大浦
  • 中地山
  • 中地山口
  • 中地山発電所前
  • 中坪
  • 中坪
  • 西小俣
  • 布目
  • 上野
  • 花崎
  • 花崎
  • 稗田
  • 日尾
  • 日尾口
  • 東小俣
  • 東黒牧
  • 東黒牧T字路
  • 福沢地区センター前
  • 福沢小学校前
  • 上野口
  • 文華橋
  • 文華橋
  • 牧
  • 牧野
  • 牧野橋詰
  • 松ノ木
  • 文珠寺
  • 文珠寺
  • 老人センター前
  • 老人センター前
  • 和田
  • 円段
  • 和田平
  • 大上

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

12 findings, ordered by severity.

Show every finding
  • Error1 instance

    The realtime feed's last update was about 3 hours old when sampled.

    A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.

    Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)

    Validator rule: scorecard_rt_feed_lapsed

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

  • Warning68 instances

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

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

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

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

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

  • 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

  • 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

  • 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

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Validator rule: trip_headsign_matches_intermediate_stop · 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 251 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.

Realtime reliability

The realtime feed responded on 100.0% of 1 checks, with 10796s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Clears the Google and Apple Maps four-week coverage bar. This feed has 251 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 69 / 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 50 / 100
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.

Toyama Oyama Community Bus (富山市 大山コミュニティバス) GTFS data quality grade: D

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/toyama-oyama-community-bus/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.