Fix: the feed contains route shapes no trip uses
Published: . Last reviewed: .
Code: unused_shape (MobilityData validator)
What this means
shapes.txt defines geographic paths for routes, and your feed includes shapes
that no trip in trips.txt references. They are dead weight left behind by the
export.
Why it matters
Unused shapes do not hurt riders directly. They make the feed larger than it needs to be and usually signal that the export is carrying stale data, which is worth knowing because the same staleness can affect things that do matter.
How to fix it
- In your export settings, look for an option like "remove unused shapes", "clean up shapes", or "only export referenced data". Turning it on drops the orphans automatically on the next export.
- If there is no such setting, the shapes are usually leftovers from retired trips or patterns. Removing those retired patterns at the source clears the shapes too.
How long it usually takes
One setting, applied on the next export. If you have to track down retired patterns by hand it is a short review pass, not a project.
Authoritative rule
unused_shape is a canonical MobilityData GTFS Validator notice used in validator reports across the GTFS ecosystem. Read the authoritative rule for unused_shape in the GTFS Validator rules. (opens on an external site)
After you republish
Once the changed feed is live at your published URL, the next scorecard run checks it again. When the same complete producer contract no longer reports this finding, it can be recorded as a dated finding clearance. That confirms the later feed state, not who changed the feed or why.