Feed status · checked 2026-08-01
Arlington Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Virginia.
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 5 hours ago; last changed 42 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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
574 of 574 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
2116 of 2116 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
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.Likely your export tool
Some values have extra spaces at the start or end. A stray space can break a match, so a stop or route may fail to link across files.
⏱ Usually one export setting.worth about +8 points in its category
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
- 574 of 574 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
- 2116 of 2116 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
- Feed evidence
- Some values have extra spaces at the start or end.
- Next action
- Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
- 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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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.
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 303 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 6 kinds of issue across 15366 instances (0 error, 15366 warning, 0 informational).
Service data covers the next 303 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.
1 accessibility depth signal
573 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("S CARLIN SPRINGS RD NB @ COLUMBIA PIKE FS", "S ARLINGTON MILL DR EB @ S TAYLOR ST NS", "S ARLINGTON MILL DR WB @ S TAYLOR ST FS", 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.
Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 574 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.
- 41 (white)
- 42 (white)
- 43 (white)
- 45 (white)
- 51 (white)
- 52 (white)
- 55 (white)
- 56 (white)
- 72 (white)
- 74 (white)
- 75 (white)
- 77 (white)
- 84 (white)
- 87 (white)
| Route | Type | Line color |
|---|---|---|
| 41 Arlington Mill-Ballston-Crthous | Bus | white |
| 42 Ballston-Pentagon-Pentagon Cty | Bus | white |
| 43 Courthouse-Rosslynn-Crystal Cty | Bus | white |
| 45 Arlington Mill -Sequoia-Rosslyn | Bus | white |
| 51 Ballston-Virginia Hosp- Langston | Bus | white |
| 52 Ballston-VA Hosp-E Flls Chrch | Bus | white |
| 55 Rosslyn-East Falls Church | Bus | white |
| 56 ROSS to MACE | Bus | white |
| 72 Rock Spring-Ballston-Shirlingtn | Bus | white |
| 74 Arlington Vlg-Arlington Vw-Pent | Bus | white |
| 75 Shirlingtn-Ballstn-Virginia Sq | Bus | white |
| 77 Shirlingtn-Lyon Park-Courthouse | Bus | white |
| 84 Douglas Prk-Green Vly-Pntgn Cty | Bus | white |
| 87 Shirlingtn-Army Navy Dr-Pentagn | Bus | white |
List every stop
- S GLEBE RD WB @ S MEADE ST FS
- COLUMBIA PIKE WB @ S BARTON ST FS
- COLUMBIA PIKE EB @ S BARTON ST FS
- S GEORGE MASON DR SB @ 6TH ST S FS
- S CARLIN SPRINGS RD NB @ 3RD ST S NS
- S WALTER REED DR NB @ 9TH ST S NS
- ARMY NAVY DR NB AT 1300
- S CARLIN SPRINGS RD SB @ 3RD ST S NS
- ARMY NAVY DR SB ACROSS FROM 1300
- S GEORGE MASON DR NB @ 6TH ST S FS
- S WALTER REED DR SB @ 9TH ST S NS
- S FOUR MILE RUN DR EB @ S NELSON ST NS
- COLUMBIA PIKE EB @ S SCOTT ST NS
- S COURTHOUSE RD SB @ 9TH ST S FS
- S GLEBE RD SB @ 8TH ST S NS
- S GEORGE MASON DR NB @ 4TH ST S NS
- S COURTHOUSE RD NB @ COLUMBIA PIKE FS
- S CARLIN SPRINGS RD NB @ 1ST ST S NS
- S GEORGE MASON DR SB @ 4TH ST S NS
- ARMY NAVY DR WB @ S FERN ST NS
- S WALTER REED DR NB @ S WAKEFIELD ST FS
- ARMY NAVY DR EB @ S LYNN ST NS
- S GLEBE RD NB @ 7TH ST S NS
- ARMY NAVY DR WB @ S LYNN ST FS
- S WALTER REED DR NB @ 8TH ST S NS
- ARMY NAVY DR WB @ S HAYES ST FS
- ARMY NAVY DR WB @ S JOYCE ST NS
- S WALTER REED DR SB @ 8TH ST S NS
- COLUMBIA PIKE EB @ S ORME ST FS
- S GLEBE RD EB ACROSS FROM SHIRLEY PARK SHOPPING CE
- S GLEBE RD SB @ 6TH ST S NS
- COLUMBIA PIKE WB @ S ORME ST NS
- S GLEBE RD NB @ 6TH ST S FS
- S COURTHOUSE RD SB @ 8TH ST S NS
- S GEORGE MASON DR NB AT NATIONAL GUARD READINESS C
- S COURTHOUSE RD NB @ 8TH ST S NS
- S GEORGE MASON DR SB ACROSS FROM NATIONAL GUARD RE
- S WALTER REED DR NB @ 6TH ST S NS
- S WALTER REED DR SB @ S WAKEFIELD ST FS
- S GLEBE RD NB @ S OLD GLEBE RD NS
- S GLEBE RD SB @ 2ND ST S NS
- S GLEBE RD NB @ 1ST RD S NS
- S GEORGE MASON DR NB @ ARLINGTON BLVD NS
- S COURTHOUSE RD SB @ 6TH ST S NS
- N GEORGE MASON DR SB @ ARLINGTON BLVD NS
- N GEORGE MASON DR NB @ ARLINGTON BLVD FS
- S GLEBE RD SB @ ARLINGTON BLVD FS
- SHIRLINGTON RD EB @ KEMPER RD FS
- S GLEBE RD NB @ ARLINGTON BLVD NS
- S COURTHOUSE RD NB @ 2ND ST S NS
- N GEORGE MASON DR NB @ N PERSHING DR FS
- N GLEBE RD SB @ N PIEDMONT ST FS
- N GLEBE RD NB @ N PIEDMONT ST NS
- N GEORGE MASON DR NB @ HENDERSON RD NS
- N GEORGE MASON DR SB @ HENDERSON RD FS
- N GLEBE RD SB @ N PERSHING DR FS
- N GLEBE RD NB @ N PERSHING DR NS
- HENDERSON RD NB @ N THOMAS ST NS
- S FOUR MILE RUN DR WB @ S OAKLAND ST FS
- N GLEBE RD NB @ 3RD RD N NS
- HENDERSON RD SB @ N THOMAS ST FS
- N GLEBE RD NB @ 4TH ST N NS
- N GLEBE RD SB @ 4TH ST N NS
- WASHINGTON BLVD SB @ ARLINGTON BLVD NS
- N GLEBE RD SB @ HENDERSON RD NS
- N GLEBE RD NB @ N QUINCY ST FS
- WILSON BLVD EB @ N JEFFERSON ST FS
- WASHINGTON BLVD NB @ N WAYNE ST NS
- WILSON BLVD EB @ N HARRISON ST NS
- S ARLINGTON MILL DR WB @ 28TH RD S NS
- WILSON BLVD WB @ N HARRISON ST NS
- WILSON BLVD EB @ N GREENBRIER ST NS
- WILSON BLVD WB @ N GREENBRIER ST NS
- WASHINGTON BLVD NB @ N BARTON ST FS
- WASHINGTON BLVD SB @ BROOKSIDE DR FS
- WILSON BLVD EB @ N EMERSON ST NS
- WILSON BLVD WB @ N FREDERICK ST NS
- WILSON BLVD EB @ N GEORGE MASON DR NS
- WILSON BLVD WB @ N GEORGE MASON DR FS
- S FOUR MILE RUN DR EB @ S OXFORD ST NS
- WASHINGTON BLVD SB @ 3RD ST N NS
- N RANDOLPH ST NB @ WILSON BLVD NS
- WILSON BLVD EB @ N ABINGDON ST NS
- WILSON BLVD WB @ N ABINGDON ST FS
- WASHINGTON BLVD NB @ N BRYAN ST NS
- WILSON BLVD EB @ N WAKEFIELD ST FS
- WILSON BLVD WB @ N WAKEFIELD ST NS
- WILSON BLVD WB @ N RANDOLPH ST NS
- WILSON BLVD EB @ N QUINCY ST FS
- S FOUR MILE RUN DR WB @ S OXFORD ST MB
- WILSON BLVD WB @ N TAYLOR ST NS
- WILSON BLVD WB @ N POLLARD ST NS
- WASHINGTON BLVD NB @ N PERSHING DR NS
- N RANDOLPH ST SB @ 9TH ST N FS
- N BARTON ST SB @ N PERSHING DR NS
- WASHINGTON BLVD SB @ N PERSHING DR FS
- N BARTON ST NB @ N PERSHING DR FS
- WILSON BLVD WB @ N OAKLAND ST FS
- WILSON BLVD EB @ N OAKLAND ST FS
- FAIRFAX DR EB @ N VERMONT ST FS
- 28TH ST S EB AT 1334
- FAIRFAX DR EB @ N TAYLOR ST NS
- WILSON BLVD WB @ N MONROE ST FS
- FAIRFAX DR WB @ N UTAH ST FS
- WASHINGTON BLVD NB @ 9TH ST N NS
- N BARTON ST NB @ 9TH ST N NS
- WILSON BLVD EB @ N KENMORE ST NS
- WILSON BLVD WB @ N KANSAS ST NS
- WASHINGTON BLVD SB @ 9TH ST N NS
- N BARTON ST SB @ 9TH ST N NS
- N GLEBE RD NB @ 11TH ST N NS
- 28TH ST S WB ACROSS FROM 1400
- WASHINGTON BLVD SB @ 10TH ST N NS
- N GLEBE RD NB @ WASHINGTON BLVD NS
- N GLEBE RD SB @ WASHINGTON BLVD FS
- WILSON BLVD EB @ 10TH ST N FS
- WILSON BLVD WB @ 10TH ST N NS
- WASHINGTON BLVD NB @ 10TH ST N FS
- WASHINGTON BLVD EB @ N EVERGREEN ST NS
- WASHINGTON BLVD WB @ N EVERGREEN ST MB
- WASHINGTON BLVD WB @ N BUCHANAN ST NS
- WASHINGTON BLVD EB @ N VERNON ST NS
- SHIRLINGTON RD NB @ 25TH ST S NS
- WASHINGTON BLVD EB @ N BUCHANAN ST NS
- WASHINGTON BLVD WB @ N VERNON ST NS
- WASHINGTON BLVD EB @ N UTAH ST FS
- WASHINGTON BLVD WB @ N GLEBE RD FS
- WASHINGTON BLVD WB @ N UTAH ST NS
- WASHINGTON BLVD EB @ N STAFFORD ST FS
- WASHINGTON BLVD WB @ N STAFFORD ST NS
- N SYCAMORE ST AT EAST FALLS CHURCH STATION BAY A
- CLARENDON BLVD EB @ N HIGHLAND ST NS
- WILSON BLVD WB @ N HERNDON ST NS
- SHIRLINGTON RD SB @ 25TH ST S FS
- N BARTON ST NB @ FAIRFAX DR NS
- CLARENDON BLVD EB @ N FILLMORE ST NS
- N SYCAMORE ST NB @ WASHINGTON BLVD FS
- N SYCAMORE ST SB @ WASHINGTON BLVD NS
- N BARTON ST SB @ FAIRFAX DR NS
- N GLEBE RD SB @ 15TH ST N NS
- N GLEBE RD NB @ 15TH ST N NS
- WILSON BLVD WB @ N FILLMORE ST NS
- CLARENDON BLVD EB @ N BARTON ST NS
- N BARTON ST SB @ CLARENDON BLVD NS
- 28TH ST S EB AT 1428
- N SYCAMORE ST NB @ 22ND RD N NS
- WILSON BLVD WB @ N DANVILLE ST NS
- N SYCAMORE ST SB @ LANGSTON BLVD FS
- N GLEBE RD SB @ 16TH ST N NS
- N GLEBE RD NB @ 16TH ST N NS
- CLARENDON BLVD EB @ N WAYNE ST NS
- WILSON BLVD WB @ N BARTON ST NS
- LANGSTON BLVD EB @ N ROOSEVELT ST NS
- CLARENDON BLVD EB @ N UHLE ST COURTHOUSE STATION
- WILSON BLVD WB @ N VEITCH ST NS
- S FOUR MILE RUN DR EB @ S WALTER REED DR NS
- LANGSTON BLVD EB @ N QUANTICO ST NS
- LANGSTON BLVD WB @ N QUANTICO ST FS
- LANGSTON BLVD EB @ N POTOMAC ST FS
- LANGSTON BLVD WB @ N POTOMAC ST NS
- CLARENDON BLVD EB @ N RHODES ST FS
- LANGSTON BLVD EB @ N POWHATAN ST FS
- N GLEBE RD NB @ 19TH ST N NS
- LANGSTON BLVD WB @ N POWHATAN ST NS
- N GLEBE RD SB @ 19TH ST N FS
- 28TH ST S WB AT 1501
- WILSON BLVD WB @ N RHODES ST FS
- LANGSTON BLVD EB @ JOHN MARSHALL DR FS
- CLARENDON BLVD EB @ N ODE ST FS
- LANGSTON BLVD WB @ JOHN MARSHALL DR FS
- LANGSTON BLVD EB @ N LEXINGTON ST FS
- LANGSTON BLVD EB @ N CLEVELAND ST FS
- LANGSTON BLVD WB @ N LEXINGTON ST NS
- LANGSTON BLVD WB @ N CLEVELAND ST FS
- LANGSTON BLVD EB @ N HIGHLAND ST NS
- S WALTER REED DR NB @ S RANDOLPH ST NS
- LANGSTON BLVD WB @ N HIGHLAND ST NS
- LANGSTON BLVD EB @ N ADAMS ST FS
- LANGSTON BLVD EB @ N JEFFERSON ST Across From
- N NASH ST NB @ WILSON BLVD MB
- LANGSTON BLVD WB @ N KENSINGTON ST NS
- N GLEBE RD NB @ 21ST ST N MB
- LANGSTON BLVD EB @ KIRKWOOD RD NS
- LANGSTON BLVD WB @ N VANCE ST NS
- LANGSTON BLVD EB @ N MONROE ST FS
- LANGSTON BLVD EB @ N VEITCH ST FS
- S FOUR MILE RUN DR WB @ S WALTER REED DR FS
- LANGSTON BLVD WB @ SPOUT RUN PKWY FS
- LANGSTON BLVD WB @ N LINCOLN ST NS
- LANGSTON BLVD EB @ N HARRISON ST NS
- LANGSTON BLVD EB AT 3206
- LANGSTON BLVD WB @ N HARRISON ST FS
- LANGSTON BLVD EB @ N RHODES ST NS
- LANGSTON BLVD EB @ N OAKLAND ST FS
- LANGSTON BLVD EB @ N GEORGE MASON DR FS
- LANGSTON BLVD EB @ N EDISON ST NS
- LANGSTON BLVD WB @ N GEORGE MASON DR FS
- S WALTER REED DR SB @ S RANDOLPH ST FS
- LANGSTON BLVD WB @ N EDISON ST NS
- LANGSTON BLVD WB @ N CULPEPER ST NS
- N GLEBE RD SB @ 21ST ST N NS
- LANGSTON BLVD EB @ N CULPEPER ST FS
- LANGSTON BLVD EB @ N QUINCY ST FS
- CHERRY HILL RD WB @ N TAYLOR ST NS
- CHERRY HILL RD EB @ N STAFFORD ST NS
- CHERRY HILL RD EB @ N RANDOLPH ST FS
- S CARLIN SPRINGS RD NB @ COLUMBIA PIKE FS
- S KENMORE ST NB @ 24TH ST S NS
- N GLEBE RD NB @ LANGSTON BLVD NS
- LANGSTON BLVD EB @ N GLEBE RD NS
- CHERRY HILL RD EB @ N THOMAS ST MB
- CHERRY HILL RD WB @ N THOMAS ST NS
- LANGSTON BLVD WB @ N SCOTT ST NS
- LANGSTON BLVD WB @ N GLEBE RD NS
- N GLEBE RD SB @ LANGSTON BLVD NS
- LANGSTON BLVD EB @ N QUINN ST FS
- ARMY NAVY DR SB ACROSS FROM 2455
- CHERRY HILL RD EB @ N VERMONT ST NS
- LANGSTON BLVD EB @ FORT MYER DR NS
- CHERRY HILL RD WB @ LORCOM LN NS
- CHERRY HILL RD EB @ N WOODROW ST NS
- LANGSTON BLVD WB @ N OAK ST NS
- LANGSTON BLVD WB @ N NASH ST MB
- N GLEBE RD NB @ 24TH ST N NS
- N GLEBE RD SB @ 24TH ST N NS
- N GLEBE RD NB @ 25TH ST N NS
- 26TH ST S NB @ S TROY ST FS
- N GLEBE RD SB @ 25TH ST N NS
- N GLEBE RD NB @ 26TH ST N FS
- N GLEBE RD SB @ 26TH ST N NS
- ARMY NAVY DR EB @ S JOYCE ST FS
- S GLEBE RD WB AT SHIRLEY PARK SHOPPING CENTER
- 26TH ST S SB @ 25TH ST S FS
- 26TH RD S WB @ S GLEBE RD MB
- S WALTER REED DR NB @ COLUMBIA PIKE NS
- SHIRLINGTON RD WB @ S FOUR MILE RUN DR NS
- 26TH RD S EB @ S GLEBE RD MB
- S KENMORE ST SB @ 24TH ST S NS
- 26TH ST S SB @ S TROY ST NS
- 26TH ST S NB @ S VEITCH ST NS
- LANGSTON BLVD WB @ N OAKLAND ST NS
- LANGSTON BLVD WB @ N HARRISON ST NS
- N SYCAMORE ST AT EAST FALLS CHURCH STATION BAY D
- LANGSTON BLVD EB @ N GREENBRIER CT NS
- N BARTON ST SB @ 10TH ST N NS
- N BARTON ST NB @ 10TH ST N FS
- CLARENDON BLVD EB @ N DANVILLE ST NS
- CRYSTAL DR NB @ 18TH ST S FS-TRANSITWAY STATION E
- 28TH ST S SB @ 26TH ST S FS
- N STUART ST NB AT BALLSTON STATION BAY C
- and 324 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 73.3 | first check |
| 2026-07-30 | 73.3 | no change |
| 2026-07-31 | 73.3 | no change |
| 2026-08-01 | 73.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning13662 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2116 instances
2116 of 2116 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)
- Warning1699 instances
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.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning574 instances
574 of 574 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)
- Warning2 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info557 instances
About 557 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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 303 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) Different (allowed)
- Your feed's agency_id is 1; your National Transit Database ID is 30080. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 1 to NTD ID 30080, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 2116 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 303 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1 of 574 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 15s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 302 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 68 / 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 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/arlington-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.