Feed status · checked 2026-11-21
South Florida Regional Transportation Authority (Tri-Rail)
Based on the feed source on file; publisher ownership is not verified
Service mode Rail + Bus
unchanged since 2026-11-20
Cataloged in Florida.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://gtfs.tri-rail.com/gtfs.zip
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Correct feed_end_date in feed_info.txt. Set it to 2027-12-31, 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 2026-10-20. Your service calendar runs to 2027-12-31. 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
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Export and publish an updated GTFS feed that covers at least the next 30 days of service.Likely your export tool
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.
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.
⏱ Usually a re-export from your scheduling software.worth about +4 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.
- Florida 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-11-02.
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for feed_expiration_date7_days
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date was 32 days ago.
- 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
- No fare information is published in the feed.
- 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
South Florida Regional Transportation Authority (Tri-Rail)’s published feed lists 3 routes (rail and bus), 245 scheduled trips and 23 stops. Its service dates run from 2023-05-31 through 2026-10-20. The published file last changed on 2026-11-09.
Score by category
The MobilityData validator flagged 4 kinds of issue across 5 instances (0 error, 2 warning, 3 informational).
Your feed_info end date, 2026-10-20, is earlier than your service calendar, which runs to 2027-12-31. The feed is read as ending on that earlier date, 32 day(s) ago.
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 not published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (TRIRAIL, FLA1).
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.
1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Terminal 2/3").
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.
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 23 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.
- TRIRAIL (teal)
- TRDML (yellow)
- FLA1 (orange)
| Route | Type | Line color |
|---|---|---|
| TRIRAIL Mainline | Rail | teal |
| TRDML Downtown Miami Link | Rail | yellow |
| FLA1 Fort Lauderdale Airport Shuttle | Bus | orange |
List every stop
- Mangonia Park Station
- Fort Lauderdale Station
- Fort Lauderdale Airport Station
- Sheridan Street Station
- Hollywood Station
- Golden Glades Station
- Opa-Locka Station
- Metrorail Transfer Station
- Hialeah Market Station
- Miami Airport Station
- MiamiCentral Station
- West Palm Beach Station
- Tri-Rail FLL Airport Station
- Terminal 1
- Terminal 2/3
- Terminal 4
- Lake Worth Beach Station
- Boynton Beach Station
- Delray Beach Station
- Boca Raton Station
- Deerfield Beach Station
- Pompano Beach Station
- Cypress Creek Station
Over time
Overall score across the last 13 checks — unchanged since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 64.0 | first check |
| 2026-11-10 | 64.0 | no change |
| 2026-11-11 | 64.0 | no change |
| 2026-11-12 | 64.0 | no change |
| 2026-11-13 | 64.0 | no change |
| 2026-11-14 | 64.0 | no change |
| 2026-11-15 | 64.0 | no change |
| 2026-11-16 | 64.0 | no change |
| 2026-11-17 | 64.0 | no change |
| 2026-11-18 | 64.0 | no change |
| 2026-11-19 | 64.0 | no change |
| 2026-11-20 | 64.0 | no change |
| 2026-11-21 | 64.0 | 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-11-09 to 2026-11-21 (13 checks) | e27b9018c46f | 2026-10-20 | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 3b5e21e09f76 | 2025-12-31 | F, 56.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-08-02 to 2026-10-01 (57 checks) | 3b5e21e09f76 | 2025-12-31 | F, 56.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-08-01 (8 checks) | 6fad99327a8f | 2027-11-25 | D, 67.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | 6fad99327a8f | 2027-11-25 | D, 67.4 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | 6fad99327a8f | 2027-11-25 | D, 67.4 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
7 findings, ordered by severity.
Show every finding
- Error1 instance
feed_info.txt says this feed ends on 2026-10-20. Your service calendar runs to 2027-12-31.
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 2027-12-31, 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)
- 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
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 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)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
How we measured this
Checked for changes 18 hours ago; last changed 12 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.
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.5, validator 8.0.1.
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 32 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 32 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 245 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. Service data expired 32 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 32 days ago.
- 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.
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.
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.
- Correctness 91 / 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 78 / 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 Florida portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Florida
Other scorecards in Florida, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/south-florida-regional-transportation-authority-tri-rail/2026-11-21.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-11-21. 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.