Call-prep brief · checked 2026-10-22

Fertagus

Grade A · 95.1 / 100

Unchanged since 2026-10-21.

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

Top three things to fix

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.
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 an export-tool fix, not hand editing.
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.
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: One setting.
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.
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: A quick look at the flagged files.

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: Some stops sit far from the route line, going by the feed's own distance values.
Next action: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
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

Agency: Fertagus
Finding: stop_too_far_from_shape_using_user_distance
Feed evidence: Some stops sit far from the route line, going by the feed's own distance values.
Why it matters: Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Requested change: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/fertagus/?finding=stop_too_far_from_shape_using_user_distance#finding-handoff

Key facts

Feed URL: https://www.fertagus.pt/GTFSTMLzip/Fertagus_GTFS.zip
Last checked: 2026-10-22
Service window: 143 days of service data remain. Last service date 2027-03-14.
Feed version: 26.10.20
Location: Setúbal, Portugal

Part of the Portugal 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.