Feed status · checked 2026-10-31
SunLine Transit Agency
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-30
Cataloged in California.
Source feed: http://www.sunline.org/transit/google_transit.zip
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.
Checked for changes 79 minutes ago; last changed 132 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
SunLine Transit Agency’s published feed lists 19 bus routes, 1,184 scheduled trips and 574 stops. Its service dates run from 2025-05-06 through 2025-12-31. The published file has not changed since our first check on 2026-06-16.
Top things to fix
Correct feed_end_date in feed_info.txt. Set it to 2026-05-06, the last day in your calendar, or to the last day your schedule is reliable.Likely your export tool
feed_info.txt says this feed ends on 2025-12-31. Your service calendar runs to 2026-05-06. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.
This one is about the feed as a whole, so there is no share of it to count.
⏱ One field in feed_info.txt, often an export setting.worth about +100 points in its category
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Varies.worth about +24 points in its category
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Varies.worth about +24 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-26.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Fix 01 · Read the fix guide for scorecard_feed_end_date_before_calendar
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.
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.
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 was 304 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send 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.
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 12 kinds of issue across 3584 instances (1542 error, 2037 warning, 5 informational).
Your feed_info end date, 2025-12-31, is earlier than your service calendar, which runs to 2026-05-06. The feed is read as ending on that earlier date, 304 day(s) ago.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (5, 8, 11, 200, 700).
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.
222 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Hwy 111 at Monroe", "Hwy 111 at Las Palmas", "Indio Blvd at Transportation Cen", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 574 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 (yellow)
- 10 (blue)
- 11 (green)
- 2 (red)
- 200 (teal)
- 3 (gray)
- 4 (yellow)
- 5 (white)
- 500 (yellow)
- 6 (pink)
- 7 (purple)
- 700 (teal)
- 701 (green)
- 8 (orange)
- 800 (purple)
- 801 (gray)
- 802 (red)
- 803 (green)
- 9 (black)
| Route | Type | Line color |
|---|---|---|
| 1 Route 1 West Valley | Bus | yellow |
| 10 Route 10 Commuter Link | Bus | blue |
| 11 Route 1 East Valley | Bus | green |
| 2 Route 2 | Bus | red |
| 200 Route 200 Tripper | Bus | teal |
| 3 Route 3 | Bus | gray |
| 4 Route 4 | Bus | yellow |
| 5 Route 5 | Bus | white |
| 500 Route 500 Tripper | Bus | yellow |
| 6 Route 6 | Bus | pink |
| 7 Route 7 | Bus | purple |
| 700 Route 700 Tripper | Bus | teal |
| 701 Route 701 Tripper | Bus | green |
| 8 Route 8 | Bus | orange |
| 800 Route 800 Tripper | Bus | purple |
| 801 Route 801 Tripper | Bus | gray |
| 802 Route 802 Tripper | Bus | red |
| 803 Route 803 Tripper | Bus | green |
| 9 Route 9 | Bus | black |
List every stop
- Palm at Two Bunch Palms
- Palm Canyon at Via Escuela
- Hwy 111 at Monroe
- Hwy 111 at Las Palmas
- Varner at Harry Oliver
- Indio Blvd at Transportation Cen
- Hwy 111 at Clinton
- Hwy 111 at Shields
- Monroe at Shadow Palm
- Monroe at Hoover
- Jackson at Date
- Ave 50 at Cesar Chavez
- Cesar Chavez at Bagdad
- Jackson at Ave 42
- Palm Canyon at Sonora
- Palm Canyon at Stevens
- Palm Canyon at Vereda Del Sur
- Vista Chino at Executive
- Sunrise Way & Vista Chino
- N Palm Canyon at Chino
- N Palm Canyon at Amado
- Tahquitz Canyon at Sunrise Way
- Palm Canyon at Arenas
- Palm Canyon at Baristo
- Ramon at Indian Canyon
- Palm Canyon at Camino Real
- Ramon at Calle Palo Fierro
- Ramon at Camino Real
- Ramon at Grenfall
- Two Bunch Palms at Palm
- Two Bunch Palms at West
- West at Granada
- Hacienda at Palm
- Airport at Desert Cactus Dr.
- Palm Canyon & Sunrise
- Ramon at Desert Way
- Ramon at El Placer
- Ramon at Paseo Dorotea
- Ramon at Vella
- B St at Buddy Rogers
- Ramon at Rattler
- Monterey at Park View
- Palm Canyon at Gene Autry
- Rosa Parks & Eastgate
- Rosa Parks at Eastgate
- 66th at SR86
- Vista Chino at Desert Princess
- Palm Canyon at Golf Club
- Vista Chino & Landau
- Ave Maravilla at Risueno
- Vista Chino at Landau
- Vista Chino at Ave Quintana
- Vista Chino at Carmela
- Palm Canyon & Bankside
- Ramon at Kirk Douglas
- Ramon at Paseo Dorotea
- Vista Chino at Sunrise Way
- Ramon at El Placer
- El Cielo at Kirk Douglas
- Tahquitz Canyon at Farrell
- Ramon at Sunrise
- Ramon at Hermosa
- Ramon at Avn Caballeros
- Palm Canyon at Bankside
- Fred Waring & Portola
- Fred Waring at Portola
- Indian Canyon at Amado
- Indian Canyon at Tamarisk
- Indian Canyon at Camino Monte Vista
- Hwy 111 at Jackson
- Monterey at Fred Waring
- Racquet Club at Indian Canyon
- Palm at Hacienda
- Palm Canyon at Eagle Cyn
- Palm Canyon at Racquet Club
- Palm Canyon at Yorba
- Fred Waring at Cook
- Rosa Parks at Granada
- Cook & Frank Sinatra
- Cook at Berger
- Cook at Frank Sinatra
- Cook at University Park
- Palm Canyon at Golf Club
- Gateway & Palm Canyon
- Gateway at Palm Canyon
- Palm Canyon at San Marco Way
- Ramon at Sky Blue Water
- Grapefruit at Ave 48
- Fred Waring at Cook
- Cesar Chavez at 6th St
- Palm Canyon at Escoba
- 66th at Tyler
- 70th at Lopez
- Fred Waring & Washington
- San Rafael & Avn Caballeros
- San Rafael at Avn Caballeros
- Indian Cyn at San Rafael
- San Rafael at Indian Cyn
- Rosa Parks at Granada
- Vista Chino at Gene Autry
- Palm Canyon at Sunrise
- Monterey at Hovley
- Dinah Shore at Bob Hope
- Bob Hope at Dinah Shore
- E Palm Canyon at Allen
- Cathedral Cyn at Officer D Vsqz
- Perez at Cathedral Canyon
- Indian Canyon at Andreas
- Monterey & Broadmoor
- Monterey at Broadmoor
- Fred Waring at Washington
- Fred Waring & Adams
- Indian Canyon at Baristo
- Fred Waring at Adams
- Fred Waring & Jefferson
- Fred Waring at Jefferson
- Fred Waring & Clinton
- Indian Canyon at Alejo
- Fred Waring at Clinton
- Hwy 111 & Village Center
- Hwy 111 at Village Center
- Ramon at Sky Blue Water
- 66th at Martinez
- Indian Canyon at Tachevah
- Tahquitz Canyon at Calle Encila
- Fred Waring at Palm Royal
- Ramon at Desert Shadows
- Fred Waring & Warner
- Cook at Country Club
- Fred Waring at Town Center
- Cook at Sheryl
- Date Palm at 30th
- Cook at Aztec
- Date Palm at Ramon
- Date Palm at McCallum
- 30th at Date Palm
- Washington at Eisenhower
- Fred Waring at Warner
- Eisenhower at Calle Durango
- Eisenhower at Calle Ensenada
- Eisenhower at Calle Chihuahua
- Eisenhower at Calle Colima
- Eisenhower at Calle Chillon
- Van Buren at Rancho Las Flores
- Hwy 111 at Plaza
- Tahquitz Canyon at Civic
- Avn Obregon at Calle Colima
- Fred Waring & Deep Cyn
- Avn Obregon at Calle Durango
- Avn Obregon at Calle Ensenada
- Fred Waring at Deep Canyon
- Fred Waring & Madison
- Washington at Calle Tampico
- Fred Waring at Madison
- Palm at Estrella
- Pierson@West
- Grapefruit at Ave 49
- Cesar Chavez & Grapefruit
- Harrison at Grapefruit
- Monroe at Hwy 111
- Monroe at Dr Carreon
- Monroe at Ave 48
- Ave 48 at Oasis
- Monroe & Ave 48
- Monroe & Dr Carreon
- Monroe & Hwy 111
- Cesar Chavez at Ave 52
- Ave 50 at Van Buren
- Ramon at Landau
- Monroe at Fred Waring
- Calhoun at Ave 50
- Calhoun at Ave 49
- Jackson at Requa
- Two Bunch Palms at Cactus
- Vista Chino at Val Yermo
- Maravilla at Tachevah
- Maravilla at Risueno
- Ramon at Companile
- Ramon at San Luis Rey
- Monroe at Miles
- Hwy 111 at Clinton
- Jackson at Dr Carreon
- Jackson at Ave 44
- Ramon at Canyon Vista
- Monterey at Hovley
- Fred Waring at Hwy 111
- Jackson & Showcase
- Dr Carreon at Jackson
- Calhoun at Ave 48
- El Cielo at Baristo
- El Cielo at Ramon
- Calhoun & Ave 49
- Ave 50 at Frederick
- Ave 50 at Cesar Chavez
- Calhoun & Ave 50
- Cesar Chavez at Ave 50
- Ave 50 at Frederick
- 5th at Date Palm
- 5th at Dale Kiler
- Dr Carreon at Van Buren
- Van Buren at Dr.Carreon
- Ramon at Landau
- Van Buren & Ave 48
- Monroe at Requa
- Lincoln & 7th
- Ave 48 at Jackson
- Lincoln at 7th
- Hwy 111 at Las Palmas
- Monroe at Santa Rosa
- 66th at Filmore
- Van Buren & Manila
- Van Buren at Manila
- Ramon at Calle El Segundo
- Harrison at Middleton
- Mountain View at Harrison
- Hammond & Thobe
- Hammond at Thobe
- 70th & Windward
- 70th at Windward
- 70th & Vander Veer
- 70th at Vander Veer
- Ramon at Farrell
- Vista Chino & Farrell
- Miramar & Lookout
- Miramar at Lookout
- Costa Brava & Salton View
- Costa Brava at Salton View
- Club View at Windlass
- Date Palm at McCallum
- Date Palm at Baristo
- Date Palm at Ortega
- Ramon at Rosemary
- Rosa Parks & Frontage
- Rosa Parks at Frontage
- Hwy 111 at Fairway
- Ramon at Monterey
- Cesar Chavez at Ave 52
- 2nd at Commerce
- Date Palm at Dinah Shore
- Golf Center & Avenue 43
- Golf Center at Avenue 43
- Ramon at Da Vall
- Ramon at Thelma
- Ramon at Shelter
- Ramon at Varner
- Date Palm & 35th
- Ramon at Braille Institute
- 66th at Mecca Family HC
- 66th at Date Palm
- Tahquitz Canyon at Civic
- and 324 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 30 checks — unchanged since 2026-10-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 20.3 | first check |
| 2026-10-03 | 20.3 | no change |
| 2026-10-04 | 20.3 | no change |
| 2026-10-05 | 20.3 | no change |
| 2026-10-06 | 20.3 | no change |
| 2026-10-07 | 20.3 | no change |
| 2026-10-08 | 20.3 | no change |
| 2026-10-09 | 20.3 | no change |
| 2026-10-10 | 20.3 | no change |
| 2026-10-11 | 20.3 | no change |
| 2026-10-12 | 20.3 | no change |
| 2026-10-13 | 20.3 | no change |
| 2026-10-14 | 20.3 | no change |
| 2026-10-15 | 20.3 | no change |
| 2026-10-16 | 20.3 | no change |
| 2026-10-17 | 20.3 | no change |
| 2026-10-18 | 20.3 | no change |
| 2026-10-19 | 20.3 | no change |
| 2026-10-20 | 20.3 | no change |
| 2026-10-21 | 20.3 | no change |
| 2026-10-22 | 20.3 | no change |
| 2026-10-23 | 20.3 | no change |
| 2026-10-24 | 20.3 | no change |
| 2026-10-25 | 20.3 | no change |
| 2026-10-26 | 20.3 | no change |
| 2026-10-27 | 20.3 | no change |
| 2026-10-28 | 20.3 | no change |
| 2026-10-29 | 20.3 | no change |
| 2026-10-30 | 20.3 | no change |
| 2026-10-31 | 20.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-31 (30 checks) | 621e5e262dbb | 2025-12-31 | Current rubric: see the trend above |
| 2026-07-25 to 2026-10-01 (65 checks) | 621e5e262dbb | 2025-12-31 | F, 20.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-24 (8 checks) | 621e5e262dbb | 2025-12-31 | F, 20.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-16 to 2026-07-13 (26 checks) | 621e5e262dbb | 2025-12-31 | F, 20.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-30.
Same feed file as 2026-10-30; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
16 findings, ordered by severity.
Show every finding
- Error1140 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)
- Error402 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
feed_info.txt says this feed ends on 2025-12-31. Your service calendar runs to 2026-05-06.
The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.
Fix: Correct feed_end_date in feed_info.txt. Set it to 2026-05-06, the last day in your calendar, or to the last day your schedule is reliable. (One field in feed_info.txt, often an export setting.)
Finding code: scorecard_feed_end_date_before_calendar · Read the fix guide for scorecard_feed_end_date_before_calendar · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1185 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1184 instances
1184 of 1184 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning799 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 streets or point riders to the wrong corner.
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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning574 instances
574 of 574 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning44 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 for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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 for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules 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.)
Finding code: feed_expiration_date7_days · Read the fix guide for feed_expiration_date7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · 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.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 304 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 304 days ago, so FTA would find the link out of date.
- 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 1184 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed does not meet the conformance requirements yet. Here is what the mark needs: 2 validator errors to resolve. Service data expired 304 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 304 days ago.
- Accessible Not yet
- States wheelchair access on 0% 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.
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 1542 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.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 1184 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 9 / 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 0 / 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 52 / 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.
Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in California
Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/sunline-transit-agency/2026-10-31.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-10-31. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.