GTFS Scorecard

← Back to the full scorecard

Board packet · transit data quality · checked 2026-10-07

Southeastern Pennsylvania Transportation Authority (SEPTA) Rail

Grade B · 87.3 / 100

Down 0.2 points since 2026-10-06 (B to B).

What this grade measures

The quality of the schedule data in the feed scored here 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

Since the previous compatible check, 1 finding was no longer reported:

  • 1 of 30 trips scheduled during the sampling window had no live predictions.

This records feed state, not who made a change or why.

What needs attention next

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

  1. Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

    47 of 134 sampled vehicle positions were far from their assigned route (worst: 32565 m). A transit vehicle shown off its route usually means a wrong trip assignment; riders watch their transit vehicle drive the wrong path.

    This was measured over a realtime sampling window, so it has no feed-wide share.

    Estimated effort: A vendor support ticket with the trip ids attached.

  2. Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.

    Some stops sit far from the route line they belong to. Trip planners may draw the transit vehicle route through 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.

    Estimated effort: A few minutes per flagged stop.

  3. Add feed_contact_email or feed_contact_url to feed_info.txt.

    feed_info.txt lists no contact email and no contact URL. Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    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.

    Estimated effort: One field, set once in export settings.

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Pennsylvania as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

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
47 of 134 sampled vehicle positions were far from their assigned route (worst: 32565 m).
Next action
Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.
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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/southeastern-pennsylvania-transportation-authority-septa-503/. Rubric v1.4, validator 8.0.1.