GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-18

Bizkaibus

Grade D · 68.3 / 100

First check for this agency, so there is no trend yet.

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

No category changes since the last check.

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.

    1359 of 2335 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.

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

  2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

    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.

    Effort: Often a bulk fix in your scheduling software.

  3. Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Key facts

Feed URL
https://baliabideak.bizkaia.eus/Bizkaibus/GTFS/Bizkaibus.zip
Last checked
2026-07-18
Service window
59 days of service data remain. Last service date 2026-09-15.
Feed version
20260716
Location
Bizkaia, Spain

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