GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T21:50:53Z,
for the dataset file:///shared/sandy-or-us_6df3e9ac.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2025-01-01
Feed End Date:
2027-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. feed_info.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 14
  • Routes: 5
  • Shapes: 10
  • Stops: 160
  • Trips: 130

Specification Compliance report

12 notices reported (0 errors, 12 warnings, 0 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 6

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.
126 "102436-1003688" "102436-8169" 186.15834202048435 3.1026390336747394 3768 19 "102436-123339" "Bigfoot RV Park Westbound" "09:49:00" 3769 20 "102436-123335" "Hwy 26 & Veneer Ln" "09:49:00"
125 "102436-1003687" "102436-8169" 186.15834202048435 3.1026390336747394 3745 19 "102436-123339" "Bigfoot RV Park Westbound" "06:49:00" 3746 20 "102436-123335" "Hwy 26 & Veneer Ln" "06:49:00"
127 "102436-1003689" "102436-8169" 186.15834202048435 3.1026390336747394 3791 19 "102436-123339" "Bigfoot RV Park Westbound" "13:19:00" 3792 20 "102436-123335" "Hwy 26 & Veneer Ln" "13:19:00"
128 "102436-1003690" "102436-8169" 186.15834202048435 3.1026390336747394 3814 19 "102436-123339" "Bigfoot RV Park Westbound" "16:09:00" 3815 20 "102436-123335" "Hwy 26 & Veneer Ln" "16:09:00"
130 "102436-1003668" "102436-8169" 186.15834202048435 3.1026390336747394 3860 19 "102436-123339" "Bigfoot RV Park Westbound" "15:19:00" 3861 20 "102436-123335" "Hwy 26 & Veneer Ln" "15:19:00"
131 "102436-1003670" "102436-8169" 186.15834202048435 3.1026390336747394 3883 19 "102436-123339" "Bigfoot RV Park Westbound" "18:29:00" 3884 20 "102436-123335" "Hwy 26 & Veneer Ln" "18:29:00"
fast_travel_between_far_stops WARNING 3

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.
6 "102436-1017306" "102436-8747" 211.9899948910072 10.59949974455036 198 0 "102436-123344" "Sandy Transit Center Hoffman St" "14:15:00" 210 12 "102436-160635" "SE Wally Road & Trailhead" "14:17:00"
128 "102436-1003690" "102436-8169" 152.63019144866263 10.17534609657751 3797 2 "102436-123336" "Industrial Way-Fred Meyer Garden Center" "15:18:00" 3802 7 "102436-123331" "Bigfoot RV Park Eastbound" "15:21:00"
93 "102436-1017246" "102436-3994" 920.4967450605395 15.341612417675659 2847 7 "102436-194739" "Hwy 26 & SE 362nd Dr Westbound" "05:35:00" 2850 10 "102436-123286" "Gresham Transit Center" "05:35:00"
stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
10 "102436-56903" "102436-1003678" 404 "102436-123355" "Fred Meyer" [45.40318037947577,-122.2910426105339] 105.2834415867085
10 "102436-56903" "102436-1003678" 417 "102436-123324" "Cascadia Village Park Southbound" [45.387038000000004,-122.26495200000002] 338.3303819235384
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
37 "102436-68903" "102436-1017323" 1255 "102436-152528" "Hamilton Ridge Playground" [45.39348897569993,-122.27538456403101] 1254 "102436-152525" "Barlow Ridge Park" [45.39050219547213,-122.26672847861]