Feed status · checked 2026-08-01
City of Miami Beach
Based on the feed this agency publishes
Service mode Bus + Ferry
unchanged since 2026-07-31
Catalogued in Florida.
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 3 hours ago; last changed 41 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
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
232 of 232 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
300 of 300 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
300 of 300 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 232 of 232 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 300 of 300 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- 300 of 300 trips lack rider-facing destination or direction text.
- Next action
- Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
- 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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 153 days.
- 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
- 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.
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 · 32 trips
- Terminal structure
- 2 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
- Unknown: none of the 2 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 32 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 32 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 32 ferry trips publish cars_allowed.
- Fares
- Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 110 instances (0 error, 66 warning, 44 informational).
Service data covers the next 153 days.
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 not published.
0% of stops state accessibility (0% 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 (Collins Express, North Beach Loop).
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.
65 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("17th Street and Pennsylvania Ave", "6th Street and Lenox Ave", "Washington Avenue and 1st Street", 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.
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 232 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.
- North Beach Loop (teal)
- Middle Beach Loop (yellow)
- Collins Express (orange)
- A (purple)
- B (purple)
- Water Taxi (teal)
| Route | Type | Line color |
|---|---|---|
| North Beach Loop | Bus | teal |
| Middle Beach Loop | Bus | yellow |
| Collins Express | Bus | orange |
| A South Beach Loop | Bus | purple |
| B South Beach Loop | Bus | purple |
| Water Taxi | Ferry | teal |
List every stop
- 17th Street and Pennsylvania Ave
- Washington Avenue and 17th Street
- Washington Avenue and Lincoln Road
- Washington Avenue and 15th Street
- Washington Avenue and 13th Street
- Washington Avenue and 12th Street
- Alton Road and 10th Street
- Alton Road and 8th Street
- 6th Street and Lenox Ave
- Alton Road and 4th Street
- Alton Road and 2nd Street
- South Pointe Drive and Washington Avenue
- Washington Avenue and 1st Street
- Washington Avenue and 2nd Street
- Washington Avenue and 4th Street
- Washington Avenue and 5th Street
- Washington Avenue and 9th Street
- Alton Road and 11th Street
- Alton Road and 13th Street
- Alton Road and 14th Street
- Alton Road and 15th Street
- 16th Street and Lenox Avenue
- 16th Street and Michigan Avenue
- 16th Street and Jefferson Avenue
- Meridian Avenue and Lincoln Road
- 17th Street and Meridian Avenue
- Meridian Avenue and Lincoln Road
- 16th Street and Jefferson Avenue
- 16th Street and Michigan Avenue
- Alton Road and 15th Street
- Alton Road and 14th Street
- Alton Road and 13th Street
- Washington Avenue and 9th Street
- Washington Ave and 7th Street
- Washington Avenue and 5th Street
- Washington Avenue and 4th Street
- Washington Avenue and 2nd Street
- Washington Avenue and 1st Street
- South Pointe Drive and Washington Avenue
- Alton Road and 2nd Street
- Alton Road and 4th Street
- Alton Road and 6th Street
- Alton Road and 8th Street
- Alton Road and 10th Street
- Washington Avenue and 11th Street
- Washington Avenue and 13th Street
- Washington Avenue and 15th Street
- Washington Avenue and 16th Street
- Alton Road and 16th Street
- Alton Road and 17 Street
- Alton Road and 19th Street
- West Avenue and 20th Street
- 18th Street and Purdy Avenue
- Venetian Way and East Island Ave
- Purdy Avenue and 18th Street
- 20th Street and Bay Road
- Alton Road and 19th Street
- Alton Road and 17th Street
- Alton Road and Lincoln Road
- Washington Avenue and 17th Street
- Washington Avenue and 18th Street
- Washington Avenue and 20th Street
- 23rd Street and Liberty Avenue
- Washington Avenue and 19th Street
- Washington Avenue and 18th Street
- 17th Street and Convention Center Drive
- 17th Street and Meridian Ave
- Meridian Avenue and 19th Street
- Dade Boulevard and Michigan Avenue
- 19th Street and Alton Road
- Dade Boulevard and Convention Center Drive
- Washington Avenue and 21st Street
- 20th Street and Liberty Avenue
- Collins Avenue and 22nd Street
- Collins Avenue and 23rd Street
- Collins Avenue and 24th Street
- Collins Avenue and 26th Street
- Collins Avenue and 27th Street
- Collins Avenue and 29th Street
- Collins Avenue and 31st Street
- Collins Avenue and 33rd Street
- Collins Avenue and 35th Street
- Collins Avenue and 38th Street
- Collins Avenue and 41st Street
- Collins Avenue and 43rd Street
- Collins Avenue and 44th Street
- Indian Creek Drive and 43rd Street
- Pine Tree Drive and 41st Street
- Sheridan Avenue and 41st Street
- Maurice Gibb Memorial Park
- 41st Street and Sheridan Avenue
- 41st Street and Prairie Avenue
- 41st Street and Meridian Avenue
- Alton Road and 41st Street
- Mt. Sinai Hospital at Main Door
- Mt. Sinai Hospital and Gumenick Building
- 41st Street and Alton Road
- 41st Street and Meridian Avenue
- 41st Street and Prairie Avenue
- Convention Center Dr/18 Street
- 41st Street and Sheridan Avenue
- 41st Street and Pine Tree Drive
- Indian Creek Drive and 41st Street
- Indian Creek Drive and 37th Street
- Indian Creek Drive and 35th Street
- Indian Creek Drive and 33rd Street
- Indian Creek Drive and 31st Street
- Indian Creek Drive and 29th Street
- Indian Creek Drive and 27th Street
- Collins Ave between 10 and 11 St
- Collins Avenue and 24th Street
- Collins Avenue and 23rd Street
- Collins Avenue and 21st Street
- Collins Avenue and 18th Street
- Collins Avenue and 17th Street
- Lincoln Road and Washington Avenue
- Washington Avenue and Lincoln Road
- 17th Street and Washington Avenue
- Collins Ave and 32 St
- 4441 Collins Avenue
- 4525 Collins Avenue
- Collins Ave and 46 St
- 4833 Collins Avenue
- 4925 Collins Avenue
- 5005 Collins Avenue
- 5101 Collins Avenue
- 5225 Collins Avenue
- 5313 Collins Avenue
- 5401 Collins Avenue
- Royal Palm Ave between 41 St and 42 St
- 5445 Collins Avenue
- 5555 Collins Avenue
- 5601 Collins Avenue
- 5757 Collins Avenue
- 5875 Collins Avenue
- Collins Avenue and 63rd Street
- 6365 Collins Avenue
- Collins Avenue and 65th Street
- Harding Avenue and 77th Street
- Harding Ave and 75th Street
- NE 38 St and NE 1 Ct
- Indian Creek Drive and 65th Street
- Indian Creek Drive and 63rd Street
- 5800 Collins Avenue
- 5750 Collins Avenue
- 5660 Collins Avenue
- 5500 Collins Avenue
- 5400 Collins Avenue
- 5333 Collins Avenue
- Maurice Gibb Memorial Park Dock
- 5200 Collins Avenue
- 5000 Collins Avenue
- 4900 Collins Avenue
- 4700 Collins Avenue
- 4500 Collins Avenue
- 4441 Collins Avenue
- Collins Avenue and 44th Street
- Lincoln Rd and Washington Avenue
- Collins Avenue and 17th Street
- Venetian Marina & Yacht Club
- 65th Street and Allison Park
- Collins Avenue and 67th Street
- Collins Avenue and 69th Street
- Collins Avenue and 72nd Street
- Collins Avenue and 76th Street
- Collins Avenue and 77th Street
- Collins Avenue and 79th Street
- Collins Avenue and 81st Street
- Collins Avenue and 85th Street
- Collins Avenue and 87th Street
- Harding Avenue and 87th Street
- Harding Avenue and 85th Street
- Harding Avenue and 83rd Street
- Harding Avenue and 81st Street
- 85th Street and Byron Avenue
- 85th Street and Crespi Boulevard
- 85 Street and Crespi Blvd
- Hawthorne Avenue and 84 Street
- Hawthorne Avenue and 81st Street
- Crespi Blvd @ Crespi Park
- 77 Street and Tatum Waterway Dr
- 77 Street and Dickens Avenue
- Dickens Avenue and 75th Street
- 73rd Street and Byron Avenue
- Harding Avenue and 72nd Street
- 71st Street and Byron Avenue
- 71st Street and Bonita Drive
- Normandy Drive and Bay Drive
- Normandy Drive and Rue Versailles Drive
- Normandy Drive and Rue Notre Dame
- Normandy Drive and Rue Bordeaux Drive
- Normandy Drive and Trouville Esplanade
- Normandy Drive and Rue Granville
- 71st Street and Biarritz Drive
- 71st Street and Rue Granville
- 71st Street and Trouville Esplanade
- 71st Street and Rue Bordeaux Drive
- 71st Street and Rue Notre Dame
- 71st Street and Rue Versailles Drive
- 71st Street and Bay Drive
- 71st Street and Indian Creek Drive
- 71st Street and Byron Avenue
- Abbott Avenue and 69th Street
- Abbott Avenue and Indian Creek Drive
- Alton Road and 44 Court
- Alton Road and 47 Street
- Alton Road and 51 Street
- Alton Road and 52 Street
- Alton Road and 54 Street
- Alton Road and 57 Street
- Alton Road and 58 Street
- Alton Road and 60 Street
- 63 Street and Allison Rd
- 77 Street and Collins Avenue
- 77 Street and Abbott Avenue
- 77 Street and Carlyle Avenue
- 77 Street and Tatum Waterway Dr
- Hawthorne Avenue and Crespi Park
- Hawthorne Avenue and 80 Street
- Hawthorne Avenue and 82 Street
- Hawthorne Avenue and 85 Street
- 85 Street and Crespi Blvd
- 85 Street and Harding Avenue
- 77 Street and Abbott Avenue
- 63 Street and Allison Rd
- Alton Road and 62 Street
- Alton Road and 58 Street
- Alton Road and 56 Street
- Alton Road and 52 Street
- Alton Road and 50 Street
- Alton Road and 47 Street
- Alton Road and 44 Street
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 72.0 | first check |
| 2026-07-30 | 72.0 | no change |
| 2026-07-31 | 72.0 | no change |
| 2026-08-01 | 72.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning300 instances
300 of 300 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning300 instances
300 of 300 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning232 instances
232 of 232 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)
- Warning34 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)
- Warning32 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)
- 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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)
- Info8 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 · See MobilityData GTFS Validator rules (opens the validator rules 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 153 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 300 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 is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 153 days.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 34 of 232 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 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 86 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 30 / 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/city-of-miami-beach/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.