Call-prep brief · checked 2026-11-21
Pittsburgh Regional Transit
Grade C · 73.1 / 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
Top three things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
6354 of 6354 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fixing this covers all 6,354 stops in the feed.
Effort: A column in stops.txt; your scheduling software likely has it.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
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: Often a bulk fix in your scheduling software.
Pick a darker/lighter route_text_color for the flagged routes.
Some route colors don't contrast with their text color. Route badges get hard to read, most of all for riders with low vision.
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 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
- 6354 of 6354 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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 rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND 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
- Feed evidence
- Some route colors don't contrast with their text color.
- Next action
- Pick a darker/lighter route_text_color for the flagged routes.
- 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://www.portauthority.org/developerresources/GTFS.zip
- Last checked
- 2026-11-21
- Service window
- 91 days of service data remain. Last service date 2027-02-20.
- Feed version
- S1000171
- 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.