Feed status · checked 2026-08-01
San Diego International Airport, Metropolitan Transit System (MTS)
Based on the feed this agency publishes
Service mode Tram + Bus + Ferry
down 0.4 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 16 hours ago; last changed 24 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
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
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
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
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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
- Feed evidence
- Equal shape distance diff coordinates (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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
- 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
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.
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
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.
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 35 days.
- Published accessibility data
- Accessibility information is stated for 82.9% 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 v2.
- 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 1 routes · 258 trips
- Terminal structure
- 3 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- 100% of ferry boarding locations publish a value; 0% of all ferry boarding locations explicitly say allowed (0 of 3). Unstated values remain unknown. 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (258 of 258). Unstated values remain unknown. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 258 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 258 ferry trips publish cars_allowed.
- Fares
- Whole feed: applied fare data is published using GTFS Fares v2.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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 16 kinds of issue across 9757 instances (527 error, 9206 warning, 24 informational).
Service data covers the next 35 days.
83% of stops state wheelchair accessibility (72% marked accessible, 11% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
83% of stops state accessibility (72% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Green, Orange).
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.
4031 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("11th Ave & Broadway", "12th & Imperial Station", "12th & Imperial Station Bayside", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
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 4367 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (blue)
- 10 (blue)
- 105 (blue)
- 11 (blue)
- 115 (blue)
- 12 (blue)
- 120 (blue)
- 13 (blue)
- 14 (blue)
- 18 (blue)
- 2 (blue)
- 20 (blue)
- 201 (red)
- 202 (red)
- 204 (red)
- 215 (red)
- 225 (red)
- 227 (red)
- 235 (red)
- 237 (red)
- 25 (blue)
- 27 (blue)
- 28 (blue)
- 280 (red)
- 290 (red)
- 3 (blue)
- 30 (blue)
- 31 (blue)
- 35 (blue)
- 4 (blue)
- 41 (blue)
- 43 (blue)
- 44 (blue)
- 5 (blue)
- Blue (blue)
- Orange (orange)
- Green (green)
- Copper (brown)
- MTG Event Line (red)
- Silver (white)
- 6 (blue)
- 60 (blue)
- 7 (blue)
- 701 (blue)
- 704 (blue)
- 705 (blue)
- 707 (blue)
- 709 (blue)
- 712 (blue)
- 8 (blue)
- 815 (blue)
- 816 (blue)
- 83 (blue)
- 832 (blue)
- 833 (blue)
- 834 (blue)
- 838 (blue)
- 84 (blue)
- 848 (blue)
- 851 (blue)
- 852 (blue)
- 854 (blue)
- 855 (blue)
- 856 (blue)
- 864 (blue)
- 872 (blue)
- 874 (blue)
- 875 (blue)
- 88 (blue)
- 888 (brown)
- 891 (brown)
- 892 (brown)
- 894 (brown)
- 9 (blue)
- 901 (blue)
- 904 (blue)
- 905 (blue)
- 906 (blue)
- 907 (blue)
- 909 (blue)
- 910 (blue)
- 916 (blue)
- 917 (blue)
- 921 (blue)
- 923 (blue)
- 928 (blue)
- 929 (blue)
- 932 (blue)
- 933 (blue)
- 934 (blue)
- 936 (blue)
- 944 (blue)
- 945 (blue)
- 955 (blue)
- 961 (blue)
- 962 (blue)
- 963 (blue)
- 964 (blue)
- 965 (blue)
- 967 (blue)
- 968 (blue)
- 985 (blue)
- 992 (blue)
- Old Town to Airport Shuttle (blue)
| Route | Type | Line color |
|---|---|---|
| 1 Fashion Valley - La Mesa | Bus | blue |
| 10 Old Town - University/College | Bus | blue |
| 105 Old Town - University City | Bus | blue |
| 11 SDSU - Downtown San Diego | Bus | blue |
| 115 El Cajon T.C. - SDSU T.C. | Bus | blue |
| 12 12th & Imperial - Skyline Hills | Bus | blue |
| 120 Downtown San Diego - Kearny Mesa Transit Center | Bus | blue |
| 13 Kaiser Hospital - 24th St Transit Center | Bus | blue |
| 14 Grantville Trolley - Baltimore & Lake Murray | Bus | blue |
| 18 Grantville Trlly via Camino del Rio | Bus | blue |
| 2 Downtown San Diego - 30th & Adams | Bus | blue |
| 20 Downtown - Rancho Bernardo Transit Station | Bus | blue |
| 201 Super Loop - Counterclockwise | Bus | red |
| 202 Super Loop - Clockwise | Bus | red |
| 204 Super Loop - Judicial Dr. | Bus | red |
| 215 Mid-City Rapid | Bus | red |
| 225 Downtown - Otay Mesa TC | Bus | red |
| 227 Imperial Beach - Otay Mesa TC | Bus | red |
| 235 Downtown - Escondido Transit Center | Bus | red |
| 237 Miramar College Transit Station - UCSD | Bus | red |
| 25 Fashion Valley - Kearny Mesa TC | Bus | blue |
| 27 Pacific Beach - Kearny Mesa Transit Center | Bus | blue |
| 28 Old Town T.C. - Shelter Island | Bus | blue |
| 280 Escondido Transit Center - Downtown | Bus | red |
| 290 Sabre Springs Station - Downtown | Bus | red |
| 3 UCSD Hospital - Euclid Transit Center | Bus | blue |
| 30 Old Town - UTC via Pacific Beach | Bus | blue |
| 31 UTC - Mira Mesa | Bus | blue |
| 35 Ocean Beach - Old Town | Bus | blue |
| 4 12th & Imperial Trolley - Lomita Village | Bus | blue |
| 41 Fashion Valley - UCSD | Bus | blue |
| 43 Balboa Av TC - Kearny Mesa | Bus | blue |
| 44 Old Town - Kearny Mesa | Bus | blue |
| 5 Downtown San Diego - Euclid Transit Center | Bus | blue |
| Blue San Ysidro - UTC | Tram / light rail | blue |
| Orange El Cajon - Courthouse | Tram / light rail | orange |
| Green El Cajon - 12th & Imperial | Tram / light rail | green |
| Copper Santee - El Cajon | Tram / light rail | brown |
| MTG Event Line Magic: The Gathering Event Line | Tram / light rail | red |
| Silver Downtown Loop | Tram / light rail | white |
| 6 North Park - Fashion Valley | Bus | blue |
| 60 Euclid Av Transit Center - UTC via Convoy | Bus | blue |
| 7 Downtown San Diego - University/College | Bus | blue |
| 701 H St Transit Center - Palomar St TC via Hilltop Dr | Bus | blue |
| 704 E St Transit Center - Palomar Transit Center | Bus | blue |
| 705 E St Transit Center - Plaza Bonita | Bus | blue |
| 707 Otay Ranch Town Center - Southwestern College | Bus | blue |
| 709 H St Transit Center - Otay Ranch Town Center | Bus | blue |
| 712 Palomar Transit Center - Southwestern College | Bus | blue |
| 8 Old Town - Balboa Av TC | Bus | blue |
| 815 El Cajon Transit Center - East Main St | Bus | blue |
| 816 El Cajon TC - Cuyamaca College | Bus | blue |
| 83 Downtown San Diego - Old Town | Bus | blue |
| 832 Santee Center - NE Santee Loop Clockwise | Bus | blue |
| 833 Santee Center - Parkway Plaza | Bus | blue |
| 834 West Santee Loop | Bus | blue |
| 838 East County Square - Viejas | Bus | blue |
| 84 Point Loma Shuttle | Bus | blue |
| 848 El Cajon - Lakeside | Bus | blue |
| 851 Spring Valley - La Mesa | Bus | blue |
| 852 University & 54th - Grossmont Transit Ctr | Bus | blue |
| 854 Grossmont Transit Ctr -- Grossmont College | Bus | blue |
| 855 Rancho San Diego - La Mesa | Bus | blue |
| 856 SDSU - Cuyamaca College | Bus | blue |
| 864 El Cajon - East County Sq | Bus | blue |
| 872 El Cajon Shuttle Loop Counterclockwise | Bus | blue |
| 874 El Cajon Eastside Shuttle Clockwise | Bus | blue |
| 875 El Cajon Eastside Shuttle Counterclockwise | Bus | blue |
| 88 Old Town - Hotel Circle | Bus | blue |
| 888 Jacumba - El Cajon | Bus | brown |
| 891 Borrego - El Cajon via Shelter Valley | Bus | brown |
| 892 Borrego - El Cajon via Ranchita/Lake Henshaw | Bus | brown |
| 894 Morena/Campo - El Cajon | Bus | brown |
| 9 Old Town - Jewell & Garnet | Bus | blue |
| 901 Iris Transit Center - Downtown | Bus | blue |
| 904 Coronado Shuttle | Bus | blue |
| 905 Iris Transit Center - Otay Mesa Transit Center | Bus | blue |
| 906 Iris Transit Center - San Ysidro Clockwise | Bus | blue |
| 907 Iris Transit Center - San Ysidro Counterclockwise | Bus | blue |
| 909 Otay Mesa Transit Center - SWC at Otay Mesa | Bus | blue |
| 910 Downtown - San Ysidro (OWL Service) | Bus | blue |
| 916 Oak Park-Emerald Hills Loop CW | Bus | blue |
| 917 Oak Park-Emerald Hills Loop CCW | Bus | blue |
| 921 UTC - Miramar College Transit Station | Bus | blue |
| 923 Downtown to Point Loma | Bus | blue |
| 928 Fashion Valley - Kearny Mesa | Bus | blue |
| 929 12th & Imperial - Iris Transit Center | Bus | blue |
| 932 Iris Transit Center - 8th St. Transit Center | Bus | blue |
| 933 Iris TC Loop - Imperial Beach Counterclock | Bus | blue |
| 934 Iris TC Loop - Imperial Beach Clockwise | Bus | blue |
| 936 Spring Valley - SDSU | Bus | blue |
| 944 Sabre Springs Station - Poway | Bus | blue |
| 945 Rancho Bernardo Station - Poway | Bus | blue |
| 955 National City - San Diego State University | Bus | blue |
| 961 24th St Transit Center - Encanto Trolley | Bus | blue |
| 962 8th St Transit Center - Spring Valley | Bus | blue |
| 963 8th St Transit Center - Paradise Hills | Bus | blue |
| 964 Mira Mesa - Alliant University via MCTS | Bus | blue |
| 965 City Heights Shuttle | Bus | blue |
| 967 24th St Transit Center - Division & Ava | Bus | blue |
| 968 8th St Transit Center - Plaza Bonita | Bus | blue |
| 985 UCSD Central Campus Station - Torrey Pines | Bus | blue |
| 992 Airport/Downtown Shuttle | Bus | blue |
| Old Town to Airport Shuttle | Bus | blue |
| Coronado Ferry | Ferry | blue (no shape in feed) |
List every stop
- Cabrillo National Monument
- Pearl St & Draper Av
- Pearl St & Fay Av
- Torrey Pines Rd & Exchange Pl
- Torrey Pines Rd & Princess St
- Garnet Av & Everts St
- Grand Av & Fanuel St
- Garnet Av & Haines St
- Garnet Av & Ingraham St
- Garnet Av & Jewell St
- Voltaire St & Mendocino St
- Garnet Av & Lamont St
- Voltaire St & San Clemente St
- Garnet Av & Noyes St
- Chatsworth Bl & Tennyson St
- Voltaire St & Poinsettia Dr
- West Point Loma Bl & Adrian St
- Nimitz Bl & Rosecrans St
- Grand Av & Culver St
- West Point Loma Bl & Loma Riviera Dr
- Nobel Dr & Lebon Dr
- Garnet Av & Bond St
- Sports Arena Bl & Midway Dr
- Midway Dr & Duke St
- Midway Dr & Kemper St
- Grand Av & Mission Bay Dr
- Balboa Av & Moraga Av
- Morena Bl & Frankfort St
- Governor Dr & Radcliffe Dr
- Morena Bl & Knoxville St
- Clairemont Dr & Merrimac Av
- Linda Vista Rd & Colusa St
- Taylor St & I-8 East (Ramp)
- Clairemont Mesa Bl & Longford St
- Miramar Rd & Miramar Mall
- N Harbor Dr & Laurel St (Coast Guard)
- Lewis St & Stephens St
- Clairemont Mesa Bl & Limerick Av
- Lewis St & Ingalls St
- Miramar Rd & Milch Rd
- Broadway & State St
- Washington St & Albatross St
- Broadway & Front St
- Clairemont Mesa Bl & Shawline St (Kaiser)
- University Av & 3rd Av
- Genesee Av & Richland St
- Broadway & 3rd Av
- Miramar Rd & Distribution Av
- Broadway & 5th Av
- University Av & 5th Av
- Broadway & 6th Av
- Camino De La Reina & Camino Del Arroyo
- Market St & 10th Av
- University Av & 10th Av
- Miramar Rd & Carroll Rd
- Market St & Park Bl
- Broadway & Park Bl
- Vista Hill Av & Meadowlark Dr
- University Av & Vermont St
- University Av & Richmond St
- Imperial Av & 16th St
- Market St & 16th St
- Logan Av & Sigsbee St
- Market St & 19th St
- Broadway & 20th St
- Logan Av & Cesar E Chavez Pkwy
- Imperial Av & 22nd St
- Miramar Rd & Dowdy Dr
- Imperial Av & 24th St
- Clairemont Mesa Bl & 8303
- El Cajon Bl & Alabama St
- University Av & Alabama St
- Miramar Rd & Cabot Dr
- Market St & 25th St
- Broadway & 25th St
- University Av & Louisiana St
- Imperial Av & 26th St
- C St & 26th St
- El Cajon Bl & Arizona St
- Adams Av & Arizona St
- Mira Mesa Bl & Reagan Rd (E)
- Main St & 27th St
- Ocean View Bl & Sampson St
- Imperial Av & Hensley St
- C St & 28th St
- Mira Mesa Bl & Westonhill Dr
- El Cajon Bl & Utah St
- National Av & 29th St
- Balboa Av & Ponderosa Av
- Aero Dr & Corporate Ct
- Market St & 30th St
- Clairemont Mesa Bl & Overland Av
- Adams Av & 30th St
- University Av & 30th St
- Upas St & 30th St
- Ocean View Bl & 30th St
- Imperial Av & 30th St
- Main St & 30th St
- C St & 30th St
- Beech St & Fern St
- Mira Mesa Bl & Marbury Av
- Adams Av & Boundary St
- Market St & 31st St
- Balboa Av & Ruffin Rd
- Ocean View Bl & 32nd St
- Imperial Av & 32nd St
- Market St & 32nd St
- Clairemont Mesa Bl & Ruffin Rd
- Camino Del Rio N & Mission City Pkwy
- Clairemont Mesa Bl & Ruffin Rd
- Market St & 33rd St
- Ocean View Bl & 33rd St
- Imperial Av & 33rd St
- Adams Av & 33rd St
- El Cajon Bl & 33rd St
- El Cajon Bl & 35th St
- Aero Dr & West Canyon Av
- Camino Del Rio S & Scheidler Wy
- National Av & 35th St
- El Cajon Bl & 35th St
- National Av & 36th St
- Adams Av & 35th St
- El Cajon Bl & 36th St
- Imperial Av & 37th St
- El Cajon Bl & 37th St
- National Av & 38th St
- Ocean View Bl & 38th St
- Imperial Av & 38th St
- University Av & 38th St
- Camino Del Rio S & 3661
- National Av & 40th St
- Carmel Mountain Rd & Freeport Rd
- Imperial Av & 40th St
- Home Av & Hixson Av
- National Av & 41st St
- Market St & Morrison St
- Ocean View Bl & San Miguel Av
- Adams Av & Biona Dr
- Market St & Denby St
- National Av & San Pasqual St
- 8th St & F Av
- Carmel Mountain Rd & Stoney Creek Rd
- Home Av & Fairmount Av
- Ocean View Bl & Elizabeth St
- Imperial Av & 45th St
- Logan Av & 47th St
- Ocean View Bl & 47th St
- Zion Av & Crawford St (Kaiser)
- University Av & 47th St
- University Av & Estrella Av
- El Cajon Bl & 54th St
- University Av & 52nd St
- Zion Av & 51st St
- E St & 3rd Av
- Olvera Av & Gwen St
- Zion Av & Waring Rd
- El Cajon Bl & 54th St
- Montezuma Rd & 54th St
- Olvera Av & San Onofre Ter
- El Cajon Bl & Dayton St
- Grape St & 55th St
- College Av & El Cajon Bl
- Olvera Av & Las Flores Ter
- Roswell St & Kelton Rd
- Streamview Dr & Lynn St
- Market St & Merlin Dr
- Skyline Dr & Radio Dr
- Rancho Bernardo Rd & Acena Dr
- Del Sol Bl & Ocean Bluffs
- Imperial Av & 62nd St
- Montezuma Rd & 63rd St
- Imperial Av & 63rd St
- Rancho Bernardo Rd & Bernardo Oaks Dr
- Streamview Dr & Hasty Dr
- Rancho Bernardo Rd & Meandro Dr
- Skyline Dr & Detroit Pl
- Montezuma Rd & Reservoir Dr
- Imperial Av & Woodman St
- Skyline Dr & Woodman St
- University Av & Aragon Dr
- El Cajon Bl & Montezuma Rd
- Imperial Av & 68th St
- Imperial Av & 69th St
- Skyline Dr & 69th St
- University Av & 69th St
- Skyline Dr & Buccaneer Dr
- Skyline Dr & Sychar Rd
- El Cajon Bl & 73rd St
- El Cajon Bl & Jessie Av
- Skyline Dr & Siena St
- University Av & Lowell St
- El Cajon Bl & Parks Av
- Jackson Dr & Lake Shore Dr
- Jamacha Rd & Glencoe Dr
- Main St & Broadway (Lemon Grove Depot)
- University Av & Maple Av
- Jackson Dr & Cowles Mountain Bl
- University Av & La Mesa Bl
- Paradise Valley Rd & Meadowbrook Dr
- Jamacha Rd & Cardiff St
- University Av & Allison Av
- San Vicente St & Cardiff St
- Jackson Dr & Lake Badin Av
- Allison Av & Spring St
- Jackson Dr & Boulder Lake Av
- Allison Av & Palm Av
- La Mesa Bl & University Av
- Sweetwater Rd & Jamacha Rd
- La Mesa Bl & Glen St
- Orville St & Brucker Av
- La Mesa Bl & Jackson Dr
- Navajo Rd & Jaffe Ct
- La Mesa Bl & Garfield St
- Pearl St & La Jolla Bl
- Silverado St & Herschel Av
- Torrey Pines Rd & Prospect St
- Turquoise St & La Jolla Bl
- Grand Av & Bayard St
- Garnet Av & Cass St
- W Mission Bay Dr & Mission Bl
- Grand Av & Cass St
- W Mission Bay Dr & Mariners Wy
- Garnet Av & Fanuel St
- Voltaire St & Sunset Cliffs Bl
- West Point Loma Bl & Sunset Cliffs Bl
- Voltaire St & Ebers St
- La Jolla Village Dr & N. Torrey Pines Rd
- Voltaire St & Froude St
- Grand Av & Ingraham St
- Voltaire St & Soto St
- W Mission Bay Dr & Quivira Rd
- Gilman Dr & Myers Dr
- Grand Av & Lamont St
- La Jolla Village Dr & Villa La Jolla Dr
- West Point Loma Bl & Temecula St
- Voltaire St & Las Lomas St
- Macaulay St & Tustin St
- Garnet Av & Olney St
- Grand Av & Olney St
- Garnet Av & Fogg St
- Garnet Av & Soledad Mountain Rd
- La Jolla Village Dr & Lebon Dr
- West Point Loma Bl & Groton St
- Garnet Av & Mission Bay Dr
- Nobel Dr & Regents Rd
- La Jolla Village Dr & Regents Rd
- Governor Dr & Regents Rd
- Governor Dr & Scripps St
- Clairemont Mesa Bl & Moraga Av
- Governor Dr & Stadium St
- and 4117 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 47.4 | first check |
| 2026-07-30 | 45.3 | down 2.1 |
| 2026-07-31 | 44.9 | down 0.4 |
| 2026-08-01 | 44.5 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-31.
Same feed file as 2026-07-31; 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
18 findings, ordered by severity.
Show every finding
- Error464 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error63 instances
Equal shape distance diff coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8480 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)
- Warning748 instances
748 of 4367 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)
- Warning258 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning227 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning126 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning103 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle 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)
- Warning4 instances
Some service calendars in the feed have already ended.
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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · 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)
- Info20 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)
- Info2 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)
- 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)
- Info1 instance
Unused station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unused_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 2 validator errors to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Ready
- Service data covers the next 35 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 MTS, SAN; your National Transit Database ID is 90026. 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 MTS, SAN to NTD ID 90026, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Needs attention
- 21175 of 21433 trips have a shape; 258 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
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. 2 validator errors to resolve. States wheelchair access on 83% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 35 days.
- Accessible Not yet
- States wheelchair access on 83% of stops and 100% 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.
- 5 of 4264 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 35 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 527 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 (3 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.
- Gap Produce no critical errors in the MobilityData GTFS Validator
2 validator errors 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 83% of stops and 100% of trips.
- Gap shapes.txt with a shape for every trip
21175 of 21433 trips have a shape; 258 do not.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 0 / 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 58 / 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 96 / 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/san-diego-international-airport-metropolitan-transit-system-mts/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.