Feed status · checked 2026-08-01
Annapolis Transit
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 1 days ago; last changed 38 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 1826 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
237 of 237 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 1826 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
- 237 of 237 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 1826 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 16111 instances (16036 error, 69 warning, 6 informational).
Service data ended 1826 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
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Orange, Gold).
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.
218 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("West St. and Calvert St.", "West St. at Loews Hotel", "West St. and Madison Pl.", 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 237 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.
- Orange (orange)
- Gold (yellow)
- Yellow (yellow)
- Green (green)
- Brown (brown)
- Red (red)
- Purple-S (purple)
- Circulator (teal)
- State Shuttle (teal)
- Purple-N (purple)
| Route | Type | Line color |
|---|---|---|
| Orange Downtown Annapolis to Forest Drive | Bus | orange |
| Gold Edgewater to Arnold/AACC | Bus | yellow |
| Yellow Westfield Mall to Harbour Center | Bus | yellow |
| Green Westfield Mall to Eastport | Bus | green |
| Brown Westfield Mall to Eastport | Bus | brown |
| Red Westfield Mall to Eastport | Bus | red |
| Purple-S Westfield Mall to Eastport | Bus | purple |
| Circulator | Bus | teal |
| State Shuttle | Bus | teal |
| Purple-N Westfield Mall to Eastport | Bus | purple |
List every stop
- 6th St. at Spa Creek Bridge
- Admiral Cochrane Dr. and Solomons Island Rd.
- Admiral Dr. and Poplar Ave.
- Admiral Dr. and Poplar Ave.
- Admiral Dr. and Captains Cir.
- Admiral Dr. and Croll Dr.
- Bay Ridge Ave. at Bens Dr.
- Bay Ridge Ave. and Janice Dr.
- Bay Ridge Rd. and Cypress Rd.
- Bay Ridge Rd. and Cypress Rd.
- Bay Ridge Ave. and Janice Dr.
- Bay Ridge Ave. and Timber Creek Dr.
- Bay Ridge Ave. and Victor Pkwy.
- Bestgate Rd. and Harbour Gates Dr.
- Bestgate Rd. at Bestgate Park
- Bestgate Rd. at Research Dr.
- Bestgate Rd. Office Building
- Bywater Rd. and Forest Dr.
- Bywater Rd. and Great Bay Ave.
- Chesapeake Ave. and 4th St.
- Chesapeake Ave. and Burnside St.
- Chesapeake Ave. and Burnside St.
- Monroe St. and Bay Ridge Ave.
- Church Circle at Court House
- Church Circle & School St.
- St. Mary's St. and Compromise St.
- Copeland Street
- Defense Hwy. at Home Depot
- Defense Hwy. and Oak St.
- Forest Dr. and Hillsmere Dr.
- Forest Dr. and Harker Pl.
- Forest Dr. and Old Solomons Island Rd.
- Forest Dr. and Old Solomons Island Rd.
- Forest Dr. and Parole St.
- Forest Dr. and Castlegate Dr.
- Forest Dr. and Spa Rd.
- Hilltop Ln. and Boxwood Rd.
- Hilltop Ln. at Truxton Park
- Hilltop Ln. and Spa Rd.
- Hilltop Ln. and Youngs Farm Rd.
- Hilltop Ln. at Youngs Farm Rd.
- Tyler Ave. and President St.
- Housley Rd. at Stone Point Dr.
- Housley Rd. and Gateway Village Dr.
- Jennifer Rd. at Detention Center
- Jennifer Rd. at Detention Center
- Madison St. and Brashears St.
- Madison St. and President St.
- Chesapeake Ave. at Eastport Shopping Center
- President St. and Van Buren St.
- President St. and Madison St.
- Riva Rd. and Admiral Cochrane Dr.
- Riva Rd. and Holiday Ct.
- Riva Rd. at Claiborne Place
- Rowe Blvd. and Taylor Ave.
- Rowe Blvd. and Taylor Ave.
- Severn Ave. and 4th St.
- Department of Public Works
- Spa Rd. and Rosemary St.
- Spa Rd. and Carraway Ln.
- Spa Rd. and Carraway Ln.
- Tyler Ave. and Forest Dr.
- Tyler Ave. and Woods Dr.
- Tyler Ave. and President St.
- Robinwood Circle
- West St. and Westbridge Dr.
- West St. and Admiral Dr.
- West St. and Calvert St.
- West St. and Church Circle
- West St. and Lafayette Ave.
- West St. and Legion Ave.
- West St. and Madison Pl.
- West St. and Parole St.
- West St. and Somerville Rd.
- West St. and Cherry Grove Ave.
- West St. and Southgate Ave.
- West St. and Taylor Ave.
- West St. and Old Solomons Island Rd.
- West St. and Hudson St.
- Admiral Cochrane Dr. and Harry S. Truman Pkwy.
- Bywater Rd. at Annapolis Marketplace
- Bywater Rd. and Belle Dr.
- Medical Pkwy. at Sajak Building
- Bestgate Rd. and Severn Grove Rd.
- Newtowne Drive
- Route 2 and Admiral Cochrane Dr.
- Route 2 and Virginia Ave.
- Route 2 and Pike Ridge Rd.
- Ritchie Hwy. and Ritchie Rd.
- Ritchie Hwy. and Arnold Rd.
- Ritchie Hwy. and Joyce Ln.
- Ritchie Hwy. and Joyce Ln.
- Ritchie Hwy. and Arnold Rd.
- Ritchie Hwy. and Brice Rd.
- B&A Blvd. and King George St.
- City Hall / Noah Hillman Garage
- Bestgate Rd. at Commerce Park Dr.
- Bestgate Rd. and Lawrence Ave.
- Calvert St. and Bladen St.
- Chesapeake Ave. and State St.
- College Ave. at Lawyer's Mall
- Hilltop Ln. and Boxwood Rd.
- Hilltop Ln. and Primrose Rd.
- Harry S. Truman Pkwy. at Dept. of Aging
- West St. and Amos Garrett Blvd.
- West St. and Legion Ave.
- Newtowne Dr. and Juliana Cir.
- Jennifer Rd. at Annapolis Exchange
- Riva Rd. and Heritage Ct.
- Skippers Ln. and Vanguard Ln.
- Route 2 and Mayo Rd.
- Route 2 and Maryland Ave.
- Route 2 and South River Rd.
- AACC Loop Rd.
- Route 2 and Lee Airpark Dr.
- B&A Blvd. and Badger Rd.
- B&A Blvd. and Badger Rd.
- Admiral Dr. and Captains Cir.
- Bay Ridge Shopping Center
- Tyler Avenue
- K-Mart at South River Colony
- Westfield Mall
- West St. and Chinquapin Round Rd.
- Anne Arundel Medical Center
- President St. and Monroe St.
- Riva Rd. at Farmers Market
- Harry S. Truman Pkwy. at MVA
- Colonial Ave. and West St.
- West St. and Cathedral St.
- Main Street / City Dock
- West St. at Loews Hotel
- County Office Building / Gotts Garage
- Park Place
- Housley Rd. and Generals Hwy.
- Harry S. Truman Pkwy. at Water Treatment
- Anne Arundel County Dept. of Health
- Riva Rd. and Towne Centre Blvd.
- West St. and Russell St.
- Norman Dr. and Americana Dr.
- Hilltop Ln. and Forest Dr.
- Spa Rd. and Spindrift Way
- Forest Dr. and Crystal Spring Farm Rd.
- Forest Dr. and Spa Rd.
- Spa Rd. and Gentry Ct.
- Forest Dr. and Gemini Dr.
- Forest Dr. and Youngs Farm Rd.
- Forest Dr. at Annapolis Middle School
- Forest Dr. and Tyler Ave.
- Forest Dr. and Tyler Ave.
- Forest Dr. and Crows Nest Ct.
- Forest Dr. and Annapolis Neck Rd.
- Forest Dr. and Thom Dr.
- Forest Dr. and Quiet Waters Pl.
- Forest Dr. and Bay Ridge Ave.
- Bay Ridge Ave. at Bens Dr.
- Hilltop Ln. and Gemini Dr.
- Hilltop Ln. and Primrose Rd.
- Bay Ridge Ave. and Parkwood Ave.
- Chesapeake Ave. and 5th St.
- 6th St. and Bay Ridge Ave.
- Spa Rd. and Rosemary St.
- Ritchie Hwy. at Severn Commerce Center
- Ritchie Hwy. at Severna Park Golf Center
- Ritchie Hwy. and Old Frederick Rd.
- Ritchie Hwy. and Old Frederick Rd.
- Housley Rd. and Gateway Village Dr.
- Housley Rd. at Best Buy
- Housley Rd. at Regatta Bay Ct.
- Bestgate Rd. and Herndon Dr.
- Bestgate Rd. and Gate Dr.
- H&B Shopping Center
- Bestgate Rd. and Compton Dr.
- Bestgate Rd. and N. Bestgate Rd.
- Bestgate Rd. and Tidewater Colony Dr.
- Jennifer Rd. at Annapolis Plaza
- Forest Dr. and Tower Pl.
- Forest Dr. at Forest Plaza
- Forest Dr. and Harker Pl.
- Riva Rd. at Courtyard Annapolis
- Riva Rd. at Annapolis Technology Park
- Admiral Cochrane Dr. at Residence Inn
- Route 2 and Old South River Rd.
- Route 2 and Old South River Rd.
- Mayo Rd. and Route 2
- Mayo Rd. and Millhaven Dr.
- Mayo Rd. and Marlboro Rd.
- Mayo Rd. and Potomac Rd.
- Mayo Rd. and Salisbury Rd.
- Mayo Rd. and Bay Ridge Rd.
- Stepneys Ln. at Edgewater Library
- Stepneys Ln. and Howards Point Rd.
- Mitchells Chance Rd. and Route 2
- Route 2 and Mitchells Chance Rd.
- Harbour Center South
- Forest Dr. and Center St.
- Forest Dr. and Center St.
- Forest Dr. and Bausum Dr.
- Forest Dr. and Fairfax Rd.
- Chinquapin Round Rd. and Drew St.
- Chinquapin Round Rd. and Margaret Ave.
- West St. and Parole St.
- Admiral Dr. at Radio Park
- Forest Dr. and Rosecrest Dr.
- Forest Dr. and Rosecrest Dr.
- Tyler Ave. and Janwall St.
- Tyler Ave. and Janwall St.
- Tyler Ave. and Woods Dr.
- West St. and Cherry Grove Ave.
- West St. and Russell St.
- Compromise St. and Newman St.
- West St. and Brewer Ave.
- Medical Pkwy. and Bestgate Rd.
- Skippers Ln. and Greenbriar Ln.
- Cherry Grove Ave. and Forest Dr.
- Herbert Sachs Blvd. at DNR
- Herbert Sachs Blvd. at Court of Appeals
- Herbert Sachs Blvd. at Court of Appeals
- Herbert Sachs Blvd. at DNR
- Northwest St. and Church Circle
- Bay Ridge Ave. and Timber Creek Dr.
- West St. and Somerville Rd.
- Harbour Center North
- Social Security Administration
- Harry S. Truman Pkwy. at Pathways
- Navy-Marine Corps Memorial Stadium (Stop 1)
- Navy-Marine Corps Memorial Stadium (Stop 2)
- Navy-Marine Corps Memorial Stadium (Stop 3)
- Navy-Marine Corps Memorial Stadium (Stop 4)
- B&A Blvd. and King George St.
- Taylor Ave. and Ridgely Ave.
- Harry S. Truman Park & Ride
- Riva Rd. and Admiral Cochrane Dr.
- Route 2 and Admiral Cochrane Dr.
- Route 2 and Wallace Manor Rd.
- Route 2 and Poplar Point Rd.
- West Campus Dr. at Fine Arts Building
- West Campus Dr. at Fine Arts Building
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 31.2 | first check |
| 2026-07-30 | 31.2 | no change |
| 2026-07-31 | 31.2 | no change |
| 2026-08-01 | 31.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error16036 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 1826 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)
- Warning415 instances
415 of 415 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)
- Warning237 instances
237 of 237 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)
- Warning52 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)
- Warning10 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)
- Warning4 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)
- 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)
- Info4 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
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: feed_valid_beyond_total_service_window · 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 1826 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 1826 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 415 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 1826 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 1826 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 16036 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 44 / 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 38 / 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/annapolis-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.