Rogue Valley Transportation District (RVTD)

What changed since the last check

• Correctness down 3.5
• Freshness down 15.0
• Rider experience down 22.5

Fixed since the last check (1 finding):

• Feed valid beyond total service window (flagged by the MobilityData validator). (feed_valid_beyond_total_service_window)

Top three things to fix

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

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

   Effort: A column in stops.txt; your scheduling software likely has it.

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

   296 of 296 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

3. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

   Effort: Two fields, set once in export settings.

   Agencies here usually clear this within about 1 week (based on 16 observed fixes).

NTD certification readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Needs attention

Service data runs out in 30 days; renew before you certify.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

The bar this score answers to

The state transit-data program is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS.

Key facts

Feed URL

https://gtfs.rvtd.cadavl.com/RVTD/GTFS/GTFS_RVTD.zip

Last checked

2026-07-09

Service window

30 days of service data remain. Last service date 2026-08-08.

State

Oregon