Feed status · checked 2026-08-01
Commute.org San Mateo County Shuttles
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
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 32 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_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
249 of 249 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
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
86 of 254 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 +8 points in its category
Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Same stop and route url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +8 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 249 of 249 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
- 86 of 254 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
- Same stop and route url (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'same_stop_and_route_url' 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
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_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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 153 days.
- Published accessibility data
- Accessibility information is stated for 66.1% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 130 instances (0 error, 87 warning, 43 informational).
Service data covers the next 153 days.
66% of stops state wheelchair accessibility (66% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
66% of stops state accessibility (66% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (SKY Shuttle, BPT Shuttle, OPB Shuttle, OPC Shuttle, OPF Shuttle, and more).
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.
165 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("1000 Gateway Blvd.", "701 Gateway Blvd.", "Oyster Point Blvd / Gateway", 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 254 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.
- BPT Shuttle (teal)
- MPT Shuttle (teal)
- NFC Shuttle (purple)
- OPB Shuttle (teal)
- OPC Shuttle (teal)
- OPF Shuttle (teal)
- SEA Shuttle (teal)
- UGB Shuttle (teal)
- UGC Shuttle (teal)
- RLC Shuttle (teal)
- BAY Shuttle (teal)
- BCP Shuttle (teal)
- HCC Shuttle (purple)
- FCC Shuttle (purple)
- MBC Shuttle (blue)
- M1 Shuttle (teal)
- M4 Shuttle (yellow)
- M3 Shuttle (pink)
- DCB Shuttle (teal)
- SKY Shuttle (teal)
| Route | Type | Line color |
|---|---|---|
| BPT Shuttle Burlingame Point | Bus | teal |
| MPT Shuttle Redwood City Midpoint | Bus | teal |
| NFC Shuttle North Foster City | Bus | purple |
| OPB Shuttle Oyster Point BART | Bus | teal |
| OPC Shuttle Oyster Point Caltrain | Bus | teal |
| OPF Shuttle Oyster Point Ferry | Bus | teal |
| SEA Shuttle Seaport Centre | Bus | teal |
| UGB Shuttle Utah/Grand BART | Bus | teal |
| UGC Shuttle Utah/Grand Caltrain | Bus | teal |
| RLC Shuttle Redwood LIFE Caltrain | Bus | teal |
| BAY Shuttle Burlingame Bayside | Bus | teal |
| BCP Shuttle Brisbane Crocker Park | Bus | teal |
| HCC Shuttle Hillsdale Caltrain Commuter | Bus | purple |
| FCC Shuttle Foster City Commuter | Bus | purple |
| MBC Shuttle Millbrae Burlingame Commuter | Bus | blue |
| M1 Shuttle Crosstown | Bus | teal |
| M4 Shuttle Willow Road | Bus | yellow |
| M3 Shuttle Marsh Road | Bus | pink |
| DCB Shuttle Daly City Bayshore | Bus | teal |
| SKY Shuttle Skyline College Express | Bus | teal |
List every stop
- 1000 Gateway Blvd.
- 701 Gateway Blvd.
- 201 Haskins Way
- 352 Oyster Point
- Oyster Point Blvd / Gateway
- 322 Airport Blvd. (BUR 102)
- Tunnel & Blanken
- 213 E. Grand Ave. (PM Only)
- 269 E. Grand Ave. (PM Only)
- 380 Littlefield Ave. (PM Only)
- Old County / Bayshore
- Mariners' Island & Fashion Island Blvd
- Barron Ave & Broadway @ Discovery Hall
- Belmont Caltrain Station
- Broadway Caltrain Station
- 505 Broadway @ Cardinal Hall
- 155 South Hill
- South San Francisco BART (UGB/OTP, Bay #6)
- Millbrae Intermodal Station (West)
- Mills-Peninsula Health Services
- Adeline & Balboa
- Adeline & Bernal
- Sisters of Mercy
- Adeline & Bernal
- Adeline & Balboa
- Hillsdale Caltrain Station
- 1800-1820 Gateway
- Shell & E. Hillsdale Blvd.
- The Plaza at Triton Park
- 393 Vintage Park Dr (AM Only)
- 951 Mariners' Island
- One Hundred Grand
- Balboa Park BART (Geneva/Delano)
- Bayshore & Geneva
- Bayshore & Guadalupe
- Old County / San Francisco (USPS Office)
- San Bruno / Mendocino
- San Bruno / Alvarado
- San Bruno / Glen Park Way
- 3745 Bayshore
- Bayshore & Tunnel
- 140 Valley
- 240 Valley
- 380 Valley
- 422 Valley
- 460 Valley
- 480 Valley
- W. Hill Dr. & W. Hill PL
- 150 West Hill Pl.
- 175 South Hill
- 99 South Hill
- 101 South Hill
- Tunnel & Recycle (Bayshore Caltrain)
- Bayshore & Guadalupe
- Bayshore & Visitacion
- Bayshore Caltrain Station
- Bayshore & Leland
- Bayshore & Blanken
- South San Francisco BART (OPB, Bay #1)
- The Cove
- 1120 Veterans Blvd.
- 220 Oyster Point
- 200 Oyster Point
- Oyster Point Blvd / Eccles (EB)
- 384 Oyster Point
- Cul-de-Sac (395/400 Oyster Point Blvd)
- South San Francisco Ferry Terminal
- 169 Harbor Way (AM Only)
- 230 E. Grand Ave. (AM Only)
- Kimball & E. Grand Ave.
- 390 Swift Ave.
- 475 E. Grand Ave.
- Cabot/Allerton Ave.
- 349 Littlefield Ave. (AM Only)
- SSF Conference Center
- 400/450 E. Jamie Court
- South San Francisco Caltrain
- Millbrae Intermodal Station (East)
- 1649 Adrian Road
- David/Rollins
- 1600 Rollins Road
- Rollins/Guittard
- 1799 Old Bayshore Hwy (AM Only)
- Bayshore/Hinckley
- 1333 Bayshore Hwy (AM Only)
- Airport/Bayview
- 600 Airport Blvd.
- 700 Airport Blvd.
- 800 Airport Blvd.
- 1350 Bayshore Hwy (PM Only)
- 1600 Bayshore Hwy (PM Only)
- 1800 Old Bayshore Hwy (PM)
- Mariners' Island & Armada Way
- 353 Lakeside
- 300-310 Lakeside
- 303 Velocity Way
- 200 Lincoln Centre
- E. 3rd Ave. & Lincoln Centre
- 1163 Chess Drive
- 1111-1133 Chess Drive
- 4000/4100 E. 3rd Ave.
- Bridgepointe Circle & Bridgepointe Pkwy (AM Only)
- Broadway & Douglas
- Redwood City Caltrain Station
- Chesapeake
- 100 Cardinal Way
- Saginaw (Cul-de-Sac)
- Galveston
- Bayshore Blvd & Geneva
- 800 Bridge Pkwy.
- Bridge Pkwy. & Island Drive
- 1600-1800 Bridge Pkwy
- 2800-3000 Bridge Pkwy.
- 3400-3600 Bridge Pkwy.
- 440 Valley
- Maple & Blomquist
- Oyster Point Blvd / Veterans Blvd (WB)
- Marine Pkwy / Boardwalk Pl
- Marine Pkwy / Sandpiper Ln
- Marine Pkwy / Twin Dolphin (AM Only)
- Marine Pkwy / Oracle Pkwy (PM Stop)
- E. 3rd Ave & S. Norfolk (SE Corner)
- E. 3rd Ave & S. Norfolk (NE Corner)
- Oyster Point Blvd / Veterans Blvd (EB)
- Oyster Point Blvd / Eccles (WB)
- 20th Ave & Alameda de las Pulgas
- California Dr & Broadway (PM Only)
- Saratoga Dr & Park Pl
- Daly City BART Station
- Menlo Park Caltrain (Crosstown Shuttle Stop)
- Ravenswood Ave & Pine St
- Santa Cruz & Curtis
- Alameda de las Pulgas & Santa Cruz Ave
- Alameda de las Pulgas & Sharon Rd
- Alameda de las Pulgas & Avy Ave
- Avy Ave & Altschul Ave
- Avy Ave & Monte Rosa Dr
- Monte Rosa Dr & Eastridge Ave
- Welch Rd @ Lucile Packard Children's Hospital
- Welch Rd @ Lucile Packard Children's Hospital
- University Dr & Middle Ave
- University Dr & Middle Ave
- Santa Cruz & Doyle
- Santa Cruz & Evelyn
- Glenwood Ave & El Camino Real
- Glenwood Ave & El Camino Real
- Glenwood Ave & Mills Ct
- Glenwood Ave & Mills Ct
- Ravenswood Ave & Pine St
- Willow Rd & Alma St
- Willow Rd & Alma St
- Linfield Dr & Laurel St
- Linfield Dr & Laurel St
- Willow Rd & Nash Ave
- Willow Rd & Nash Ave
- Willow Rd & Newbridge St
- Willow Rd & Newbridge St
- Ivy Dr & Willow Rd
- Ivy Dr & Willow Rd
- Ivy Dr & Sevier Ave
- Ivy Dr & Sevier Ave
- Chilco St & Hamilton Ave
- Chilco St & Hamilton Ave
- Terminal Ave & Modoc Ave
- Terminal Ave & Modoc Ave
- Menlo Park Caltrain (Marsh Rd. Shuttle Stop)
- 3760 Haven (Quicken)
- 3639 Haven (Anton Menlo Park)
- 3641 Haven (Elan Menlo Park)
- Constitution Dr & Chilco St
- 180 Jefferson
- TIDE Academy
- 149 Commonwealth
- Chrysler Dr & Independence Dr
- Constitution Dr & Chrysler Dr
- Scott & Marsh Rd (PM Stop)
- Scott & Marsh Rd (AM Stop)
- 4100 Bohannon (PM Stop)
- 4100 Bohannon (AM Stop)
- Bohannon Dr & Campbell Ave (PM Stop)
- Bohannon Dr & Campbell Ave (AM Stop)
- Post Office (PM Stop)
- Post Office (AM Stop)
- Adams Court (AM Stop)
- 1505 O'Brien
- 1200 O'Brien (PM Stop)
- 1200 O'Brien (AM Stop)
- O'Brien Dr & Willow Rd (PM Stop)
- O'Brien Dr & Willow Rd (AM Stop)
- Willow Rd & Coleman Ave
- Willow Rd & Coleman Ave
- Willow Rd & Clover Ln
- Willow Rd & Clover Ln
- Linfield Dr & Middlefield Rd (PM Stop)
- Linfield Dr & Middlefield Rd (AM Stop)
- Linfield Dr & Waverley St
- Linfield Dr & Waverley St
- Chilco & Ivy (OB)
- Palo Alto Caltrain (Lytton & Alma)
- University/Partridge Ave.
- Stanford Medical Center (Welch/Blake Wilbur Dr)
- Menlo Commons
- Sharon Heights Shopping Center
- Stanford Medical Center (900 Welch Rd.)
- Nordstrom / Crate & Barrel
- Stanford Shopping Center
- Hoover Pavilion
- Palo Alto Medical Foundation
- Partridge/Kennedy
- Little House Recreation Center
- Safeway (El Camino Real/Middle Ave)
- Santa Cruz & Crane
- Santa Cruz & Chestnut
- Crane Place
- Crane Place
- Middlefield & Oak Grove Ave
- Middlefield & Oak Grove Ave
- Menlo Park Library
- Menlo Medical Clinic
- V.A. Medical Center
- Chilco & Ivy (IB)
- Belle Haven Community Campus
- Menlo Park Caltrain (Willow Rd. Shuttle Stop)
- Carter/Saddleback Dr.
- Rio Verde/Partridge St.
- Schwerin/Otillia St.
- Martin/Schwerin St.
- Bay Ridge/Accacia St.
- Linda Vista/Jacqueline Ln
- Balboa Park BART (MUNI)
- Walgreens (998 Geneva) - Eastbound
- Mission/Wellington
- Daly City BART
- North Peninsula Food Pantry (San Jose/Bepler)
- Mission Safeway
- Walgreens (965 Geneva) - Westbound
- Bayshore Community Center
- 7 Mile House (Bayshore/Geneva)
- Skyline College - South Bus Stop
- Skyline College - North Drop-off Loop
- O'Brien & Kelly (IB)
- O'Brien & Kelly (OB)
- 1555 O'Brien
- 1149 Chess Drive
- Cul-de-Sac (4000/4001 E. 3rd Ave.)
- 378 Vintage Park Dr (PM Only)
- Bridgepointe Pkwy & Chess Dr (PM Only)
- Blomquist & Maple
- E. Grand & Pointe Grand
- 324 Lakeside
- and 4 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 | 85.7 | first check |
| 2026-07-30 | 85.7 | no change |
| 2026-07-31 | 85.7 | no change |
| 2026-08-01 | 85.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning249 instances
249 of 249 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)
- Warning86 instances
86 of 254 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)
- Warning68 instances
Same stop and route url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_stop_and_route_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning19 instances
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)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
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)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
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 153 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 249 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 66% 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 153 days.
- Accessible Not yet
- States wheelchair access on 66% 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.
- 19 of 254 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (5 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 66% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 249 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 84 / 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 76 / 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/commute-org-san-mateo-county-shuttles/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.