GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-18

Guimabus (Guimarães)

Grade F · 46.5 / 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. Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

    Invalid integer (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

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

Key facts

Feed URL
https://map.mobility.ubiwhere.com/dataset/ee6d46e4-9f19-4f4a-ab93-1a3cd69df349/resource/08f1ee6c-2d3f-4fb3-a861-5d6fb347a6d4/download/gtfs_gui.zip
Last checked
2026-07-18
Service window
166 days of service data remain. Last service date 2026-12-31.
Location
Braga, Portugal

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