Feed status · checked 2026-09-18
Maui County Transit
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hawaii.
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.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
216 of 216 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
240 of 240 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 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
- 216 of 216 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
- 240 of 240 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
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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 for scorecard_wheelchair_boarding_unknown
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.
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 for scorecard_wheelchair_accessible_unknown
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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide for scorecard_missing_feed_info_dates
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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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.
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 268 instances (0 error, 264 warning, 4 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 6, 35, 5, 1, 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.
169 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Lahainaluna Rd. /Kalena St.(Down) (1243)", "Lahainaluna Rd. /Kalena St.(Up) (1244)", "Keanuhea St./Pahilikoa Pl.", 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 216 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.
- 2 (teal)
- 6 (orange)
- 15 (yellow)
- 40 (teal)
- 23 (yellow)
- 35 (red)
- 5 (orange)
- 10 (purple)
- 1 (teal)
- 8 (gray)
- 39 - Loop (brown)
- 29 (purple)
| Route | Type | Line color |
|---|---|---|
| 2 02 - Wailuku Loop (Reverse) | Bus | teal |
| 6 06 - Kahului Loop (Reverse) | Bus | orange |
| 15 15 - Kihei Villager | Bus | yellow |
| 40 40 - Upcountry Islander | Bus | teal |
| 23 23 - Lahaina Villager | Bus | yellow |
| 35 35 - Haiku Islander | Bus | red |
| 5 05 - Kahului Loop | Bus | orange |
| 10 10 -Kihei Islander | Bus | purple |
| 1 01 - Wailuku Loop | Bus | teal |
| 8 08 - Waihe'e Villager | Bus | gray |
| 39 - Loop 39 - Kula Islander | Bus | brown |
| 29 29 - West Maui Express | Bus | purple |
List every stop
- Lahainaluna Rd. /Kalena St.(Down) (1243)
- Lahainaluna Rd. /Kalena St.(Up) (1244)
- Keanuhea St./Pahilikoa Pl.
- Charley Young Beach (northbound) (1247)
- Charley Young Beach (southbound) (1246)
- L. Honoapi'ilani Rd/ The Gardens at West Maui
- Pi'ikea Ave./Hale O Pi'ikea (across)
- Pi'ikea Ave./Hale O Pi'ikea
- Pu'unene Ave./Kauai Street (southbound)
- Pu'unene Ave./Kauai Street (northbound)
- Hali'imaile Rd./Na Mahoe St.
- W. Papa Ave./S. Lanai St. (across)
- Kanaloa Ave./Keopuolani Regional Park
- Lahainaluna Rd./Kuhua St. (down)
- Kamehameha Ave./Ho'ohana St.
- Haiku Marketplace
- Pauwela Rd./Hana Hwy.
- Makawao Public Library
- Hali'imaile Park and Tennis
- Makawao Ave./Mahola St.
- Wells St./State and County Buildings
- Kahului Airport Pick-Up Zone #3
- Luana Gardens (across)
- W. Papa Ave./La'au St.
- Kanaloa Ave./YMCA
- Kamehameha Ave./La'au St.
- Kamehameha Ave./Moloka'i Akau St.
- Leiali'i Pkwy/Ho'oli St.
- Paia Town/Public Parking (to Kahului)
- S. Papa Ave./Kea St.
- Ainakea Park
- Ainakea Rd./Fleming Rd.
- Lahaina Cannery Mall
- Lipoa St./Liloa Dr.
- Kamaole Beach III (southbound)
- Kamaole Beach III (northbound)
- S. Kihei Rd./Kilohana Dr. (southbound)
- S. Kihei Rd./Kilohana Dr. (northbound)
- S. Kihei Rd./Mana Kai Resort (northbound)
- Wailea Ike Drive
- S. Kihei Rd./Mana Kai Resort (southbound)
- Hale Mahaolu
- Onehe'e Ave./Uhu St.
- Onehe'e Ave./S. Papa Ave.
- S. Papa Ave./Roselani Place (across)
- Imi Kala St./Wailuku Post Office
- Maka'ala Dr./Alihilani St.
- Waena St./L. Main St.
- Maka'ala Dr./Kilihau St.
- L. Honoapi'ilani Rd./Napili Village
- L. Honoapi'ilani Rd./Napili Shores (to Lahaina)
- L. Honoapi'ilani Rd./Napili Kai
- L. Honoapi'ilani Rd./Alaeloa (to Kapalua)
- Napili Plaza
- L. Honoapi'ilani Rd./Napili Shores (to Kapalua)
- L. Honoapi'ilani Rd./Kepola Pl.
- Aukai Pl./Waiehu Heights
- Waiehu Beach Rd./Ka'ae Rd.
- Waiehu Beach Rd./Kuhio Pl.
- Makawao Ave./Alana Pl.
- Makawao Ave./Poalima Pl.
- Makawao Ave./Makani Rd.
- L. Honoapi'ilani Rd./Kahana Manor
- L. Honoapi'ilani Rd./Pi`ina Pl.
- L. Honoapi'ilani Rd./Polynesian Shores (to Kapalua)
- L. Honoapi'ilani Rd./Makani Sands (to Kapalua)
- L. Honoapi'ilani Rd./Sunset Terrace
- Honokowai Shopping Center (to Kapalua)
- Whalers Village
- Lipoa St./S. Kihei Rd.
- Kula Community Center (to Kula)
- Kulamalu Town Center (to Kula)
- Pi'ilani Village Shopping Center
- S. Kihei Rd./Ohukai Rd. (southbound)
- Kamehameha Ave./Kahului Salvation Army
- Kamehameha Ave./Kahului Shopping Center
- L. Honoapi'ilani Rd./Honokowai Beach Park
- L. Honoapi'ilani Rd./Honokowai Villa
- S. Kihei Rd./Uwapo Rd. (southbound)
- S. Kihei Rd./Ohukai Rd. (northbound)
- Ma'alaea Harbor Village
- S. Kihei Rd./Uwapo Rd. (northbound)
- Pueo Dr./Hi'ipali Lp.
- Ahulua St./Pueo Dr.
- Pueo Dr./Kula Hwy.
- Pueo Dr.
- Keanuhea St./Lauie Dr.
- Ka'amana St./Keanuhea St.
- Lauie Dr./Ahulua St.
- Lauie Dr./Kaulia'aha St.
- Maui Lani Parkway/Safeway
- Kula Hwy./Kula Hospital
- Pakaula St./Home Depot
- Wailupe Dr./Waiehu Heights
- Kamole St./Kehalani
- L. Honoapi'ilani Rd./Valley Isle Resort
- L. Honoapi'ilani Rd./Kuleana
- L. Honoapi'ilani Rd./Pohaku Park
- L. Honoapi'ilani Rd./Kahana Sunset
- L. Honoapi'ilani Rd./Alaeloa (to Lahaina)
- L. Honoapi'ilani Rd./Kahana Outrigger
- L. Honoapi'ilani Rd./Omaikai Pl.
- L. Kula Rd./Waokele Pl.
- L. Kula Rd./L. Kimo Dr. (to Kula)
- Mayor Hannibal Tavares Community Center
- L. Honoapi'ilani Rd./Makani Sands (to Lahaina)
- L. Honoapi'ilani Rd./Polynesian Shores (to Lahaina)
- Okolani Dr./Wailea Alanui Dr.
- Lipoa St./Haggai Institute
- Kanaloa Ave./N. Wakea Ave.
- Kamehameha Ave./Maui Mall
- Pakaula St./Wal-Mart
- Dairy Rd./Kele St.
- Maui Lani Parkway/Kaiser
- Kanaloa Ave./Little League Field
- Eha St./Sack N Save
- Eha St./Hookahi St.
- Maka'ala Dr./Hale Mahaolu
- Paia Town/Charley's (to Haiku)
- Maui Memorial Medical Center
- Maui Memorial Medical Center (across)
- Kanaloa Ave./Little League Field (across)
- Wahine Pio Ave./UH Maui College
- Wahine Pio Ave./MACC
- Hana Hwy./Kuau Mart (to Kahului)
- Honokowai Shopping Center (to Lahaina)
- Maka'ala Dr./Hale Mahaolu (across)
- Waikapu (to Lahaina)
- L. Kula Rd./Pulehunui Rd. (to Pukalani)
- Paia Town/Charley's (to Kahului)
- Paia Town/Public Parking (to Haiku)
- S. Kihei Rd./Welakahao Rd. (northbound)
- S. Kihei Rd./Welakahao Rd. (southbound)
- S. Kihei Rd./Keala Pl. (northbound)
- S. Kihei Rd./Keala Pl. (southbound)
- Kamaole Beach I (northbound)
- Kamaole Beach I (southbound)
- Kamaole Shopping Center (northbound)
- Kamaole Shopping Center (southbound)
- L. Kula Rd./Na'alae Rd. (to Pukalani)
- Morihara Store
- Ka Hale A Ke Ola
- Maka'ala Dr./Makamua St.
- High St./State and County Buildings
- Malama I Ke Ola Health Center
- N. Market St./Kahekili Terrace (across)
- N. Market St./Kahekili Terrace
- N. Market St./Pi'ihana Terrace (across)
- N. Market St./Pi'ihana Terrace
- Makawao Ave./Koehana Pl.
- Maka'ala Dr./Kuhio Pl.
- Lahaina Gateway
- Lahainaluna Rd./Kuialua St.
- Liloa St./Hokeo St.
- Ainakea Rd./Kaniau Rd.
- Waikapu (to Kahului)
- Ainakea Rd./Malolo Pl.
- Hana Hwy./Kuau Mart (to Haiku)
- Keka'a Dr./Fairway Shops (across)
- S. Kihei Rd./Kulanihakoi St. (southbound)
- S. Kihei Rd./Kulanihakoi St. (northbound)
- S. Kihei Rd./Kaonoulu St. (southbound)
- S. Kihei Rd./Kaonoulu St. (northbound)
- Pi'ikea Ave./S. Kihei Rd.
- S. Kihei Rd./Waipuilani Rd. (southbound)
- S. Kihei Rd./Waipuilani Rd. (northbound)
- S. Kihei Rd./St. Theresa's Church
- Waiakoa Gymnasium
- Velma McWayne Santos Community Center
- Kanaloa Ave./Lihi St.
- Kanaloa Ave./N. Wakea Ave.
- Maka'ala Dr./Kilihau St.
- Maka'ala Dr./Makamua St. (across)
- W. Papa Ave./S. Lanai St.
- W. Papa Ave./La'au St.
- Hale Mahaolu
- Lahainaluna Rd./Kuhua St. (up)
- Pi'ikea Ave./S. Kihei Rd.
- S. Papa Ave./Roselani Place
- S. Papa Ave./Kea St.
- Onehe'e Ave./S. Papa Ave.
- Onehe'e Ave./Uhu St.
- Kamehameha Ave./La'au St.
- Kamehameha Ave./Moloka'i Akau St.
- Luana Gardens
- L. Kula Rd./Pulehunui Rd. (to Kula)
- L. Kula Rd./Na'alae Rd. (to Kula)
- Kula Community Center (to Pukalani)
- L. Kula Rd./L. Kimo Dr. (to Pukalani)
- L. Kula Rd./Waimele Pl.
- Kulamalu Town Center
- Dairy Rd./Maui Marketplace (across)
- Dairy Rd./Maui Marketplace
- Pueo Dr.
- Kapalua Dr./Kapalua
- Mayor Hannibal Tavares Community Center (to Kahului)
- Ho'okahi St./Eha St. (to Waihe'e)
- L. Waiehu Beach Rd./Pakele Pl.
- Akake St./L. Waiehu Beach Rd.
- Hoauna St./Oceanview Estates
- Kahekili Hwy./Bus Shelter
- Kahekili Hwy./Waiehu Kou
- Richard Pablo Caldito Sr. Park
- Kahekili Hwy./Hoauna St.
- Ho'okahi St./Eha St. (to Kahului)
- Kahekili Hwy./Ho'ola Hou St. (past)
- Kula Hardware (to Kula)
- Kula Hardware (to Pukalani)
- W. Papa Ave./Lono Ave.
- W. Papa Ave./Lono Ave.
- Iolani St./Ehilani St.
- Iolani St./Ehilani St. (to Kahului)
- Pulehu Pl./Hookele St. (across Safeway)
- Maui County Service Center
- Lahaina Civic Center (front)
- Kahului Transit Center
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning240 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)
- Warning240 instances
240 of 240 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)
- Warning216 instances
216 of 216 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)
- Warning16 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)
- Warning6 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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)
- Info3 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
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 240 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. 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 71 / 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 85 / 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 45 / 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/maui-county-transit/2026-09-18.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-09-18. 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.