Feed status · checked 2026-08-01
Palm Tran
Based on the feed this agency publishes
Service mode Bus
down 0.4 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 71 minutes ago; last changed 2 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
2688 of 2688 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
4207 of 4207 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
⏱ Often a bulk fix in your scheduling software.worth about +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
- 2688 of 2688 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
- 4207 of 4207 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
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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. 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.
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. 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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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 is in 49 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
- 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.
Score by category
The MobilityData validator flagged 7 kinds of issue across 4437 instances (0 error, 4437 warning, 0 informational).
Service data covers the next 49 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (3, 4, 10, 40, 43, and more).
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.
2524 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Dixie Hwy at 8th St", "Military Trl at Larch Ave", "MIilitary Trl at Johnson Dairy Rd", 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 2688 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 (orange)
- 2 (green)
- 20 (teal)
- 3 (pink)
- 30 (brown)
- 31 (green)
- 33 (purple)
- 4 (red)
- 40 (yellow)
- 41 (purple)
- 43 (teal)
- 44 (brown)
- 46 (pink)
- 47 (brown)
- 60 (brown)
- 61 (brown)
- 62 (purple)
- 63 (blue)
- 64 (teal)
- 70 (gray)
- 73 (red)
- 80 (purple)
- 81 (teal)
- 88 (green)
- 91 (red)
- 92 (orange)
- 94 (purple)
- 95 (red)
| Route | Type | Line color |
|---|---|---|
| 1 US-1 | Bus | blue |
| 10 Jupiter | Bus | orange |
| 2 Congress Ave | Bus | green |
| 20 North Congress/Executive Center Dr | Bus | teal |
| 3 Military Trl | Bus | pink |
| 30 Blue Heron Blvd | Bus | brown |
| 31 45th St/Tamarind Ave | Bus | green |
| 33 Australian Ave/Palm Beach Lakes | Bus | purple |
| 4 Haverhill Rd/Lawrence Rd | Bus | red |
| 40 Wellington - Belle Glade | Bus | yellow |
| 41 Palm Beach | Bus | purple |
| 43 Okeechobee Blvd | Bus | teal |
| 44 Belvedere Rd | Bus | brown |
| 46 Forest Hill Blvd | Bus | pink |
| 47 South Bay - Belle Glade - Pahokee | Bus | brown |
| 60 Purdy Ln/Summit Blvd/Lake Ave | Bus | brown |
| 61 Cresthaven/10th Ave N | Bus | brown |
| 62 Lake Worth Rd | Bus | purple |
| 63 Lantana Rd/Jog Rd | Bus | blue |
| 64 Melaleuca Ln/6th Ave S | Bus | teal |
| 70 Seacrest Blvd | Bus | gray |
| 73 Boynton Beach Blvd | Bus | red |
| 80 Lake Ida Rd/SW 4th Ave | Bus | purple |
| 81 Atlantic Ave | Bus | teal |
| 88 Linton Blvd | Bus | green |
| 91 Glades Rd | Bus | red |
| 92 Palmetto Park Rd | Bus | orange |
| 94 FAU/Boca Tri-Rail | Bus | purple |
| 95 Port St. Lucie Express | Bus | red |
List every stop
- Dixie Hwy at 8th St
- Military Trl at Larch Ave
- MIilitary Trl at Johnson Dairy Rd
- Military Trl at Burns Rd
- Military Trl at Lilac St
- Military Trl at Holly Dr
- Military Trl at Gardenia Dr
- Military Trl at Brady Ln
- Military Trl at Arbor Way
- Military Trl at Northlake Blvd
- Military Trl at Square Lake Dr
- Military Trl at Investment Ln
- Military Trl at Lillian Ave
- Military Trl at Woodbine Trl
- Military Trl at Woodbine Trl
- Military Trl at VA Medical Center
- VA Medical Center
- Military Trl at Bee Line Hwy
- Military Trl at South Ballpark
- Military Trl at Dyer Blvd
- Military Trl at Old Beacon Way
- Military Trl at Canterbury Dr N
- Military Trl at Canterbury Dr S
- Military Trl at 45th St
- Military Trl at Shiloh Dr
- Military Trl at Palmbrooke Cir
- Military Trl at Appaloosa St
- Military Trl at Willow Pond Rd
- Military Trl at Roebuck Rd
- Military Trl at Lakeside Green Blvd
- Military Trl at Green Pine Blvd
- Quadrille Blvd at 4th St
- Military Trl at Oxbridge Academy
- Military Trl at Community Dr
- Military Trl at Upthegrove Ln
- Military Trl at Steele St
- Military Trl at Hibiscus St
- Military Trl at Okeechobee Blvd
- Military Trl at Elmhurst Rd
- Military Trl at Cherry Rd
- Quadrille Blvd at Clematis St
- Military Trl at Cole St
- Military Trl at Durham St
- Military Trl at Golf St
- Military Trl at Wallis Rd
- Military Trl at Sunset Ln
- Military Trl at Gun Club Rd
- Military Trl at Sunny Ln
- Military Trl at Gardenette Rd
- Military Trl at Summit Blvd
- Military Trl at Kelmar Dr
- Quadrille Blvd at Fern St
- Military Trl at Sutton Ter
- Military Trl at Forest Hill Blvd
- Military Trl at Barbridge Rd
- Military Trl at Purdy Ln
- Military Trl at Evans Ln
- Military Trl at Cresthaven Blvd
- Military Trl at Canal 10 Rd
- Military Trl at Jean Dr
- Military Trl at 10th Ave N
- Military Trl at Clinton Blvd
- Military Trl at Clemens St
- Military Trl at Boatman Rd
- Military Trl at Bowman St
- Military Trl at Lake Worth Rd (N)
- Military Trl at Melaleuca Ln
- Military Trl at Landar Dr
- Military Trl at Pine Forest Dr
- Military Trl at Holly Lake Dr
- Military Trl at Melaleuca Ln
- Dixie Hwy at Fern St
- Military Trl at Barclay Crescent
- Military Trl at N Country Club Blvd
- Military Trl at Collier Rd
- Military Trl at Morrison Ave
- Military Trl at Blue Pine Cir
- Military Trl at Vespasian Ct
- Military Trl at Walmart Entrance
- Military Trl at Hypoluxo Rd
- Military Trl at Colony View Dr
- Military Trl at Canal Dr
- Dixie Hwy at Hibiscus St
- Military Trl at Old Military Trl
- Military Trl at Le Chalet Blvd
- Military Trl at Windward Passage Dr
- Military Trl at Gateway Blvd
- Military Trl at Tartan Lakes Blvd
- Military Trl at La Paloma Blvd
- Military Trl at Palo Verde Dr
- Military Trl at Cypress Park Wy
- Military Trl at Boynton Beach Blvd
- Military Trl at Boynton Beach Blvd
- Military Trl at Cedar Point Blvd
- Military Trl at Palm Chase Dr
- Military Trl at Brighton Lakes Blvd
- Military Trl at Woolbright Rd
- Military Trl at Indian Hills
- Military Trl at Golf Rd
- DIXIE HWY at ACACIA RD
- MILITARY TRL at ROYAL PALM DR
- MILITARY TRL at FLAVOR-PICT RD
- MILITARY TRL at PINETREE DR
- MILITARY TRL at SUNRISE BLVD
- MILITARY TRL at VIA DELRAY ST
- MILITARY TRL at LAKE IDA RD
- MILITARY TRL at NESTING WY/HIGH PT
- MILITARY TRL at LAKEFRONT BLVD
- MILITARY TRL at ATLANTIC AVE
- MILITARY TRL at LAKE BLVD
- MILITARY TRL at LOWSON BLVD
- MILITARY TRL at LAS VERDES DR
- MILITARY TRL at LINTON BLVD
- MILITARY TRL at COUNTRY LAKE CIR
- MILITARY TRL at MONTEREY LN
- DIXIE HWY at PALM ST
- MILITARY TRL at BOCA DELRAY BLVD
- MILITARY TRL at CHAMPION WAY
- MILITARY TRL at PHEASANT WAY
- MILITARY TRL at MAXWELL DR
- MILITARY TRL at CLINT MOORE RD
- MILITARY TRL at MIZNER CT
- MILITARY TRL at SAN MARCOS N ENT
- MILITARY TRL at SAN MARCOS S ENT
- NW EXEC CTR DR at GLADES RD
- NE 20th St at Federal Hwy
- NE 20TH ST at NE 4TH CT
- NW 20TH ST at FL ATL BLVD
- FAU Boca Raton (Main Admin Bldg)
- NW 20TH ST at DIXIE HWY
- MILITARY TRL at YAMATO RD
- DIXIE HWY at FLAMINGO
- MILITARY TRL at SAN MARCO N ENT
- MILITARY TRL at OFFICE DEPOT
- MILITARY TRL at CLINT MOORE RD
- MILITARY TRL at PHEASANT WAY
- MILITARY TRL at BOCAIRE BLVD
- MILITARY TRL at BOCA RAY PLZ SE ENT
- MILITARY TRL at LINTON BLVD
- MILITARY TRL at LAS VERDES DR
- MILITARY TRL at LOWSON BLVD
- MILITARY TRL at LAKE BLVD
- MILITARY TRL at DELRAY W PLZ SE ENT
- Military Trl at Atlantic Ave
- MILITARY TRL at FOUNTAINS WAY
- MILITARY TRL at LAKE FRONT/BY POST
- DIXIE HWY at UPLAND
- MILITARY TRL at NW 5TH ST
- MILITARY TRL at LAKE IDA RD
- MILITARY TRL at W BEXLEY PARK DR
- MILITARY TRL at PALM RIDGE BLVD
- MILITARY TRL at MODERN DR
- MILITARY TRL at RIDGEWOOD RD E
- MILITARY TRL at COCONUT LN
- MILITARY TRL at ROYAL PALM DR
- MILITARY TRL at PIPERS GLEN BLVD
- MILITARY TRL at GOLF RD
- MILITARY TRL at INDIAN HILLS
- MILITARY TRL at WOOLBRIGHT RD
- MILITARY TRL at BRIGHTON LAKES BLVD
- MILITARY TRL at PALM CHASE DR
- MILITARY TRL at APPLEGATE PLZ SE ENT
- Military Trl at Boynton Beach Blvd
- MILITARY TRL at OLD BOYNTON BCH RD
- DIXIE HWY at ALMERIA RD
- MILITARY TRL at CYPRESS PK WY
- MILITARY TRL at MIRROR LAKES BLVD
- MILITARY TRL at LA PALOMA BLVD
- MILITARY TRL at TARTAN LAKES BLVD
- MILITARY TRL at GATEWAY BLVD
- MILITARY TRL at WINDWARD PASSAGE DR
- MILITARY TRL at WHITE FEATHER TR
- MILITARY TRL at OLD MILITARY TRL
- MILITARY TRL at DOLPHINS DR
- MILITARY TRL at COLONY VIEW RD
- MILITARY TRL at HYPOLUXO RD
- MILITARY TRL at WAL-MART E ENT
- MILITARY TRL at PINESTEAD DR
- MILITARY TRL at TALL PINES RD
- Military Trl at Lantana Rd
- MILITARY TRL at 61ST ST
- MILITARY TRL at N COUNTRY CLUB BLVD
- MILITARY TRL at BARCLAY CRES
- MILITARY TRL at MELALEUCA
- MILITARY TRL at FULLER ST
- DIXIE HWY at BLD 311
- MILITARY TRL at COSTWOLD H
- Military Trl at Lake Worth Rd
- MILITARY TRL at LAKEWOOD
- MILITARY TRL at TODD ST
- MILITARY TRL at CAMBRIDGE
- MILITARY TRL at 10TH AVE N
- MILITARY TRL at DIAMOND RD
- MILITARY TRL at SUSSEX AVE
- MILITARY TRL at CRESTHAVEN BLVD
- DIXIE HWY at AVENIDA HERMOSA
- MILITARY TRL at CYPRESS LN
- MILITARY TRL at PURDY LN
- MILITARY TRL at BEECH DR
- MILITARY TRL at BARBRIDGE RD
- Military Trl at Forest Hill Blvd
- MILITARY TRL at 14TH RD
- MILITARY TRL at PALM AVE
- MILITARY TRL at COCONUT RD
- MILITARY TRL at SUMMIT W ENT POLO G
- MILITARY TRL at VENUS AVE
- DIXIE HWY at EL VEDADO
- MILITARY TRL at SUNNY LN AVE
- MILITARY TRL at GUN CLUB RD
- MILITARY TRL at EOC
- MILITARY TRL at SOUTHERN BLVD/SR-80
- MILITARY TRL at TULAN DR
- MILITARY TRL at MOUNTS BOTAN CTR
- MILITARY TRL at HAZZARD ST
- MILITARY TRL at GROVE LN
- MILITARY TRL at DURHAM ST
- MILITARY TRL at COLE ST
- MILITARY TRL at CHERRY RD
- MILITARY TRL at WESTGATE AVE
- Military Trl at Okeechobee Blvd
- MILITARY TRL at SCHALL WY
- MILITARY TRL at HIBISCUS
- MILITARY TRL at NORTHWOOD UNIV
- MILITARY TRL at BLD2800
- Military Trl at Community Dr
- MILITARY TRL at PEGGY ADAMS ANM RSC
- MILITARY TRL at GREEN PINE
- MILITARY TRL at SHENANDOAH
- MILITARY TRL at ROEBUCK RD
- MILITARY TRL at BEAR LAKES CT
- MILITARY TRL at WADITA KA WY
- MILITARY TRL at CUMBERLAND DR
- MILITARY TRL at SHILOH DR
- MILITARY TRL at BLDG 1466
- MILITARY TRL at CANTERBURY DR
- MILITARY TRL at E HOLLY LN
- MILITARY TRL at PORT W BLVD
- DIXIE HWY at SOUTHERN BLVD
- MILITARY TRL at WESTROADS DR
- MILITARY TRL at CASCADES LAKES BLVD
- MILITARY TRL at UP THE GROVE LN
- MILITARY TRL at VA HOSP
- MILITARY TRL at WOODS EDGE
- MILITARY TRL at LEO LN
- MILITARY TRL at S FOUR SEASONS ST
- MILITARY TRL at N FOUR SEASON ST
- MILITARY TRL at INVESTMENT LN
- MILITARY TRL at E GARDEN OAKS CIR
- MILITARY TRL at MARY CIR
- MILITARY TRL at GARDENS PK PLZ
- and 2438 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 | 67.7 | first check |
| 2026-07-30 | 63.0 | down 4.7 |
| 2026-07-31 | 62.6 | down 0.4 |
| 2026-08-01 | 62.2 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- 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.
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-08-01 the grade held, though the score fell from 68 to 62. As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-30 Score fell 5 points, freshness fell 8 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning4207 instances
4207 of 4207 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2688 instances
2688 of 2688 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)
- Warning2398 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1972 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning39 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning17 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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
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 · 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 49 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 4207 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 49 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 49 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 58 / 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 82 / 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.
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/palm-tran/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.