Fertagus

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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.

   Estimated 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.

   Estimated 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.

   Estimated effort: A quick look at the flagged files.