Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Petaluma Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 30% of all tracked agencies and 28% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 10 hours ago; last changed 8 days ago.
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 1105 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required column (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
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
152 of 167 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 +23 points
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.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
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 9 kinds of issue across 95 instances (2 error, 39 warning, 54 informational).
Service data ended 1105 day(s) ago. Trip planners have likely already dropped this feed.
9% of stops state wheelchair accessibility (9% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
9% of stops state accessibility (9% marked accessible). Reflects what the feed states, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 10 (red)
- 501 (black)
- 2 (red)
- 3 (teal)
- 33 (teal)
- 11 (purple)
- 24 (yellow)
- 311 (red)
- 303 (green)
- 302 (purple)
- 312 (green)
- 301 (gray)
| Route | Type | Line color |
|---|---|---|
| 10 Route 10 | Bus | red |
| 501 Route 501 | Bus | black |
| 2 Route 2 | Bus | red |
| 3 Route 3 | Bus | teal |
| 33 Route 33 | Bus | teal |
| 11 Route 11 | Bus | purple |
| 24 Route 24 | Bus | yellow |
| 311 Route 311 | Bus | red |
| 303 Route 303 | Bus | green |
| 302 Route 302 | Bus | purple |
| 312 Route 312 | Bus | green |
| 301 Route 301 | Bus | gray |
This feed has 167 stops.
List every stop
- Lakeville Hwy @ Marina Ave. SB
- Lakeville Hwy @ Casa Grande Rd. SB
- Lakeville Hwy @ Caulfield Lane SB
- Lakeville Hwy @ Frates Rd. NB
- Lakeville Hwy @ S. McDowell Extension NB
- Lakeville Hwy @ S. McDowell Extension SB
- Magnolia @ Keokuk EB (St. Vincent's HS)
- N. McDowell Blvd @ RR Tracks NB (Sr. Apts)
- Bodega Ave @ Webster St EB
- D Street at Lakeville - SMART Stn. WB
- E. Washington @ Petaluma Blvd. North
- EB - Magnolia Ave & Antone Way
- B St & Webster St (First Presbyterian Church)
- Western Ave & N Fair St - WB
- Park Ln & Greenbriar Circle
- Lakeville Hwy @ Cader Ln EB
- Kenilworth Dr. at Target Shopping Center
- Copeland Street Transit Mall south of Washington Street
- E. Washington St. west of Grey St.
- Keller Street north of Western (Petaluma Market)
- 4th Street west of C St.
- E. Washington St. east of Lakeville St. (Taco Bell)
- E. Washington St. west of Vallejo St.
- E. Washington St. & Ellis St. (Petaluma Swim Center)
- E. Washington St. west of Ellis St.
- E. Washington St. west of Vallejo St.
- E. Washington St. south of Lakeville
- Petaluma Blvd. S south of F Street
- Petaluma Blvd. S south of Mtn View Ave.
- Petaluma Blvd. S at Roundabout
- Petaluma Blvd. S. east of McNear Ave.
- Petaluma Blvd. S east of Mountain View Ave.
- Petaluma Blvd. S north of G st.
- Petaluma Blvd. S east of E st.
- McNear Ave. north of Mission Dr.
- Sunnyslope Rd West of I St
- Fair Street West of Douglas St. (Petaluma High School)
- Bantam Way at Petaluma Junior High
- Bodega Ave. east of Bantam Way
- Petaluma Blvd. N north of Washington St GG
- Petaluma Blvd. N south of Kent
- Petaluma Blvd. N at Cherry
- Petaluma Blvd. N north of Shasta Ave./Sycamore Ln.
- Petaluma Blvd. N north of Factory Outlets
- Petaluma Blvd. N north of Corona Rd./Skillman Ln.
- Industrial Ave. south of Petaluma Blvd. N. (Comm. School)
- Petaluma Blvd. N south of Skillman Ln./Corona Rd.
- Petaluma Blvd. N at Gossage Ave. (Park N Ride)
- Petaluma Blvd. N south of Factory Outlets
- Petaluma Blvd. N north of Shasta Ave./Sycamore Ln.
- Petaluma Blvd. N. south of Magnolia Ave.
- Petaluma Blvd. N north of West Street
- Petaluma Blvd. N north of Oak St.
- Petaluma Blvd. N north of Washington St.
- Maria south of Creekside Drive
- Maria Dr. north of Greenbriar Circle
- Eastside Transit Ctr (Maria Dr.) at Washington Square SC
- E. Madison St. east of Novak Dr. (Sr Center)
- E. Madison St. east of Novak Dr. (SR. Center)
- Maria Dr. north of Monroe St. (Eldredge School)
- Maria Dr. south of Rainier Drive
- Maria Dr. south of Northstar Dr.
- Maria Dr. at Sunrise Pkwy
- Maria Dr. north of Meadow School
- Sonoma Mtn Parkway south of Maria Drive
- Sonoma Mtn Parkway south of Colombard Rd./Ely Rd.
- Sonoma Mtn Parkway south of Riesling Rd.
- Sonoma Mtn Parkway south of Campus Circle
- Sonoma Mtn Parkway south of Campus Circle/Cygnus Way
- Sonoma Mtn Parkway south of Rainier Ave.
- Sonoma Mtn Parkway south of Clary Way
- Sonoma Mtn Parkway south of Chehalis Drive
- Sonoma Mtn Parkway north of E. Washington
- Sonoma Mtn Parkway north of Turtle Creek Way
- Sonoma Mtn Parkway south of Castle Drive
- Sonoma Mtn Parkway north of Rainier Drive
- Sonoma Mtn Parkway south of Campus Circle/Cygnus Way
- Sonoma Mtn Parkway north of Campus Circle (SRJC/Leghorn Park)
- Sonoma Mtn Parkway north of Riesling Rd.
- Sonoma Mtn Parkway north of Ely Rd./Colombard Rd.
- Maria Dr. south of Morning Glory Dr.
- Maria Dr. south of DuPree Way (Meadow School)
- Maria Dr. north of Sunrise Pkwy
- Maria Dr. at Halley's Court
- Maria Dr. south of Rainier Ave.
- Maria Dr. north of Professional Dr.
- Maria Dr. south of Monroe St. (Eldredge/B&G Club)
- Dover Lane at Kenilworth JHS
- Ely Blvd. S. south of Gilrix St.
- Ely Blvd. S. at Washington Creek Trail
- Ely Blvd. S. at Caulifield Lane
- Ely Blvd S. south of Juliet (Casa Grande HS Main)
- Ely Blvd S. north of Casa Grande Rd.
- Casa Grande Rd. east of Crinella (Casa Grande HS)
- S. McDowell Blvd. north of Casa Grande Rd.
- S. McDowell Blvd. south of Anna Way
- S. McDowell Blvd. north of Baywood Dr.
- S. McDowell Blvd. north of Covey Way (midblock)
- S. McDowell Blvd. north of Caulfield Ln.
- S. McDowell Blvd. north of Weaverly Dr.
- S. McDowell Blvd. at Lindberg Lane
- S. McDowell Blvd at Caulfield Ln
- S. McDowell Blvd. north of Baywood Dr.
- S. McDowell Blvd. south of Evergreen Lane (midblock)
- S. McDowell Blvd. north of Casa Grande Ave.
- Casa Grande Rd. west of Casa de Arroyo Drive
- Casa Grande Rd. east of Sartori Dr.
- Casa Grande Rd. at Ely Blvd. S. 400 Casa Grande Apts
- Ely Blvd S. north of Cross Creek St.
- Ely Blvd S. north of Village East Dr.
- Ely Blvd S at Caulfield Ln
- Ely Blvd S. north of Estuary Way
- Ely Blvd S. north of Clydesdale Way
- Ely Blvd S. north of Gilrix Street
- N. McDowell Blvd. at Community Center/Luchessi
- N. McDowell Blvd. north of Lynch Creek Way (Hospital)
- N. McDowell Blvd. north of Rainier Ave.
- N. McDowell Blvd. south of Candlewood Dr. (Sandlewood MHP)
- N. McDowell Blvd. north of Sunrise Pkwy
- N. McDowell Blvd. north of Southpoint Blvd.
- N. McDowell Boulevard. & Corona Rd.
- N. McDowell Blvd. north of Corona Rd. (Post Office)
- N. McDowell Blvd. north of Ross St.
- 1368 N. McDowell Bl(Motel 6) south of Redwood Way
- Old Redwood Highway east of N. McDowell Blvd. (IHOP)
- 1330 Redwood Way at Holistic Institute
- 1367 N. McDowell Blvd. south of Redwood Way (Gateway SC)
- N. McDowell Blvd. north of Ross St.
- N. McDowell at Clegg
- N. McDowell Blvd. north of Rand St. (Post Office)
- N. McDowell Blvd. at Youngstown MHP
- N. McDowell Blvd. at Petaluma Estates MHP
- N. McDowell Blvd. south of Southpoint Blvd.
- N. McDowell Blvd. at Round Walk Circle
- N. McDowell Blvd. north of Dynamic St.
- N. McDowell Blvd. south of Rainier Drive (PT Admin)
- N. McDowell Blvd. north of Lynch Creek Way (Hospital)
- N. McDowell Blvd. at Petaluma Plaza S.C. North
- N. McDowell Blvd. at Petaluma Plaza SC South
- Lakeville Apartment #1 on Ely Blvd. S.
- Lakeville Apartment #2 on Frates Rd.
- Kaiser Medical Center on Cypress Dr.
- S. McDowell Blvd. Ext. west of Cypress Dr.
- 2000 S. McDowell Blvd. Ext. south of Cader Lane
- S. McDowell Blvd. Ext. north of Fisher Dr.
- Lakeville Hwy east of Casa Grande Rd. (USA Gas)
- Lakeville Hwy east of Marina Ave.
- Lakeville Hwy east of Baywood Dr.
- Lakeville Hwy west of Caulifield Lane
- Caulfield Ln. north of Lakeville Hwy
- St. Francis Dr. at Miwok School
- Lakeville Hwy @ Baywood Drive
- Payran St. at Jefferson St.
- 3860 Cypress Drive at UPS
- 3820 Cypress Drive south of S. McDowell Extension
- St. Francis Dr. at Lombardi Ave. (Caulifield)
- St. Francis Dr. south of Baywood Dr.
- S. McDowell Blvd. Ext. south of Lakeville Hwy
- Lakeville Hwy north of Wilson St (Silk Mill)
- Ely Blvd. South @ Capistrano Dr
- Sonoma Mtn Parkway west of E Washington St.
- Lindberg Lane east of S. Payran
- McNear Ave. and Country Club Dr (140)
- McNear Ave. and Mountain View Ave.
- Kelly Ln & Grant Ave (Grant Elementary School)
- Sunnyslope Rd. and Wallenberg Way
- El Rose Dr. and D St.
Over time
Overall score across the last 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 48.1 | first check |
| 2026-07-01 | 48.1 | no change |
| 2026-07-02 | 48.1 | no change |
| 2026-07-04 | 48.1 | no change |
| 2026-07-05 | 48.1 | no change |
| 2026-07-06 | 48.1 | no change |
| 2026-07-07 | 48.1 | no change |
| 2026-07-08 | 48.1 | no change |
| 2026-07-09 | 48.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error2 instances
Missing required column (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1105 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.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning2283 instances
2283 of 2283 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning152 instances
152 of 167 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning23 instances
Some service calendars in the feed have already expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
3 of 2283 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: 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
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.)
Validator rule: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info37 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · 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).
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 301, 311).
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.
147 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Lakeville Hwy @ Marina Ave. SB", "Lakeville Hwy @ Casa Grande Rd. SB", "Lakeville Hwy @ Caulfield Lane SB", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1105 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 1105 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 1105 days ago. States wheelchair access on 9% 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 1105 days ago.
- Accessible Not yet
- States wheelchair access on 9% 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.
- 14 of 167 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.
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 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. 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 (3 of 5 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.
- Gap Produce no critical errors in the MobilityData GTFS Validator
1 validator error to resolve.
- 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 9% of stops and 0% of trips.
- Not measured here shapes.txt with a shape for every trip
Shape coverage has not been measured for this feed.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 66 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 62 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/petaluma-transit-72/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.