Feed status · checked 2026-08-01
Saint Maryʼs Transit System
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 42 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
105 of 105 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
197 of 197 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
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.
197 of 197 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.
⏱ Usually one value per route pattern in your scheduling source.worth about +15 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
- 105 of 105 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
- 197 of 197 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
- 197 of 197 trips lack rider-facing destination or direction text.
- Next action
- 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.
- 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. Self-check a feed before you publish.
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. Self-check a feed before you publish.
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. · 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. 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 is in 1249 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 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 236 instances (0 error, 235 warning, 1 informational).
Service data covers the next 1249 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
77 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Intersection of Thompson Corner Rd and Budds Creek Rd", "Wawa at the intersection of Three Notch Rd and Point Lookout Rd", "Intersection of Three Notch Rd and Mattapany Rd", 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 105 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 (green)
- 11 (green)
- 12 (green)
- 14 (green)
- 2 (green)
- 3 (green)
- 4 (green)
- 4.5 (green)
- 5 (green)
- 6 (green)
- 7 (green)
| Route | Type | Line color |
|---|---|---|
| 1 California Route | Bus | green |
| 11 Great Mills/California Route | Bus | green |
| 12 Leonardtown Route | Bus | green |
| 14 County Span Saturday Route | Bus | green |
| 2 Charlotte Hall Route | Bus | green |
| 3 Great Mills Route | Bus | green |
| 4 County Span Route | Bus | green |
| 4.5 Between Lexington Park and California via MD 235 | Bus | green |
| 5 Calvert Connection | Bus | green |
| 6 Northern Route | Bus | green |
| 7 Southern Route | Bus | green |
List every stop
- Intersection of Thompson Corner Rd and Budds Creek Rd
- Intersection of Three Notch and Millstone Landing Rd
- Intersection of Commerce Park Rd and Three Notch Rd
- Intersection of Three Notch Rd and Old Rolling Rd
- Three Notch Rd Opposite of Hollywood Medical Center
- Intersection of Three Notch Rd and Shady Mile Dr
- Toyota Dealership off of Three Notch Rd
- Intersection of Three Notch Rd and Valley Dr
- Wawa at the intersection of Three Notch Rd and Point Lookout Rd
- Intersection of Three Notch Rd and Mattapany Rd
- Shell Gas Station at the intersection of Three Notch and New Market Turner Rd
- Intersection of Three Notch Rd and Trapp Rd
- Intersection of Thompson Corner Rd and Ryceville Rd
- Intersection of Thompson Corner Rd and Woodburn Hill Rd
- Hollywood Rd and Leonard Hall Dr
- Intersection of Hollywood Rd and McIntosh Rd on the North Side of Hollywood Rd
- Intersection of Hollywood Rd and McIntosh Rd on the South Side of Hollywood Rd
- Intersection of Hollywood Rd and Three Notch Rd on the North Side of Hollywood Rd
- Intersection of Hollywood Rd and Three Notch Rd on the South Side of Hollywood Rd
- Hollywood Rd Opposite of Leonard Hall Dr
- Intersection of Loveville Rd and Busy Corner Rd
- Intersection of Loveville Rd and Three Notch Rd by East Coast Investments
- Intersection of Loveville Rd and Three Notch Rd on the South Side of Three Notch Rd North of Loveville Rd
- Intersection of Loveville Rd and Three Notch Rd on the South Side of Loveville Rd
- Loveville Rd Opposite of Busy Corner Rd
- Intersection of Oak Rd and Patuxent Beach Rd
- Intersection of Oak Rd and Patuxent Beach Rd
- Farmers Market in Charlotte Hall off of Three Notch Rd
- New Market Plaza off of Point Lookout Rd in Mechanicsville
- Intersection of Point Lookout Rd and Park Hall Rd
- Intersection of Point Lookout Rd and Willows Rd
- Ledo Pizza off of Point Lookout Rd in Leonardtown
- The MVA off of Point Lookout Rd
- Third Base Store off of Point Lookout Rd
- Point Lookout Rd opposite Budds Creek Rd
- Point Lookout Rd opposite of Weis
- Point Lookout Rd opposite of Leonardtown High School
- Point Lookout Rd opposite of St Peters Claver Rd
- Point Lookout Rd opposite of Third Base Store
- Camden Way by Five Below
- Intersection of Baywoods Dr and Castaway Cir
- Philip J. Bean Medical Center
- Shell Gas Station at intersection of Point Lookout Rd and Washington St
- Callaway Marketplace off of Point Lookout Rd
- Cedar Lane Apartments off of Point Lookout Rd
- Intersection of Chancelors Run and FDR Blvd
- Charlotte Hall Food Lion
- Charlotte Hall Post Office
- Charlotte Hall Veterans Home
- College of Southern Maryland Parking Lot off of Point Lookout Rd
- Intersection of Fox Chase Dr and Lexington Dr
- County Governmental Center
- Great Mills Rd by Great Mills Highschool
- Great Mills Rd Opposite Great Mills Highschool
- Sheetz off of Great Mills Rd
- Intersection of Green Leaf Rd and Silver Slate Dr
- Hollywood Medical Center
- J. Patrick Jarboe Medical Center
- Laurel Glen Shopping Center
- Leonardtown Center by Food Lion
- Leonardtown High School
- Leonardtown Library
- Leonardtown Wharf
- Lexington Park Active Adult Community
- Lexington Park Library
- Intersection of Lexwood Dr and Joe Baker Ct
- Intersection of Liberty St and Pacific Dr by Apartment Offices
- Intersection of Liberty St and Pacific Dr
- Intersection of Liberty St and Pegg Rd
- Loffler Senior Center
- Mckays At Breton Bay
- Intersection of Mechanicsville Rd and Opposite Carpenter Dr
- Intersection of Mechanicsville Rd and Yowaiski Mill Rd
- Millison Plaza by Showtime Deli
- Intersection of Three Notch Rd and South Sandgates Rd
- New Towne Village
- Northern Senior Center
- Intersection of Old Village Rd and Mechanicsville Rd
- Intersection of Park Ave and Washington St
- Pathways off of Airport View Dr
- Patuxent Plaza
- Intersection of Pine Hill Run And Atalanta St
- Point Lookout Rd by Ridge Apartments
- Ridge Market
- Intersection of Ryceville Rd and Brookline Rd
- Intersection of Three Notch Rd and South Sandgates Rd
- San Souci Plaza
- Social Security Administration off of Business Center Dr
- Soup Kitchen at Langley Rd
- Intersection of Spring Valley Dr and Valley Ct
- Mill Field Dr at St Marys College
- St Marys Hospital
- Harris Teeter at St Marys Marketplace
- St Marys Nursing Center off of Peabody St
- St Marys Square
- Target
- Tulagi Place
- Walmart
- Intersection of Westbury Blvd and Great Mills Rd
- Intersection of Westbury Blvd and Great Mills Rd
- Wildewood Center by Belk
- Wildewood Center by JCPenny
- Intersection of Willows Rd and Abberly Crest Rd
- Intersection of Willows Rd and Great Mills Rd
- Winters Sheet Metal off of Point Lookout Rd
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 66.2 | first check |
| 2026-07-30 | 66.2 | no change |
| 2026-07-31 | 66.2 | no change |
| 2026-08-01 | 66.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning197 instances
197 of 197 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)
- Warning197 instances
197 of 197 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)
- Warning126 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)
- Warning105 instances
105 of 105 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)
- Warning63 instances
Stop has too many matches for shape (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_has_too_many_matches_for_shape' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning37 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 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)
- 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)
- Info1 instance
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · 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 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 1249 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 197 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 1249 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 1248 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 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/saint-mary-s-transit-system-2268/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.