Call-prep brief · checked 2026-11-09
Elevated Transit
Grade C · 71.4 / 100 · partial: freshness not measured
The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.
Scored from a Mobility Database mirror copy downloaded on 2026-10-02, because the feed URL on file could not be downloaded. Service dates in that copy run 2017-01-01 to 2017-06-01. It may not match the feed the agency publishes today.
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
The scoring methodology changed since the prior check. Category deltas restart with this scorecard.
Top three things to fix
Check that https://transitfeeds.com/p/elevated-transit/609/latest/download still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://transitfeeds.com/p/elevated-transit/609/latest/download, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2017-06-01, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
Effort: Usually a server or hosting setting, not a change to the feed itself.
Add the required column named in the finding to the flagged file.
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
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 an export setting; ask your vendor if it recurs.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
25 of 25 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 25 stops in the feed.
Effort: A column in stops.txt; your scheduling software likely has it.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Utah 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
- The feed URL on file, https://transitfeeds.com/p/elevated-transit/609/latest/download, could not be downloaded: the server answered with an error instead of the file.
- Next action
- Check that https://transitfeeds.com/p/elevated-transit/609/latest/download still serves your current feed. If the feed moved, publish the new address.
- 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
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- 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
- 25 of 25 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
NTD GTFS readiness: Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. No service end date could be read, so currency is unknown.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- No service end date could be read, so currency is unknown.
- 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://transitfeeds.com/p/elevated-transit/609/latest/download
- Last checked
- 2026-11-09
- Service window
- Expiry date not stated in the feed.
- Location
- Utah
Part of the Utah 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.