← All agencies

Feed status · checked 2026-08-02

Stanford Marguerite Shuttle (SMS)

Based on the feed this agency publishes

Service mode Bus

FDCBA

92.9 / 100

unchanged since 2026-08-01

Catalogued in California.

Covers 320 daysRealtime not yet published

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 2 hours ago; last changed 25 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

Fix 01

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool

Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

⏱ Usually one export setting.worth about +8 points in its category

Fix 02

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

⏱ Often a bulk fix in your scheduling software.worth about +6 points in its category

Fix 03

Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

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.

⏱ A quick look at the flagged files.

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: Some route lines list the same point twice in a row.
Next action: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
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

Agency: Stanford Marguerite Shuttle (SMS)
Finding: equal_shape_distance_same_coordinates
Feed evidence: Some route lines list the same point twice in a row.
Why it matters: Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Requested change: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/stanford-marguerite-shuttle-sms/?finding=equal_shape_distance_same_coordinates#finding-handoff

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.

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 320 days.
Published accessibility data: Accessibility information is stated for 100% of stops and 100% 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.

Hi,

Our GTFS feed (Stanford Marguerite Shuttle (SMS)) scored A (92.9 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
   What: Some route lines list the same point twice in a row.
   Finding code: equal_shape_distance_same_coordinates
   Guide: https://gtfsscorecard.org/fix/equal_shape_distance_same_coordinates/

2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
   What: Some rider-facing names are in ALL CAPS or all lowercase.
   Finding code: mixed_case_recommended_field
   Guide: https://gtfsscorecard.org/fix/mixed_case_recommended_field/

3. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
   What: Some files contain columns that are not part of the GTFS spec.
   Finding code: unknown_column
   Guide: https://gtfsscorecard.org/fix/unknown_column/

Full scorecard: https://gtfsscorecard.org/agency/stanford-marguerite-shuttle-sms/

Score by category

Correctness83.8 / 100

The MobilityData validator flagged 6 kinds of issue across 288 instances (0 error, 263 warning, 25 informational).

Freshness100.0 / 100

Service data covers the next 320 days.

Rider experience100.0 / 100

100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility100 / 100

100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 186 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.

RWC Line (pink)
SE (pink)
RP PM (teal)
SE (pink)
Y Line (red)
P Line (white)
MC (purple)
1050A (brown)
X Line (red)
S Line (brown)
AE-F Line (gray)
RP AM (teal)
C Line (white)
YL-AM (red)
XL-AM (red)
C Line Limited AM/PM (white)
YL-PM (red)
XL-PM (red)
X Express AM (red)
Y Express PM (red)
OCA (gray)
HD (teal)
SLAC (green)
CAX (yellow)

Routes in Stanford Marguerite Shuttle (SMS)'s feed
Route	Type	Line color
RWC Line	Bus	pink
SE Shopping Express	Bus	pink
RP PM Research Park	Bus	teal
SE Shopping Express - Weekend	Bus	pink
Y Line	Bus	red
P Line	Bus	white
MC Medical Center	Bus	purple
1050A 1050 Arastradero	Bus	brown
X Line	Bus	red
S Line	Bus	brown
AE-F Line	Bus	gray
RP AM Research Park	Bus	teal
C Line	Bus	white
YL-AM Y Limited AM	Bus	red
XL-AM X Limited AM	Bus	red
C Line Limited AM/PM	Bus	white
YL-PM Y Limited PM	Bus	red
XL-PM X Limited PM	Bus	red
X Express AM	Bus	red
Y Express PM	Bus	red
OCA Oak Creek Apartments	Bus	gray
HD Hospital: Direct	Bus	teal
SLAC S L A C	Bus	green
CAX California Ave Caltrain	Bus	yellow

List every stop

On Jane Stanford Way @ Campus Oval
On Jane Stanford Way @ Burnham Pavilion
On Quarry Road @ Neuroscience Health Center
On Quarry Road @ Stanford Shopping Center
On Roth Way @ Campus Drive
On Roth Way @ Rodin Sculpture Garden
On Clark Way Across From Leasing Office
On Jane Stanford Way @ Encina Hall
On Stock Farm Road @ Parking Lot L-20
On Stock Farm Road @ Automotive Innovation Facility
PATC @ Bus Depot Bay # 6
On San Antonio Road @ El Camino Real NB
On Quarry Road @ Sweet Olive Way
PATC @ Bus Depot Bay #7
On Jane Stanford Way @ Campus Drive
On Welch Road @ LPCH
Hillview Avenue @ Watkins Johnson
Palo Alto Transit Center
On Showers Drive @ San Antonio Shopping Center
On Winslow Street @ Redwood City Caltrain
On El Camino Real NB @ California Avenue
On El Camino Real SB @ California Avenue
On Broadway @ Cardinal Hall
On Barron Avenue @ Discovery Hall
On Jane Stanford Way @ Manzanita Field
On Welch Road @ Pasteur Staff Garage
On Welch Road @ Blake Wilbur Drive
1000 Welch Road
900 Welch Road
780 Welch Road
On Olmsted Road @ Wellesley Street East
3300 Hillview Avenue
3375 Hillview Avenue
On Sand Hill Road @ Clark Way
On Clark Way @ Vi At Palo Alto
On Sand Hill Road @ Pasteur Drive
On El Camino Real SB @ Serra Street
Ardenwood Park & Ride (Line U/DB Stop)
Fremont BART (Line U Stop)
In Parking Lot @ SLAC Main Gate (Restricted Access)
1530 Page Mill Road
On N Pasteur Drive @ Sand Hill Road
On S Pasteur Drive @ Sand Hill Road
On Page Mill Road @ Peter Coutts Road
1501 Page Mill Road
On Walnut Avenue @ Liberty Street
On Campus Drive @ Parking Lot L-63
On Walnut Avenue @ Wells Fargo
On Fremont Blvd @ ACE Station
ACE Station (Fremont Boulevard @ Bonde Way)
On Campus Drive @ Li Ka Shing Center
On Campus Drive Across From Li Ka Shing Center
On Campus Drive @ Studio 2
On Roth Way @ Roth Way Garage
On Page Mill Road @ El Camino Real SB
1290 Page Mill Road @ Hanover Street
On Hillview Avenue @ Porter Drive
On Hillview Avenue @ Coyote Hill Road
3412 Hillview Avenue
1070 Arastradero Road @ Side Door
3495 Deer Creek Road
On Campus Drive @ Rains, Building # 238
3475 Deer Creek Road
3500 Deer Creek Road
Across From 3495 Deer Creek Road @ Arastradero Road
1070 Arastradero Road @ Front Door
3421 Hillview Avenue
3405 Hillview Avenue
On Porter Drive @ Hillview Avenue
Across From 1290 Page Mill Road @ Hanover Street
3145 Porter Drive
On Jane Stanford Way @ Main Quad
On Campus Drive @ Parking Lot L-62
Rosewood Hotel
On Campus Drive @ Vaden Health Center
On El Camino Real SB @ Page Mill Road
On El Camino Real NB @ Oregon Expressway
On El Camino Real SB @ Hansen Way
On Campus Drive @ Wilbur Field
On El Camino Real NB @ Portage Avenue
On El Camino Real SB @ Maybell Avenue
On El Camino Real NB @ El Camino Way
On California Street @ Pacchetti Way
On Panama Street @ Campus Drive
On Welch Road Across From LPCH
On Campus Drive @ Munger Graduate Residence
On Clark Way @ Leasing Oﬀice
On Via Ortega @ Cypress Hall
On Via Ortega @ Shriram Center
On Campus Drive @ Alvarado Row
On Campus Drive @ Parking Lot L-17
On Campus Drive @ Stock Farm Road
On Page Mill Road @ Hansen Way
965 Page Mill Road @ Hansen Way
On Welch Road @ Lucas Center For Imaging
On Welch Road @ Comparative Medicine Pavilion
On El Camino Real NB @ Park Avenue
On Campus Drive @ Mayfield Avenue North
On Olmsted Road @ Studio 6
3170 Porter Drive
3165 Porter Drive
On Quarry Road @ Vineyard Lane
On Campus Drive @ Mayfield Avenue South
On Bowdoin Street @ Pine Hill Court
Tresidder Union
On Embarcadero Road @ Wildwood Lane
On Embarcadero Road @ N California Avenue
On Bowdoin Street @ Rains Building # 227
Tresidder Union (Island)
On Quarry Extension @ Roth Way
On Campus Drive @ Parking Lot L-22
On Campus Drive Across From Parking Lot L-22
Oak Creek Apartments @ Building # 1824
On Santa Teresa Street @ Thornton Center
Oak Creek Apartments @ Club
Oak Creek Apartments @ Building # 1704
Oak Creek Apartments @ Building # 1470
Oak Creek Apartments @ Building # 1380
On Jane Stanford Way @ Memorial Auditorium
On Santa Teresa Street @ Papua New Guinea Sculpture Garden
On Campus Drive @ Sam McDonald Mall
On Campus Dr @ Koret Plaza
On Campus Drive @ Knight Management Center Garage
On Campus Drive @ Maples Pavilion
On Campus Drive @ Manzanita Field Garage
On Campus Drive @ Serra Street
On Serra Street @ EVGR 2 (C)
On Serra Street @ Fire Department
On Serra Street @ Hulme Court
On Serra Street @ Pampas Lane
SLAC Arrillaga Science Center (B057) (Restricted Access)
SLAC LCLS Office Building (B901) (Restricted Access)
Fremont Blvd & Mowry Ave
Fremont Blvd & Mowry Ave
Fremont Blvd & Tamayo St
Fremont Blvd & Tamayo St
On Porter Drive Near Page Mill Road
500 Pasteur Drive - HD Line
California Avenue Caltrain
On Jane Stanford Way @ ChEM-H Building
3460 Hillview Ave
1070 Arastradero
Across From 1070 Arastradero Road
On Hillview Ave @ Arastradero Rd
3373 Hillview Ave
On Jane Stanford Way Across From ChEM-H Building
On Santa Teresa Street @ Via Ortega
On Santa Teresa Street @ Lagunita Court
On Santa Teresa Street @ Governor’s Corner
On Santa Teresa Street @ Los Arboles Avenue
On Jane Stanford Way @ Hoover Tower
On Olmsted Road @ Barnes Court West
On Olmsted Road @ Barnes Court East
On Olmsted Road @ Yale Street East
On Olmsted Road @ Yale Street West
University Circle @ Platform East
500 Pasteur Drive - MC Line
University Circle @ Platform South
On Galvez Street @ El Camino Real SB
On El Camino Real NB @ Town & Country Village
On El Camino Real SB Across From PAMF
On El Camino Real NB @ PAMF
University Circle @ Caltrain Platform
On Quarry Road Across From Parking Lot L-3
On Quarry Road @ Parking Lot L-3
On Quarry Road Across From Psychiatry Building
On Quarry Road @ Psychiatry Building
On Quarry Extension @ Medical Center
On Quarry Extension Across From Medical Center
On Quarry Extension @ Grant Building
On Jane Stanford Way @ Gilbert Biological Sciences
On Galvez Street @ Visitor Center
On Jane Stanford Way @ David Packard Electrical Engineering
On Campus Drive @ Panama Street
On Campus Drive @ Welch Road
On Sand Hill Road Across From Sharon Park Drive
On Sand Hill Road @ Sharon Park Drive
Stock Farm Garage
In Parking Lot L-18 @ Oak Road
Across From Stock Farm Garage
On Sand Hill Road @ Oak Creek Apartments
On Sand Hill Road Across From Oak Creek Apartments
On Jane Stanford Way @ Lasuen Mall
Campus Oval
On Jane Stanford Way @ Graduate School Of Business
On Jane Stanford Way @ Schwab Residential Center

Over time

Overall score across the last 4 checks — unchanged since 2026-08-01.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	92.9	first check
2026-07-30	92.9	no change
2026-08-01	92.9	no change
2026-08-02	92.9	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-08-01.

Same feed file as 2026-08-01; 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

7 findings, ordered by severity.

Show every finding

Warning257 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning6 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Info16 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)
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info3 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
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)

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 320 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 764 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 Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.

