GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-01

Humboldt Transit Authority

Grade A · 95.5 / 100

Unchanged since 2026-07-31.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality no change

Top three things to fix

  1. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

    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.

    Effort: Usually an export-tool fix, not hand editing.

  2. Re-generate shape_dist_traveled on export so stop and shape distances use the same units.

    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.

    Effort: Usually an export-tool fix, not hand editing.

  3. Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.

    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'.

    Effort: One field per flagged route.

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
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

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 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.

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL
https://data.trilliumtransit.com/gtfs/humboldtcounty-ca-us/humboldtcounty-ca-us.zip
Last checked
2026-08-01
Service window
152 days of service data remain. Last service date 2026-12-31.
Feed version
UTC: 05-Feb-2026 23:45
Location
California

Part of the California portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.