# GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-09T09:53:45-04:00,
for the dataset file:///C:/OD/Foursquare%20ITP/Projects%20-%20ODOT%20GTFS%20Creation/_clientshared/Phase%203%20Final%20Deliverables/GoBus/GoBus%20-%20Prior%20to%20Expansion/gobus_filtered.zip. No country code was provided.

Use this report alongside our documentation.

## Summary

#### Agencies included

- GoBus
  - website: https://ridegobus.com/
  - phone number: 888-954-6287
  - email: gobus@hapcap.org

#### Feed Info

  Publisher Name:
GoBus
  Publisher URL:
https://ridegobus.com
  Feed Email:
gobus@hapcap.org
  Feed Language:
English
  Feed Start Date:
2026-03-04
  Feed End Date:
2027-03-04
  Service Window:
2025-01-01 to 2026-03-03 (?) 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

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

#### Counts

- Agencies: 1
- Blocks: 0
- Routes: 5
- Shapes: 20
- Stops: 39
- Trips: 20

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

Shapes Feed Information Route Colors Bike Allowed

## Specification Compliance report

### 169 notices reported (0 errors, 169 warnings, 0 infos)

Notice Code | Severity | Total
--- | --- | ---
equal_shape_distance_same_coordinates | WARNING | 3
### equal_shape_distance_same_coordinates Two consecutive points have equal `shape_dist_traveled` and the same lat/lon coordinates in `shapes.txt`. When sorted by `shape.shape_pt_sequence`, the values for `shape_dist_traveled` must increase along a shape. Two consecutive points with equal values for `shape_dist_traveled` and the same coordinates indicate a duplicative shape point. You can see more about this notice here.
shapeId (?) The id of the faulty shape. | csvRowNumber (?) The row number from `shapes.txt`. | shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. | shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. | prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. | prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. | prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
--- | --- | --- | --- | --- | --- | ---
"Green-SB-2" | 41400 | 147799.0 | 1692 | 41399 | 147799.0 | 1691
"Orange-EB-1" | 43957 | 277785.0 | 2556 | 43956 | 277785.0 | 2555
"Blue-SB-AM-1" | 13211 | 370400.0 | 3951 | 13210 | 370400.0 | 3950
expired_calendar | WARNING | 1
### expired_calendar Dataset should not contain date ranges for services that have already expired. This warning takes into account the `calendar_dates.txt` file as well as the `calendar.txt` file. You can see more about this notice here.
csvRowNumber (?) The row of the faulty record. | serviceId (?) The service id of the faulty record.
--- | ---
2 | "Daily"
missing_recommended_field | WARNING | 1
### missing_recommended_field A recommended field is missing. The given field has no value in some input row, even though values are recommended. You can see more about this notice here.
filename (?) The name of the faulty file. | csvRowNumber (?) The row of the faulty record. | fieldName (?) The name of the missing field.
--- | --- | ---
"feed_info.txt" | 2 | "feed_version"
missing_timepoint_value | WARNING | 158
### missing_timepoint_value `stop_times.timepoint` value is missing for a record. When at least one of `stop_times.arrival_time` or `stop_times.departure_time` are provided, `stop_times.timepoint` should be defined You can see more about this notice here. Only the first 50 of 158 affected records are displayed below.
csvRowNumber (?) The row number of the faulty record. | tripId (?) The faulty record's `stop_times.trip_id`. | stopSequence (?) The faulty record's `stop_times.stop_sequence`.
--- | --- | ---
2 | "Pink-1" | 0
3 | "Pink-1" | 1
4 | "Pink-1" | 2
5 | "Pink-1" | 3
6 | "Pink-1" | 4
7 | "Pink-1" | 5
8 | "Pink-2" | 0
9 | "Pink-2" | 1
10 | "Pink-2" | 2
11 | "Pink-2" | 3
12 | "Pink-2" | 4
13 | "Pink-2" | 5
14 | "Pink-3" | 0
15 | "Pink-3" | 1
16 | "Pink-3" | 2
17 | "Pink-3" | 3
18 | "Pink-3" | 4
19 | "Pink-3" | 5
20 | "Pink-3" | 6
21 | "Pink-3" | 7
22 | "Pink-3" | 8
23 | "Pink-3" | 9
24 | "Pink-4" | 0
25 | "Pink-4" | 1
26 | "Pink-4" | 2
27 | "Pink-4" | 3
28 | "Pink-4" | 4
29 | "Pink-4" | 5
30 | "Pink-4" | 6
31 | "Pink-4" | 7
32 | "Pink-4" | 8
33 | "Blue-1" | 0
34 | "Blue-1" | 1
35 | "Blue-1" | 2
36 | "Blue-1" | 3
37 | "Blue-1" | 4
38 | "Blue-1" | 5
39 | "Blue-1" | 6
40 | "Blue-1" | 7
41 | "Blue-2" | 0
42 | "Blue-2" | 1
43 | "Blue-2" | 2
44 | "Blue-2" | 3
45 | "Blue-2" | 4
46 | "Blue-2" | 5
47 | "Blue-2" | 6
48 | "Blue-2" | 7
49 | "Blue-2" | 8
50 | "Blue-3" | 0
51 | "Blue-3" | 1
route_long_name_contains_short_name | WARNING | 5
### route_long_name_contains_short_name Long name should not contain short name for a single route. In routes.txt, `route_long_name` should not contain the value for `route_short_name`, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use `route_long_name` only. Good examples:
route_short_name/route_long_name | Dataset
--- | ---
"N"/"Judah" | Muni San Fransisco
"6"/"ML King Jr Blvd" | Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" | STM Montreal
"1"/"Rangiora/Cashmere" | Metro Christchurch
Bad examples:
route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"
You can see more about this notice here.
routeId (?) The id of the faulty record. | csvRowNumber (?) The row number of the faulty record. | routeShortName (?) The faulty record's `route_short_name`. | routeLongName (?) The faulty record's `route_long_name`.
--- | --- | --- | ---
"Pink" | 2 | "Pink" | "Pink"
"Blue" | 3 | "Blue" | "Blue"
"Lime" | 4 | "Lime" | "Lime"
"Green" | 5 | "Green" | "Green"
"Orange" | 6 | "Orange" | "Orange"
trip_coverage_not_active_for_next7_days | WARNING | 1
### trip_coverage_not_active_for_next7_days Trips data should be valid for at least the next seven days. This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days. You can see more about this notice here.
currentDate (?) Current date (YYYYMMDD format). | serviceWindowStartDate (?) The start date of the majority service window. | serviceWindowEndDate (?) The end date of the majority service window.
--- | --- | ---
"20260409" | "20250101" | "20260303"