GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-24

Fertagus

Grade A · 95.1 / 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. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

    Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

    Effort: Usually an export-tool fix, not hand editing.

  2. Turn on 'remove unused shapes' (or the like) in your export tool.

    The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.

    Effort: One setting.

  3. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

    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.

    Effort: A quick look at the flagged files.

Key facts

Feed URL
https://www.fertagus.pt/GTFSTMLzip/Fertagus_GTFS.zip
Last checked
2026-07-24
Service window
167 days of service data remain. Last service date 2027-01-07.
Feed version
26.10.19
Location
Setúbal, Portugal

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