Feed status · checked 2026-10-31
Marin Transit
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-30
Cataloged in California.
Source feed: https://marintransit.gov/data/google_transit.zip
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.4, validator 8.0.1.
Checked for changes 79 minutes ago; last changed 8 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Marin Transit’s published feed lists 20 bus routes, 1,613 scheduled trips and 545 stops. Its service dates run from 2026-04-12 through 2027-01-09. The published file last changed on 2026-10-22.
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
535 of 1613 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers 535 of 1,613 trips, about 33% of them.
⏱ A default or per-trip field in your export.worth about +5 points in its category
Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ A quick look at the flagged file.
Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.
The feed has a stretch of two weeks or more with no service running. A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ A review of your calendar dates.
Riders and need behind these fixes
- No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
- California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-26.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
Fix 01 · Read the fix guide for scorecard_wheelchair_accessible_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for unknown_file
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for big_gap_in_service
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 70 days.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 66.8% 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 5 kinds of issue across 14 instances (0 error, 0 warning, 14 informational).
Service data covers the next 70 days.
100% of stops state wheelchair accessibility (71% marked accessible, 29% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (71% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (219, 57, 49, 36, 35, 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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
This agency publishes realtime, but the feed needs an access key we don't have 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 545 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.
- 17 (teal)
- 219 (green)
- 22 (red)
- 228 (green)
- 23 (pink)
- 233 (green)
- 245 (green)
- 30 (purple)
- 35 (teal)
- 36 (yellow)
- 49 (teal)
- 57 (gray)
- 61 (blue)
- 613 (green)
- 619 (green)
- 625 (green)
- 629 (green)
- 654 (green)
- 68 (blue)
- 71 (orange)
| Route | Type | Line color |
|---|---|---|
| 17 Downtown San Rafael - Sausalito | Bus | teal |
| 219 Tiburon - Strawberry | Bus | green |
| 22 Downtown San Rafael - Marin City | Bus | red |
| 228 Downtown San Rafael - Fairfax Manor | Bus | green |
| 23 Canal - Fairfax Manor | Bus | pink |
| 233 San Rafael (Downtown - Santa Venetia) | Bus | green |
| 245 San Rafael (Downtown - Smith Ranch Road) | Bus | green |
| 30 Canal - Downtown San Rafael | Bus | purple |
| 35 Canal - Northgate | Bus | teal |
| 36 Canal - Marin City | Bus | yellow |
| 49 Downtown San Rafael - Novato San Marin | Bus | teal |
| 57 Downtown San Rafael - Novato | Bus | gray |
| 61 Sausalito - Bolinas | Bus | blue |
| 613 Paradise Cay - Redwood HS | Bus | green |
| 619 Tiburon - Redwood HS | Bus | green |
| 625 Lagunitas - Sir Francis Drake HS - San Anselmo Hub | Bus | green |
| 629 Paradise Cay - Hall MS | Bus | green |
| 654 Olive - Novato Loop | Bus | green |
| 68 Downtown San Rafael - Inverness | Bus | blue |
| 71 Novato - Marin City | Bus | orange |
List every stop
- Bridgeway & Ebbtide St
- Bridgeway & Gate 5 Rd
- Bridgeway & Nevada St
- Bridgeway & Nevada St
- Bridgeway & Easterby St
- Bridgeway & Easterby St
- Bridgeway & Napa St
- Bridgeway & Napa St
- Bridgeway & Pine St
- Bridgeway & Turney St
- Bridgeway & Caledonia Av
- Bay St & Bridgeway
- Marin City Hub-Donahue & Terners
- Drake Av & Donahue St
- Drake Av & Buckelew St
- Drake Av & Cole Dr
- Drake Av & Donahue St
- Shoreline Hwy & Almonte Blvd
- E Blithedale Ave & Tower Dr
- E Blithedale Ave & Kipling Dr
- E Blithedale Ave & Lomita Dr
- E Blithedale Ave & Roque Moraes Dr
- E Blithedale Ave & Mesa Ave
- E Blithedale Ave & Nelson Ave
- E Blithedale Ave & Alta Vista Ave
- E Blithedale Ave & Hilarita Ave
- E Blithedale Ave & East Dr
- E Blithedale Ave & Elm Ave
- E Blithedale Ave & Mountain View Ave
- E Blithedale Ave & Walnut Ave
- E Blithedale Ave & Hill St
- Mill Valley Depot-Sunnyside Ave & Miller Ave
- Miller Ave & Una Way
- Miller Ave & Park Ave
- Miller Ave & Montford Ave
- Miller Ave & Locust Ave
- Miller Ave & Reed St
- Miller Ave & Reed St
- Miller Ave & Camino Alto
- Miller Ave & Camino Alto
- Almonte Blvd & Miller Ave
- Almonte Blvd & Miller Ave
- Almonte Blvd & Rosemont Ave
- Almonte Blvd & Rosemont Ave
- Tam Junction-Shoreline Hwy & Almonte Blvd
- Tam Junction-Shoreline Hwy & Almonte Blvd
- Mill Valley Depot-Miller Ave & Sunnyside Ave
- Reed Blvd & Belvedere Dr
- Shoreline Hwy & Pine Hill Rd
- Manzanita Park & Ride Lot
- Shoreline Hwy & Pine St
- Hwy 101 @ Tiburon Wye Bus Pad
- Shoreline Hwy & Laurel Way
- Shoreline Hwy & Laurel Way
- Shoreline Hwy & Ross Dr
- Shoreline Hwy & Pohono St
- Hwy 101 @ Tiburon Wye Bus Pad
- Tiburon Blvd & Hwy 101 NB-Off Ramp
- Tiburon Blvd & Bay Vista Dr
- Tiburon Blvd & N Knoll Rd
- Tiburon Blvd & N Knoll Rd
- Tiburon Blvd & Strawberry Dr
- Reed Blvd & Redwood Hwy
- Redwood Hwy Frontage Rd & De Silva Island Dr
- Redwood Hwy Frontage Rd & Hwy 101 SB Ramps
- Hwy 101 @ Seminary Dr Bus Pad
- Hwy 101 @ Seminary Dr Bus Pad
- Beach Rd & San Rafael Av
- Beach Rd & Juanita Ln
- Tiburon Blvd & Beach Rd
- Tiburon Blvd & Beach Rd
- Tiburon Tiburon Blvd & Main St
- Tiburon Blvd & Mar West St
- Tiburon Blvd & Lyford Dr
- Tiburon Blvd & Lyford Dr
- Tiburon Blvd & Neds Way
- Tiburon Blvd & Neds Way
- Tiburon Blvd & San Rafael Av
- Tiburon Blvd & Gilmartin Dr
- Tiburon Blvd & Gilmartin Dr
- Tiburon Blvd & Rock Hill Dr
- Tiburon Blvd & Rock Hill Dr
- Tiburon Blvd & Avenida Miraflores
- Tiburon Blvd & Pine Terrace
- Tiburon Blvd & Stewart Dr
- Tiburon Blvd & Jefferson Dr
- Tiburon Blvd & Reed Ranch Rd
- Tiburon Blvd & Cecilia Way
- Tiburon Blvd & Cecilia Way
- Tiburon Blvd & Blackfield Dr
- Tiburon Blvd & Greenwood Beach Rd
- Tiburon Blvd & Greenwood Cove Rd
- Tiburon Blvd & Mar West St
- Magnolia Ave & Frances Ave
- Tiburon Blvd & Stewart Dr
- Antilles Way & Martinique Av
- Hwy 101 @ Lucky Dr Bus Pad
- Hwy 101 @ Lucky Dr Bus Pad
- Tamal Vista Blvd & Fifer Av
- Tamal Vista Blvd & Fifer Av
- Tamal Vista Blvd & Sandpiper Circle
- Tamal Vista Blvd & Sandpiper Circle
- Madera Blvd & Monona Dr
- Redwood Av & Montecito Dr
- Redwood Av & Montecito Dr
- Tamalpais Dr & Eastman Av
- Tamalpais Dr & Eastman Av
- Tamalpais Dr & Meadowsweet Dr
- Tamalpais Dr & Madera Blvd
- Tamalpais Dr & Casa Buena Dr
- Madera Blvd & Mohawk Av
- Paradise Dr & Madera Del Presidio Av
- Paradise Dr & Harbor Dr
- Paradise Dr & El Camino Dr
- Paradise Dr & Seawolf Passage
- Paradise Dr & Prince Royal Dr
- Paradise Dr & Prince Royal Dr
- Paradise Dr & Golden Hinde Passage
- Paradise Dr & Golden Hinde Passage
- Paradise Dr & Uplands Circle
- Paradise Dr & Uplands Circle
- Paradise Dr & Robin Dr
- Paradise Dr & Robin Dr
- Hwy 101 @ Tamalpais Dr Bus Pad
- Hwy 101 @ Paradise Dr Bus Pad
- Magnolia Ave & Frances Ave
- Magnolia Ave & Estelle Ave
- Magnolia Ave & Skylark Dr
- Magnolia Ave & Dartmouth Dr
- Magnolia Ave & Bon Air Rd
- Magnolia Ave & Bon Air Rd
- Magnolia Av & Ward St
- Magnolia Av & Ward St
- Magnolia Av & Madrone Av
- Magnolia Av & Madrone Av
- Magnolia Av & Park Way
- Magnolia Av & Alexander Av
- Doherty Dr & Larkspur Plaza Dr
- Doherty Dr & Larkspur Plaza Dr
- Redwood High & Doherty Dr
- Redwood High & Doherty Dr
- Lucky Dr & Riviera Circle
- Lucky Dr & Riviera Circle
- Sir Francis Drake Blvd & Mcallister Av
- Sir Francis Drake Blvd & Wolfe Grade
- Sir Francis Drake Blvd & Wolfe Grade
- Sir Francis Drake Blvd & Bon Air Rd
- Sir Francis Drake Blvd & El Portal Dr
- Sir Francis Drake Blvd & La Cuesta Dr
- Sir Francis Drake Blvd & La Cuesta Dr
- Sir Francis Drake Blvd & Eliseo Dr
- Sir Francis Drake Blvd & Eliseo Dr
- Doherty Dr & Hall Middle School
- College of Marin College Av & Sir Francis Drake
- 1125 Sir Francis Drake Blvd
- Sir Francis Drake Blvd & Ross Terrace
- College of Marin - Sir Francis Drake Blvd & Elm Av
- College Of Marin Sir Francis Drake Blvd & Maple
- Sir Francis Drake Blvd & Ash Av
- Sir Francis Drake Blvd & Ash Ave
- Sir Francis Drake Blvd & Rosebank Dr
- Sir Francis Drake Blvd & Oak Ave
- Sir Francis Drake Blvd & Laurel Grove Ave
- Ross Sir Francis Drake Blvd & Lagunitas Rd
- Ross Sir Francis Drake Blvd & Lagunitas Rd
- College of Marin College Ave & Sir Francis Drake
- Lincoln Ave & Wilson Ct
- Lincoln Ave & Wilson Ct
- Lincoln Ave & Grand Ave
- Lincoln Ave & Grand Ave
- Lincoln Ave & Linden Ln
- Lincoln Ave & Linden Ln
- Lincoln Ave & Paloma Ave
- Lincoln Ave & Paloma Ave
- Lincoln Ave & Mission Ave
- Lincoln Ave & Mission Ave
- Grand Av & Linden Ln
- Grand Av & Linden Ln
- Grand Av & Mountain View Av
- Grand Av & Mountain View Av
- Dominican University Grand Av & Acacia Av
- Grand Av & Acacia Way
- Grand Av & Jewell St
- Grand Av & Jewell St
- Grand Av & Belle Av
- Grand Av & Belle Av
- 2nd St & Grand Ave
- 4th St & Ross Valley Dr
- 4th St & Santa Margarita Ave
- 4th St & Greenfield Ave
- 4th St & Greenfield Ave
- 4th St & Ida St
- 4th St & Ida St
- 4th St & E St
- 4th St & E St
- 4th St & C St
- 4th St & C St
- 4th St & Court St
- 4th St & Court St
- 3rd St & Grand Ave
- Kerner Blvd & Canal St
- Kerner Blvd & Canal St
- Medway Rd & Francisco Blvd E
- Francisco Blvd E & Bay St
- Canal St & Medway Rd
- Canal St & Novato St
- Medway Rd & Mill St
- Canal St & Sonoma St
- Canal St & Novato St
- Kerner Blvd & Fairfax St
- Canal St & Sonoma St
- Kerner Blvd & Larkspur St
- Kerner Blvd & Bahia Way
- Kerner Blvd & Larkspur St
- Kerner Blvd btwn 3140 & 3160
- Bellam Blvd & Lisbon St
- Bellam Blvd & Francisco Blvd E
- E Sir Francis Drake Blvd & Larkspur Landing
- Sir Francis Drake Blvd & San Anselmo Ave
- Sir Francis Drake Blvd & Butterfield Rd
- Archie Williams HS-Sir Francis Drake & Ash Ave
- Sir Francis Drake Blvd & Broadmoor Ave
- Sir Francis Drake Blvd & Tamal Ave
- Sir Francis Drake Blvd & Aspen Ct
- Sir Francis Drake Blvd & Sais Ave
- Sir Francis Drake Blvd & San Francisco Blvd
- Sir Francis Drake Blvd & Sunnyhills Dr
- Sir Francis Drake Blvd & Madrone Ave
- Sir Francis Drake Blvd & Madrone Ave
- San Anselmo Hub
- Sir Francis Drake Blvd & Ross Av
- Sir Francis Drake Blvd & Barber Av
- Sir Francis Drake Blvd & Bolinas Av
- Sir Francis Drake Blvd & Bolinas Rd
- Red Hill Ave & Sequoia Dr
- Red Hill Ave & Sequoia Dr
- Sir Francis Drake Blvd & Olema Rd
- Sir Francis Drake Blvd & Glen Dr
- Sir Francis Drake Blvd & Alhambra Circle
- Sir Francis Drake Blvd & Alhambra Circle
- Sir Francis Drake Blvd At Drake Manor Apts
- Sir Francis Drake Blvd At Drake Manor Apts
- Sir Francis Drake Blvd & Oak Manor Dr
- Sir Francis Drake Blvd & Oak Manor Dr
- Sir Francis Drake Blvd & Marin Rd
- Sir Francis Drake Blvd & Oak Tree Ln
- Sir Francis Drake Blvd & Claus Dr
- Broadway Blvd & Bolinas Ave
- Sir Francis Drake Blvd & Broadway
- Sir Francis Drake Blvd & Marinda Dr
- and 295 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 30 checks — unchanged since 2026-10-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 92.2 | first check |
| 2026-10-03 | 92.2 | no change |
| 2026-10-04 | 92.2 | no change |
| 2026-10-05 | 92.2 | no change |
| 2026-10-06 | 92.2 | no change |
| 2026-10-07 | 92.2 | no change |
| 2026-10-08 | 92.2 | no change |
| 2026-10-09 | 92.2 | no change |
| 2026-10-10 | 92.2 | no change |
| 2026-10-11 | 92.2 | no change |
| 2026-10-12 | 92.2 | no change |
| 2026-10-13 | 92.2 | no change |
| 2026-10-14 | 92.2 | no change |
| 2026-10-15 | 92.2 | no change |
| 2026-10-16 | 92.2 | no change |
| 2026-10-17 | 92.2 | no change |
| 2026-10-18 | 92.2 | no change |
| 2026-10-19 | 92.2 | no change |
| 2026-10-20 | 92.2 | no change |
| 2026-10-21 | 92.2 | no change |
| 2026-10-22 | 97.2 | up 5.0 |
| 2026-10-23 | 97.2 | no change |
| 2026-10-24 | 97.2 | no change |
| 2026-10-25 | 97.2 | no change |
| 2026-10-26 | 97.2 | no change |
| 2026-10-27 | 97.2 | no change |
| 2026-10-28 | 97.2 | no change |
| 2026-10-29 | 97.2 | no change |
| 2026-10-30 | 97.2 | no change |
| 2026-10-31 | 97.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-22 to 2026-10-31 (10 checks) | 772c6b3e1340 | 2027-01-09 | Current rubric: see the trend above |
| 2026-10-02 to 2026-10-21 (20 checks) | d7835c29f93e | 2027-01-09 | Current rubric: see the trend above |
| 2026-09-13 to 2026-10-01 (15 checks) | d7835c29f93e | 2027-01-09 | A, 92.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-08-25 to 2026-09-12 (19 checks) | 3453994b9f23 | 2026-09-12 | D, 63.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-27 to 2026-08-24 (29 checks) | fb1b4ee508d8 | 2026-09-13 | C, 73.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-07-26 (2 checks) | 3b15e92f2618 | 2026-09-13 | B, 85.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | 7e9da8467ae0 | 2026-09-13 | B, 86.1 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-16 to 2026-07-12 (25 checks) | d03b333bc455 | 2026-08-09 | D, 66.8 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-30.
Same feed file as 2026-10-30; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-10-02 this feed started at grade A. On 2026-10-31 the grade held, though the score rose from 92 to 97. As of 2026-10-31 it holds grade A.
A plain-language history of this feed, newest first.
- 2026-10-22 Score rose 5 points, correctness rose 11 points.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning535 instances
535 of 1613 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info6 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 for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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 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 for service_window_outside_feed_period · 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 for unknown_column · 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 70 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Different (allowed)
- Your feed's agency_id is 33; your National Transit Database ID is 90234. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 33 to NTD ID 90234, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 1613 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 100% of stops and 67% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 70 days.
- Accessible Not yet
- States wheelchair access on 100% of stops and 67% 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 70 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 100% of stops and 67% of trips.
- Meets shapes.txt with a shape for every trip
All 1613 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 97 / 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 95 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Access needed to measure
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in California
Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/marin-transit/2026-10-31.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-10-31. 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.