GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-20

Onomichi Bus (おのみちバス)

Grade C · 74.0 / 100

Up 2.3 points since 2026-10-19 (C to C).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality up 11.5

No longer reported since the last check (1 finding):

  • 1 of 2 sampled vehicle positions were far from their assigned route (worst: 477 m). (scorecard_rt_vehicles_off_route)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    472 of 472 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 472 stops in the feed.

    Effort: A column in stops.txt; your scheduling software likely has it.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

    1406 of 1406 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 1,406 trips in the feed.

    Effort: A default or per-trip field in your export.

  3. Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.

    Some rows in stop_times.txt leave the timepoint column blank. That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

    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.

    Effort: Usually one export setting.

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.

Feed evidence
472 of 472 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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

Key facts

Feed URL
https://ajt-mobusta-gtfs.mcapps.jp/static/53/current_data.zip
Last checked
2026-10-20
Service window
167 days of service data remain. Last service date 2027-04-05.
Feed version
20261005
Location
Hiroshima, Japan

Part of the Japan portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.