Feed status · checked 2026-08-01
Charles County VanGo
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Maryland.
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 41 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
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1801 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time timepoint without times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
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
370 of 370 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
This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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
- Service data ended 1801 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- 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
- Stop time timepoint without times (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 370 of 370 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
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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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. Self-check a feed before you publish.
Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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. Self-check a feed before you publish.
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. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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. Self-check a feed before you publish.
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 was 1801 days ago.
- 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
- No fare information is published in the feed.
- 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 your vendor a fix request
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 10 kinds of issue across 232 instances (174 error, 54 warning, 4 informational).
Service data ended 1801 day(s) ago. Trip planners have likely already dropped this feed.
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 not 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 (St. Charles A, Berry Road, St. Charles B, Charlotte Hall).
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.
284 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("301 Park & Ride Transfer Point", "Stone Ave & Smallwood Dr", "Stone Ave & Garner Ave", 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.
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 370 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.
- La Plata (red)
- Berry Road (gray)
- Business A (teal)
- Business B (teal)
- Bryans Road (black)
- Charlotte Hall (gray)
- Indian Head (black)
- Newburg (purple)
- Pinefield (gray)
- St. Charles A (green)
- St. Charles B (green)
- St. Charles C (yellow)
- Brandywine Connector (red)
- Nanjemoy (orange)
- St. Charles D (yellow)
- 301 Connector (red)
| Route | Type | Line color |
|---|---|---|
| La Plata | Bus | red |
| Berry Road | Bus | gray |
| Business A | Bus | teal |
| Business B | Bus | teal |
| Bryans Road | Bus | black |
| Charlotte Hall | Bus | gray |
| Indian Head | Bus | black |
| Newburg | Bus | purple |
| Pinefield | Bus | gray |
| St. Charles A | Bus | green |
| St. Charles B | Bus | green |
| St. Charles C | Bus | yellow |
| Brandywine Connector | Bus | red |
| Nanjemoy | Bus | orange |
| St. Charles D | Bus | yellow |
| 301 Connector | Bus | red |
List every stop
- Mall Circle (Toys ""R"" Us)
- Acton Ln & Tawney Dr
- Acton Ln & Tred Avon Ct
- Andrew's Auto Parts
- Rt 5 & Burnt Store Rd
- Aqualand
- Bannister Cir & Cooper Ct
- Bannister Cir & Hunt Pl
- Bannister Cir & Oakley Dr
- Bannister Cir & Vaughn Ct
- Beecher Ave & Jennifer Dr
- Bel Alton Motel
- Bensville Rd & Bancroft Dr
- Bensville Rd & Billingsley Rd (Indian Head)
- Bensville Rd & Eutaw Forest Dr (Indian Head)
- Bensville Rd & Grey Run Dr
- Bensville Rd & Laurel Branch Dr
- Berry Rd & Ashford Dr
- Berry Rd & Bensville Rd
- Berry Rd & Briarwood Dr
- Berry Rd & Buttonbush Dr
- Berry Rd & Cassidy St
- Berry Rd & Chestnut Dr
- Berry Rd & Community Dr
- Berry Rd & Greenmont Dr
- Berry Rd & Greenwood Dr
- Berry Rd & Ironwood Dr
- Berry Rd & Kanegis Dr
- Berry Rd & Leyton Ct
- Berry Rd & McDaniel Rd
- Berry Rd & Mill Hill Rd
- Berry Rd & Sharperville Pl
- Berry Rd & Stavors Rd
- Berry Rd & Streamview Dr
- Berry Rd & Sun Valley Dr
- Berry Rd & Trumpeter Ct
- Berry Rd & Western Pkwy (WaWa)
- Berry Rd & Westwood Dr
- Bicknell Rd & Pisgah/Marbury Rd
- Billingsley Rd & Countryside Ln
- Billingsley Rd & Highgrove Dr
- Billingsley Rd & Livingston Rd
- Billingsley Rd & Maintenance Pl
- Billingsley Rd & Middletown Rd
- Billingsley Rd & Old Washington Rd
- Billingsley Rd & Piney Church Rd (Charlotte Hall)
- Billingsley Rd & Prestancia Pl
- Billingsley Rd & Prince Edward Dr
- Billingsley Rd & Silent Creek Rd (Indian Head)
- Billingsley Rd & Southwinds Dr
- Billingsley Rd & St Francis Dr
- Billingsley Rd & St Martin's Dr
- Blair Rd & Strauss Ave
- Bowie Rd & Gilroy Rd
- Brandywine Crossing (Costco)
- Brandywine Crossing (Xscape 14)
- Bryans Rd McDonalds (Indian Head)
- Bryans Rd Shopping Center (Indian Head)
- Bryantown Mall
- Business Park Dr
- Cambridge
- Capt Dement Dr & Bensville Rd (Indian Head)
- Cenna Center
- Charles County Health Department
- Charles County Plaza (Giant)
- Charles County Plaza
- Charles St & Kent Ave
- Charles St & St Marys Ave (Courthouse)
- Chicamuxen Rd & Bicknell Rd
- Civista Medical Center
- Clymer Dr & Albert Rd
- College of Southern Maryland
- Copley Ave & Belfast Rd
- Copley Ave & Industrial Park Dr
- Copley Ave & Acadia Rd
- Country Ln & Spruce St
- Dartmouth Rd & Kipling Dr
- Davis Rd & Bunker Hill Rd
- Department of Community Services (Nanjemoy)
- Department of Social Services
- Dorchester Cir & Parrotfish Ct
- Dorchester Cir & St Phillips Dr
- Dorchester Cir & Tarpon Ct
- Dorchester St & Potomac St
- Elite Gymnastics
- Festival at Waldorf
- Food Lion
- Food Lion
- Food Lion on Old Washington Rd
- Garner Ave & Copley Ave
- Garner Ave & Fillmore Rd
- Garner Ave & Marshall Rd
- Garner Ave & Van Buren Rd
- Garner Ave & Wilson Rd
- Gilroy Rd & Chicamuxen Rd
- Glen Albin Rd & Patuxent Ct
- Golden Corral
- Hamilton Rd & Firethorne St
- Hamilton Rd & Flora Springs St
- Hamilton Rd & Moran Dr
- Hamilton Rd & Stoney Cover Dr
- Hamilton Rd & Wildmeadows St
- Hampshire Cir & St. Anthony's Dr
- Hampton Ct (Indian Head)
- Hampshire Cir & Impala Ct
- Hanson Community Center
- Harford St & Washington Ave
- Hawthorne Dr (CVS)
- Hawthorne Rd & Magnolia Dr (Genesis)
- Hawthorne Rd & Marshall Corner Rd
- Hawthorne Rd & Rt 301 N
- Henson Community Center
- Heritage Green Pkwy & Lelia Ct
- Heritage Green Pkwy & Morris Dr
- Heritage Pl @ St Ignatius Dr
- Huntington Cir & Heathcote
- Huntington Cir & Light Arms Pl
- Huntington Cir & Post Office Rd
- Industrial Park Dr & Copley Ave
- Industrial Park Dr & Irongate Dr
- Industrial Park Dr & Rockefeller Ct
- Ironsides Rd & Baptist Church Rd
- Ironsides Store
- JRJ Income Tax Building
- Jaycees Apartments
- Rt 301 N & Smitty Dr
- Josephine Rd & Pinewood Dr
- Jude House
- Kent Ave & Caroline Dr
- Kent Ave & Hawthorne Rd
- Kenwood Building
- Kipling Dr & Jubilee Way
- La Plata Manor
- La Plata Professional Building
- LaPlata Library
- La Plata Professional Building (SB)
- LaPlata Transfer Point (Walmart Lot)
- Lancaster Cir & Bluebird Dr
- Lancaster Cir & Gamebird Ct
- Hampshire Cir & Red Fox Ln
- Lancaster Cir & Smallwood Dr
- Lexington Rd & Montpelier Dr
- Livingston Rd & Pomfret Rd
- Livingston Rd (Shell Gas Station)
- MVA (entrance)
- Maples Apartments on Rt 301 S
- Maples Apartments
- Marshall Corner Rd & Hawthorne Rd
- Marshall Corner Rd & Pomfret Rd
- Marshall Hall Rd & Arbor Ln
- Mason Springs Rd & Poorhouse Rd
- Mattawoman-Beantown Park and Ride
- Mattawoman-Beantown Rd & Council Oak Dr
- Mattawoman-Beantown Rd & Idlewood Park Rd
- Mattawoman-Beantown Rd & Indian Ln
- McDonalds (Rt 301 S ONLY)
- McDonalds on Rt 301 S
- McDonough High School
- McKays
- Melwood
- Michael Rd & Country Ln
- Middletown Rd & Biltmore St
- Middletown Rd & Ethridge Dr
- Mill Hill Rd & Homecoming Ln
- Mitchell Rd & Hawthorne Rd
- Nanjemoy Community Center
- New Post Professional Building
- North Point Complex
- Oak Ave & Worchester St
- Oak Ave (Milton Somers Community Center)
- Oakley Dr & Wakefield Cir
- October Pl & Smallwood Dr
- Old Line Center
- Old Washington Rd & Oak Manor Dr
- Old Washington Rd & Sub Station Rd
- PD Brown Library
- Pierce Rd & Western Pkwy
- Pinecone Cir & Huntington Woods Dr
- Pinecone Cir & White Fir Ct
- Pinecone Cir& Primrose Dr
- Pinefield Rd & Alfred Dr
- Pinefield Rd & Josephine Rd
- Pinefield Rd & Lisa Dr
- Pinefield South Shopping Center
- Pinewood Dr & Michael Rd
- Pisgah/Marbury Rd & Mason Springs Rd
- Pomfret Rd & Livingston Rd
- Pomfret Rd & Marshall Corner Rd
- Pomfret Rd & Preston Ln
- Pomfret Rd & Preston Ln
- Poorhouse Rd & Rt 6
- Poseytown Rd & Bowie Rd
- Post Office Rd & Copley Ave
- Post Office Rd & Henry Ford Cir
- Post Office Rd & Huntington Cir
- Post Office Rd & October Pl
- RT 301 N & Demarr Rd
- RT 301 N & Hickory Ln
- Radio Station Rd (La Plata High School)
- Randy's Ribs & BBQ
- Red Top Store
- Relax Inn
- Richard R. Clark Senior Center
- Rips on Rt 301 S
- Riverside Rd & Holly Springs Rd
- Riverside Rd & Maryland Pt Rd
- Robert Stethem Education Center
- Rosewick Rd & Radio Station Rd
- Route 301 S & Billingsley Rd
- Rt 210 N & Metropolitan Church Rd
- Rt 210 S & Cedar Ln
- Rt 210 S & Marshall Hall Rd (McDonalds)
- Rt 210 S & McWilliams Dr
- Rt 210 S & South Hampton Dr
- Rt 301 N & Centennial St
- Rt 301 N & Central Ave
- Rt 301 N & Fairgrounds Rd
- Rt 301 N & Faulkner Rd
- Rt 301 N & Hawthorne Rd (CVS)
- Rt 301 N & Ridley Dr
- Rt 301 N & Rosewick Rd
- Rt 301 N & Rt 257 (Hardesty's Store)
- Rt 301 N & St Mary's Ave
- Rt 301 N ( Olive Garden)
- Rt 301 N (Cracker Barrel/Carraba's)
- Rt 301 S & Balsam Run
- Rt 301 S & Business Park Dr
- Rt 301 S & Catalpa Dr
- Rt 301 S & Cherry Ln
- Rt 301 S & Cliffton Dr
- Rt 301 S & Crossover Rd
- Rt 301 S & Edge Hill Rd
- Rt 301 S & Gillespie Cir
- Rt 301 S & Old Stagecoach Rd
- Rt 301 S & Oriole Ln
- Rt 301 S & Pierce Rd
- Rt 301 S & Popes Creek Rd
- Rt 301 S & Preference Dr
- Rt 301 S & Rosewick Rd
- Rt 301 S & S Faulkner Rd
- Rt 301 S & Sadie Ln
- McDonalds
- Rt 5 N & Aubrey James Sr Pl
- Rt 5 N & Billingsley Rd
- Rt 5 N & Olivers Shop Rd
- Rt 5 N & Sapp Pl
- Rt 5 N Ted Bowling Rd
- Rt 5 S & Rooselvelt Pl
- Rt 5 S & Wolfe Dr
- Rt 5 S & Zachia Manor Ct
- and 120 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 | 26.0 | first check |
| 2026-07-30 | 26.0 | no change |
| 2026-07-31 | 26.0 | no change |
| 2026-08-01 | 26.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
16 findings, ordered by severity.
Show every finding
- Error174 instances
Stop time timepoint without times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_time_timepoint_without_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1801 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning370 instances
370 of 370 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)
- Warning218 instances
218 of 218 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)
- Warning212 instances
212 of 218 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning30 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning16 instances
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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · 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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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 Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1801 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 1801 days ago, so FTA would find the link out of date.
- 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 218 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. 1 validator error to resolve. Service data expired 1801 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 1801 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 174 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 43 / 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 0 / 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 23 / 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/charles-county-vango/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.