Call-prep brief · checked 2026-08-01

High Desert Point

Grade F · 31.3 / 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

Top three things to fix

Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.
Neither feed_info.txt nor the calendars state when service ends. Nobody can tell when this feed will go stale.
Effort: Likely a one-time export setting.
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing calendar and calendar date files (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.

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: Neither feed_info.txt nor the calendars state when service ends.
Next action: Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in 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

Agency: High Desert Point
Finding: scorecard_no_expiry_date
Feed evidence: Neither feed_info.txt nor the calendars state when service ends.
Why it matters: Nobody can tell when this feed will go stale.
Requested change: Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in 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.
Evidence: https://gtfsscorecard.org/agency/high-desert-point/?finding=scorecard_no_expiry_date#finding-handoff

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 2 validator errors to resolve. No service end date could be read, so currency is unknown. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.

Published Ready: Published at a public URL.
Valid Needs attention: 2 validator errors to resolve.
Current Not ready: No service end date could be read, so currency is unknown.
agency_id provided Not ready: agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.

The bar this score answers to

A local transit-data support resource is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS.

Key facts

Feed URL: https://oregon-gtfs.com/gtfs_data/highdesertpoint-or-us/highdesertpoint-or-us.zip
Last checked: 2026-08-01
Service window: Expiry date not stated in the feed.
Location: Oregon

Part of the Oregon 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.