GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-07T13:02:12Z,
for the dataset file:///shared/sandy-or-us-flex_bcc13af8.zip. No country code was provided.

Summary

Agencies included

Mt. Hood Express
- website: http://www.mthoodexpress.com/
- phone number: (503) 668-3466
- email: Not provided
Sandy Area Metro
- website: https://rideclackamas.org/
- phone number: 503-668-3466
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
English: Feed Start Date:
2024-11-01: Feed End Date:
2027-03-31: Service Window:
2024-11-01 to 2027-03-31 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 2
Blocks: 4
Routes: 3
Shapes: 10
Stops: 84
Trips: 176

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Feed Information Fares V1 Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types Continuous Stops

Specification Compliance report

6 notices reported (0 errors, 4 warnings, 2 infos)

Notice Code

Severity

Total

fast_travel_between_consecutive_stops

WARNING

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type	Description	Threshold, km/h
0	Light rail	100
1	Subway	150
2	Rail	500
3	Bus	150
4	Ferry	80
5	Cable tram	30
6	Aerial lift	50
7	Funicular	50
11	Trolleybus	150
12	Monorail	150
-	Unknown	200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
33	"105123-t_12225_b_86911_tn_0"	"105123-1116"	254.65827597047698	12.73291379852385	461	9	"105123-759185"	"Hwy 26 & Kirkwood Dr"	"22:32:00"	462	10	"105123-29673"	"Sandy Transit Center"	"22:34:00"
31	"105123-t_12223_b_86911_tn_0"	"105123-1116"	254.65827597047698	12.73291379852385	433	10	"105123-759185"	"Hwy 26 & Kirkwood Dr"	"23:02:00"	434	11	"105123-29673"	"Sandy Transit Center"	"23:04:00"

fast_travel_between_far_stops

WARNING

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
33	"105123-t_12225_b_86911_tn_0"	"105123-1116"	254.65827597047698	12.73291379852385	461	9	"105123-759185"	"Hwy 26 & Kirkwood Dr"	"22:32:00"	462	10	"105123-29673"	"Sandy Transit Center"	"22:34:00"
31	"105123-t_12223_b_86911_tn_0"	"105123-1116"	254.65827597047698	12.73291379852385	433	10	"105123-759185"	"Hwy 26 & Kirkwood Dr"	"23:02:00"	434	11	"105123-29673"	"Sandy Transit Center"	"23:04:00"

stop_without_zone_id

INFO

stop_without_zone_id

Stop without value for stops.zone_id contained in a route with a zone-dependent fare rule.

If fare_rules.txt is provided, and fare_rules.txt uses at least one column among origin_id, destination_id, and contains_id, then all stops and platforms (location_type = 0) must have stops.zone_id assigned if they are defined in a trip defined in a route defined in a fare rule which also defines at least one of origin_id, destination_id, or contains_id.

You can see more about this notice here.

stopId (?) The faulty record's id.	stopName (?) The faulty record's `stops.stop_name`.	csvRowNumber (?) The row number of the faulty record.
"105123-4259143"	"Clackamas Town Center Transit Center"	71
"105123-4259144"	"Clackamas Town Center Transit Center"	72