Feed status · checked 2026-08-01
Dodger Area Rapid Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Iowa.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 3 hours ago; last changed 10 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top 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.Likely your team
148 of 148 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
76 of 76 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 148 of 148 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
- 76 of 76 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 152 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The validator found no problems in this feed. That is rare and worth celebrating.
Service data covers the next 152 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, 4, 6).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
110 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("N 11th St and Central Ave", "N 11th St and 2nd Ave N", "6th Ave N and N 11th St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 148 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (yellow)
- 2 (gray)
- 3 (orange)
- 4 (teal)
- 5 (yellow)
- 6 (orange)
| Route | Type | Line color |
|---|---|---|
| 1 Community College / Hospital | Bus | yellow |
| 2 Palace Park | Bus | gray |
| 3 Feelhaver / North 15th Street | Bus | orange |
| 4 High School / Cooper | Bus | teal |
| 5 Pleasant Valley / Highland Park | Bus | yellow |
| 6 Crossroads Center | Bus | orange |
List every stop
- Trinity Hospital
- Friendship Haven
- ICCC
- Lifeworks
- Ave C and C St
- Public Library
- Hawley Lions Park
- Palace Park
- 2nd St and Hawkeye Ave
- AFES
- Starlite
- Hawkeye Ave and 2nd St
- Village Green
- Feelhaver School
- Evergreen Estates
- Duncombe School
- N 15th St and Floral Ave
- St Edmond Catholic School
- Fort Dodge Senior High School
- Fort Dodge Middle School
- Cooper School
- Hy-Vee Wine and Sprits
- Northridge Apartments
- Knollcrest
- Highland Park
- Deer Creek
- S 14th St and 5th Ave (St. Paul's School)
- Sacred Heart
- Butler School
- Community Christian School
- Fort Frenzy
- Wal-Mart
- Target
- Hy-Vee
- Crossroads Mall
- Fareway/Blanden
- Trolley Center
- 3rd Ave NW and 11th St NW
- 3rd Ave NW and 11th St NW
- 3rd Ave NW and 7th St NW
- 3rd Ave NW and 7th St NW
- 5th St NW and 4th Ave NW
- Riverside St NW and 6th Ave NW
- 2nd St NW and Hawkeye Ave
- 2nd St NW and 5th Ave NW
- Hawkeye Ave and 7th Ave N
- 7th Ave N and Hawkeye Ave
- N 3rd St and 10th Ave N
- 11th Ave N and N 7th St
- N 7th St and Dakota St
- 5th Ave N and 4th Ave N
- 1st Ave N and N 3rd St
- 1st Ave N and N 7th St
- 1st Ave N and N 7th St
- S 7th St and 2nd Ave S
- S 7th St and 4th Ave S
- S 8th St and Kenyon Rd
- S 8th St and Kenyon Rd
- Kenyon Rd and Ave C
- Kenyon Rd and Ave C
- Museum Rd and Kenyon Rd
- Kenyon Rd and Tower Dr
- ICCC Stop 2
- A St and Ave O W
- A St and Ave G
- A St and Ave D
- Ave C and G St
- Ave C and J St
- N 11th St and Central Ave
- N 11th St and 2nd Ave N
- 6th Ave N and N 11th St
- 6th Ave N and N 14th St
- 6th Ave N and N 17th St
- N 15th St and 9th Ave N
- Floral Ave and N 19th St
- N 22nd St and Timberlane
- 16th Ave N and N 24th St
- 18th Ave N and N 27th St
- N 29th St and N 30th St
- Kramme Dr and Elmhurst Ave
- N 25th St and 6th Ave N
- 2nd Ave N and N 19th St
- 2nd Ave N and N 22nd St
- 2nd Ave N and N 25th St
- 2nd Ave N and N 26th St (Rd Mitchell Park)
- 4th Ave North at Garden Village Apts
- N 29th St and 2nd Ave N
- N 15th Ave and 20th Ave N
- N 15th St and 28th Ave N
- 28th Ave N and N 15th St
- Williams Dr and 28th Ave N
- Williams Dr and 25th Ave N
- Williams Dr and 20th Ave N
- 14th Ave N and Williams Dr
- 12th Ave N and N 9th St
- N 9th St and 8th Ave N
- N 9th St and 5th Ave N
- 2nd Ave N and N 9th St
- 3rd Ave S and S 9th St
- 3rd Ave S and S 12th St
- 3rd Ave St and S 15th St
- 3rd Ave S and S 19th St
- 5th Ave S and S 21st St
- S 25th St and 5th Ave S
- 8th Ave S and S 29th St (Wood Plaza)
- S 31st St and 8th Ave S
- 5th Ave S and S 31st St
- Kohl's
- Goodwill
- Crossroads Mall Entrance/Younkers
- 1st Ave S and S 31st St
- 1st Ave S and N 23rd St
- 1st Ave S and S 20th St
- 1st Ave S and S 16th St
- Central Ave and S 13th St
- N 15th St and Floral Ave
- N 15th St and 9th Ave N
- N 15th St and 5th Ave N
- 2nd Ave N and N 15th St
- N 12th St and 2nd Ave N
- 11th Ave SW and 12th St SW (Crimmins Field)
- 11th Ave SW and 15th St SW
- 12th Ave SW and 17th St SW
- S 15th St and 15th Ave SW
- S 15th St and 18th Ave S
- S 15th S and 21st Ave S
- S 22nd St and 22nd Ave S
- S 22nd St and 19th Ave S
- National Gypsum
- S 22nd St and 14th Ave S
- S 25th St and 13th Ave S
- 12th Ave S and S 22nd St
- S 18th St and 12th Ave S
- S 22nd St and 8th Ave S
- 6th Ave S and S 21st St
- 6th Ave S and S 18th St
- Fort Dodge Housing Authority
- 8th Ave S and S 16th St
- Dodger Stadium
- S 7th St and Meriwether Dr
- 12th Ave N and Knollcrest Dr
- Sacred Heart
- 8th Ave N at N 7th St
- 8th Ave N at N 7th St
- 8th Ave N at N 3rd St
- Exposition Park
- N 11th St and Central Ave
- Central Ave and S 13th St
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 87.4 | first check |
| 2026-07-30 | 87.4 | no change |
| 2026-07-31 | 87.4 | no change |
| 2026-08-01 | 87.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
2 findings, ordered by severity.
Show every finding
- Warning148 instances
148 of 148 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning76 instances
76 of 76 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
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 152 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 your 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.
- shapes.txt covers your trips Ready
- All 76 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 151 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 100 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/dodger-area-rapid-transit/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.