[![GTFS conformance mark](https://gtfsscorecard.org/data/artifacts/stanford-marguerite-shuttle-sms/mark.svg)](https://gtfsscorecard.org/agency/stanford-marguerite-shuttle-sms/)

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 320 days.
Accessible Met: States wheelchair access on 100% of stops and 100% of trips.

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 320 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 (6 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.
Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
Meets shapes.txt with a shape for every trip
All 764 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 100 / 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.

[![Stanford Marguerite Shuttle (SMS) GTFS data quality grade: A](https://gtfsscorecard.org/data/artifacts/stanford-marguerite-shuttle-sms/badge.svg)](https://gtfsscorecard.org/agency/stanford-marguerite-shuttle-sms/)

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/stanford-marguerite-shuttle-sms/2026-08-02.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-02. 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.

GTFS Scorecard. (2026). Stanford Marguerite Shuttle (SMS) GTFS feed-quality record, dated 2026-08-02 (grade A (92.9/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 71089bae39ef…). https://gtfsscorecard.org/data/artifacts/stanford-marguerite-shuttle-sms/2026-08-02.json

@misc{gtfsscorecard-stanford-marguerite-shuttle-sms-2026-08-02,
  title        = {Stanford Marguerite Shuttle (SMS) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/stanford-marguerite-shuttle-sms/2026-08-02.json}},
  note         = {Checked 2026-08-02; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade A (92.9/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.