Feed status · checked 2026-08-01
Humboldt Transit Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
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 1 days ago; last changed 38 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
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.worth about +6 points in its category
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.worth about +6 points in its category
Check the flagged trips in your scheduling software; remove them or restore their missing stops.Likely your export tool
Some trips serve fewer than two stops. A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
⏱ Worth a vendor question if it appears often.worth about +4 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
- On some trips the stop distances run a little past the end of the route line.
- Next action
- Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
- 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 stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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 trips serve fewer than two stops.
- Next action
- Check the flagged trips in your scheduling software; remove them or restore their missing 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
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.
Re-generate shape_dist_traveled on export so stop and shape distances use the same units. · 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. Self-check a feed before you publish.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · 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. Self-check a feed before you publish.
Check the flagged trips in your scheduling software; remove them or restore their missing stops.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 152 days.
- Published accessibility data
- Accessibility information is stated for 99.7% of stops and 100% 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 6 kinds of issue across 40 instances (0 error, 34 warning, 6 informational).
Service data covers the next 152 days.
100% of stops state wheelchair accessibility (88% marked accessible, 12% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (88% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (E Grn, E Prpl, E Red, A Red).
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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 339 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.
- A G&G (green)
- A Gold (yellow)
- A Orng (orange)
- A Red (red)
- DAR (teal)
- E Gold (yellow)
- E Grn (green)
- E Prpl (purple)
- E Red (red)
- E Rnbw (pink)
- FLEX (teal)
- NSE101 (green)
- NSE299 (orange)
- RTS (green)
- SHI (pink)
| Route | Type | Line color |
|---|---|---|
| A G&G Arcata Green & Gold Loop | Bus | green |
| A Gold Arcata Gold Loop | Bus | yellow |
| A Orng Arcata Orange Loop | Bus | orange |
| A Red Arcata Red Loop | Bus | red |
| DAR Dial-A-Ride | Bus | teal |
| E Gold Eureka Gold Loop | Bus | yellow |
| E Grn Eureka Green Loop | Bus | green |
| E Prpl Eureka Purple Loop | Bus | purple |
| E Red Eureka Red Loop | Bus | red |
| E Rnbw Eureka Rainbow Loop | Bus | pink |
| FLEX Ride Humboldt Flex | Bus | teal |
| HHM HHM Express | Bus | purple (no shape in feed) |
| NSE101 North State Express 101 | Bus | green |
| NSE299 North State Express 299 | Bus | orange |
| RTS Redwood Transit System | Bus | green |
| SHI Southern Humboldt Line | Bus | pink |
List every stop
- HTA Yard
- Alamar Way (CCC)
- Myers Flat
- Weott Off Ramp - SB Stop
- Redwood Dr & Maple Ln - Garberville SB Stop
- Ave of Giants - SB Stop (Phillipsville Post Office)
- Ave of Giants - NB Stop (Phillipsville Fire Department)
- Ave of Giants & School Rd - Miranda NB Stop (Sips Coffee)
- Redwood Dr & Melville Rd - Garberville NB Stop
- Rohnerville Rd & Guliiksen Dr - NB Stop (OpenDoor)
- Rohnerville Rd & Guliiksen Dr - SB Stop (OpenDoor)
- Wildwood Ave & Davis St - NB Stop (Rio Dell City Hall)
- Main St & Mill St (Hoby's Market)
- Rigby Ave & Davis St - SB Stop
- Center St & Rigby Ave - SB Stop
- School St & Rainbow Ln (Campton Heights Market)
- Rohnerville Rd & School St
- Redwood Way & St Joseph Dr - SB Stop (Redwood Memorial)
- Fortuna Blvd & Smith Ln - NB Stop
- N St & 11th St - NB Stop
- Palmer Creek Rd & Palmer Blvd - SB Stop
- Fernbridge Dr & Rte 211 - SB Stop
- Loleta Dr & Scenic Dr - NB Stop
- College of the Redwoods
- Davis St Off Ramp
- Davis St Off Ramp
- Broadway St & McCullens Ave - NB Stop
- Bayshore Mall
- 4th St & B St (Co-Op)
- 4th St & H St
- 4th St & L St
- Peninsula Dr - NB Stop (Manila Community Center)
- Cal Poly Humboldt (Library)
- Valley West Blvd (McDonald's)
- Central Ave & Bella Vista Rd - NB Stop
- Central Ave & School Rd - NB Stop
- Central Ave & Gwin Rd - NB Stop (McK Shops)
- McKinleyville Ave & Murray Rd - NB Stop (High School)
- Murray Rd & Central Ave - NB Stop
- Arcata/Eureka Airport
- Central Ave - NB Stop (Clam Beach Tavern)
- Riverwalk Dr (Fortuna Overlook)
- H St & 16th St (Arcata High)
- 5th St & D St
- 5th St & H St
- 5th St & K St
- 5th St & O St
- 5th St & U St
- School St & Ronald Ave
- 6th Ave & Spring Ln - NB Stop (Westhaven Fire Dept)
- Main St & View Ave - Trinidad SB Stop
- Hwy 96 & Hwy 299 - Willow Creek
- Kenwood Rd & Kenmar Rd
- Railroad Dr & Central Ave - NB Stop
- G St & 5th St
- H St & 6th St
- Kenwood Rd & Brandi Ln
- S Broadway St & Humboldt Hill Rd - NB Stop (Spruce Point)
- Arcata Transit Center
- S St & Trinity St (Zane Middle School)
- West Ave & 17th St
- West Ave & 13th St
- Walnut Dr & Redwood St
- Walnut Dr & Fern St
- Walnut Dr & Cypress St
- W St & Chester St
- Vance Ave & Herrick Ave
- Rohnerville Rd & Clifton Way
- Summer St & W Wabash Ave
- Summer St & W Clark St
- Summer St & W 7th St
- Summer St & W 15th St
- Dolbeer St & St Joseph Ln (Hospital)
- Tydd St & West Ave (Silvercrest)
- Sequoia Park - Eureka
- S St & Carson St
- Park St & Nedra Ave
- Park St & Myrtle Ave
- Nedra Ave & 18th St
- Myrtle Ave & Hubbard Ln (Myrtle Ave. Market)
- Myrtle Ave & Park St (Myrtletown Shops)
- Myrtle Ave & Sunny Ave
- Myrtle Ave & Hall Ave
- Myrtle Ave & Glenwood St
- Myrtle Ave & Dean St
- Campton Rd - Moose Lodge
- Little Fairfield St & Sydni Ct
- Little Fairfield St & Allard Ave
- Park St & Terrace Way (Lafayette School)
- Koster St & Washington St
- I St & Huntoon St
- I St & Del Norte St
- I St & 15th St
- I St & 12th St
- Holly St & Walnut Dr
- Hodgson St & T St
- Hodgson St & Q St
- Hodgson St & J St
- Herrick Ave & Elk River Rd
- W Henderson St & Summer St
- W Henderson St & Spring St
- Henderson St & Lowell St
- Henderson St & Central Ave
- Henderson St & A St
- Harrison St & Harris St
- Harrison Ave & 18th St
- Harrison St & Erie St
- Harris St & U St
- W Harris St & Summer St
- Harris St & Q St
- Harris St & P St
- Harris St & Lowell St
- Harris St & K St
- W Harris St & Elizabeth St
- Harris St (Redwood Acres)
- H St & Russ St
- H St & Oak St
- H St & Manzanita Ave
- H St & Huntoon St
- H St & 9th St
- H St & Del Norte St
- H St & 15th St
- H St & 12th St
- General Hospital Campus - West Side
- Bayshore Way (Forest Service)
- F St & Harris St
- Excelsior Rd & Holly St
- Excelsior Rd & Campton Rd
- Eureka St & Leonard Dr
- E St & Huntoon St
- E St & Dollison St
- E St & Del Norte St
- E St & 12th St
- E St & 9th St
- E St & 15th St
- Short St & W 15th St (Costco)
- Campton Rd & Leslie Rd
- Campton Rd & Herron Rd
- California St & Simpson St
- California St & Long St
- California St & W Dollison St
- California St & 7th St
- California St & Buhne St
- California St & 15th St
- Myrtle Ave & West Ave (Burre Center)
- Buhne St & S St
- Buhne St & N St
- Buhne St & J St
- Buhne St & Harrison Ave
- Buhne St & F St
- Bingen Ave & Lewis Ave
- Alpha St & Myers Ave
- Fortuna Blvd & Strongs Creek Dr
- 7th St & C St
- 6th St & O St
- 6th St & J St
- 6th St & C St
- 6th St & G St
- 3rd St & V St
- 3rd St & T St
- 2nd St & Y St (Target)
- 2nd St & V St
- 18th St & Myrtle Ave
- H St & 3rd St
- 2nd St & L St
- 11th St & Q St - NW Corner
- Alliance Rd & Hilfiker Dr
- Spear Ave & Alliance Rd - NW Corner
- F St & 8th St (Arcata City Hall)
- Union St & Dr M L King Jr Pkwy (Apts)
- Arcata Community Center
- Giuntoli Ln & Airstream Ave (Town & Country)
- Crescent Way & Old Arcata Blvd
- Union St & Dr M L King Jr Pkwy (School)
- G St & 13th St
- G St & 18th St
- Janes Rd & 11th St (Market)
- H St & 14th St
- H St & 18th St
- H St & 9th St (Arcata Plaza)
- Janes Rd & Edith Dr - W Side (Hospital)
- LK Wood Blvd & Redwood Ave
- Janes Rd & Palomino Ln (Lazy J)
- Janes Rd & Palomino Ln (Gardens)
- Foster Ave & Alliance Rd - N Side
- F St & 6th St (Uniontown Shops)
- Valley East Blvd (Little Learner's)
- Valley East Blvd (South)
- Alliance Rd & Stromberg Ave - E Side
- Zehndner Ave & S St
- Q St & Zehndner Ave
- Fernbridge Dr & Eel River Dr - NB Stop
- Eel River Dr & Fernbridge Dr - SB Stop
- Fortuna Blvd & Main St - SB Stop (Ray's)
- Broadway St & W Cedar St (Cinema)
- Redwood Way - NB Stop (Redwood Village)
- Fields Landing Dr & Central Ave - SB Stop
- King Salmon Offramp & King Salmon Ave - SB Stop
- Westhaven Offramp & Westhaven Dr
- Scenic Dr & Moonstone Beach Rd
- S Broadway St & King Salmon Ave - NB Stop
- Peninsula Dr & Taylor Ct - NB Stop
- Fields Landing Offramp & Orchard Ave - NB Stop
- Peninsula Dr & Tide Rd - SB Stop
- Railroad Dr & McKinleyville Ave - NB Stop
- McKinleyville Ave & Railroad Dr - SB Stop
- McKinleyville Ave & Belnor Rd (Church of the Rock)
- Myrtle Ave & 18th St
- S St & Wood St
- 3rd St & H St
- McKinleyville Ave & Adkins Rd
- Murray Ave & Blue Bird Ln (aka Strating Ln or Little Pond St)
- 14th St & Union St
- 14th St & B St - North Side
- Greenwood Ave (Blue Lake City Hall)
- LK Wood Blvd & California Ave
- LK Wood Blvd & Ridge Rd
- LK Wood Blvd & Diamond Dr
- Camp Curtis
- G St & 16th St (Arcata High)
- Buttermilk Ln & Bayside Rd
- Alliance Rd & 27th St
- Spear Ave & Alliance Rd - NE Corner
- Alliance Rd & Stromberg Ave - W Side
- Central Ave & Norton Rd - NB Stop (Golf Course)
- W Del Norte St & California St
- 11th St & H St
- 11th St & K St - NW Corner
- 11th St & Q St - SE Corner
- Foster Ave & Alliance Rd - S Side
- 4th St & Y St (Target)
- Peninsula Dr - SB Stop (Manila Community Center)
- Wildwood Ave & Davis St - SB Stop (Rio Dell City Hall)
- Central Ave & Norton Rd - SB Stop (Golf Course)
- H St & 4th St
- I St & 8th St
- 4th St & U St
- 4th St & O St
- Central Ave & Grange Rd - SB Stop
- Fortuna Park & Ride - NB Stop
- School St & Rohnerville Rd
- Airport Rd & Halfway Ave - East Side
- Main St & View Ave - Trinidad NB Stop
- Utah St & South Ave
- Utah St & Allard Ave
- Central Ave (Veterans Clinic)
- California St & Del Norte St - Senior Center
- Benbow KOA
- Ave of Giants & Maple Hills Rd - NB Stop
- Redwood Dr & Conger St (Humboldt House Inn)
- and 89 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 90.7 | first check |
| 2026-07-30 | 90.7 | no change |
| 2026-07-31 | 90.7 | no change |
| 2026-08-01 | 90.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady 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.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning22 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
8 of 458 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)
- Warning7 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)
- Warning4 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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
1 of 339 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info5 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
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 152 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 458 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 4 of 458 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (6 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 458 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 79 / 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 100 / 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/humboldt-transit-authority-3032/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.