Call-prep brief · checked 2026-10-07
Anchorage People Mover
Grade C · 72.1 / 100
Unchanged since 2026-10-06.
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 no change
Top three things to fix
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
This was measured over a realtime sampling window, so it has no feed-wide share.
Effort: Usually a vendor support ticket.
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.
Remove retired stops from the export, or add them back to the trips that should serve them.
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
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: A review pass in your scheduling software.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Alaska 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
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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 stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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 200 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
- http://gtfs.muni.org/People_Mover.gtfs.zip
- Last checked
- 2026-10-07
- Service window
- 200 days of service data remain. Last service date 2027-04-25.
- Feed version
- 20260910
- Location
- Alaska
Part of the Alaska 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.4, validator 8.0.1.