Call-prep brief · checked 2026-11-21
Southeastern Pennsylvania Transportation Authority (SEPTA) Rail
Grade A · 91.7 / 100
Unchanged since 2026-11-20.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. 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
- Realtime quality up 0.2
Top three things to fix
Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.
21 of 65 sampled vehicle positions were far from their assigned route (worst: 31711 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.
Effort: A vendor support ticket with the trip ids attached.
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.
Effort: One field, set once in export settings.
Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.
Some route long names repeat the route's short name inside them. Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
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 field per flagged route.
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-11-02.
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
- 21 of 65 sampled vehicle positions were far from their assigned route (worst: 31711 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
- Feed evidence
- feed_info.txt lists no contact email and no contact URL.
- Next action
- Add feed_contact_email or feed_contact_url to feed_info.txt.
- 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
- Feed evidence
- Some route long names repeat the route's short name inside them.
- Next action
- Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.
- 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
NTD GTFS readiness: Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 91 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
Key facts
- Feed URL
- https://www3.septa.org/developer/google_rail.zip
- Last checked
- 2026-11-21
- Service window
- 91 days of service data remain. Last service date 2027-02-20.
- Feed version
- v202611220
- Location
- Pennsylvania
Part of the Pennsylvania 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.5, validator 8.0.1.