GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T03:34:13Z,
for the dataset file:///shared/yellowknife-transit_b4d98120.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Passio Technologies
Publisher URL:
https://passiotech.com
Feed Email:
support@passiotech.com
Feed Language:
English
Feed Start Date:
2026-05-03
Feed End Date:
2026-06-03

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: 12
  • Routes: 3
  • Shapes: 19
  • Stops: 93
  • Trips: 156

Specification Compliance report

32 notices reported (25 errors, 7 warnings, 0 infos)

Notice Code Severity Total
start_and_end_range_out_of_order ERROR 25

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. startFieldName (?) The start value's field name. startValue (?) The start value. endFieldName (?) The end value's field name. endValue (?) The end value.
"stop_times.txt" 1126 "arrival_time" "07:35:00" "departure_time" "07:20:00"
"stop_times.txt" 1138 "arrival_time" "08:35:00" "departure_time" "08:20:00"
"stop_times.txt" 1150 "arrival_time" "08:05:00" "departure_time" "07:50:00"
"stop_times.txt" 1162 "arrival_time" "10:05:00" "departure_time" "09:50:00"
"stop_times.txt" 1174 "arrival_time" "11:05:00" "departure_time" "10:50:00"
"stop_times.txt" 1186 "arrival_time" "12:05:00" "departure_time" "11:50:00"
"stop_times.txt" 1198 "arrival_time" "13:05:00" "departure_time" "12:50:00"
"stop_times.txt" 1210 "arrival_time" "14:05:00" "departure_time" "13:50:00"
"stop_times.txt" 1222 "arrival_time" "15:05:00" "departure_time" "14:50:00"
"stop_times.txt" 1234 "arrival_time" "16:05:00" "departure_time" "15:50:00"
"stop_times.txt" 1246 "arrival_time" "17:05:00" "departure_time" "16:50:00"
"stop_times.txt" 1258 "arrival_time" "18:05:00" "departure_time" "17:50:00"
"stop_times.txt" 1270 "arrival_time" "19:05:00" "departure_time" "18:50:00"
"stop_times.txt" 1282 "arrival_time" "10:05:00" "departure_time" "09:50:00"
"stop_times.txt" 1294 "arrival_time" "11:05:00" "departure_time" "10:50:00"
"stop_times.txt" 1306 "arrival_time" "12:05:00" "departure_time" "11:50:00"
"stop_times.txt" 1318 "arrival_time" "13:05:00" "departure_time" "12:50:00"
"stop_times.txt" 1330 "arrival_time" "14:05:00" "departure_time" "13:50:00"
"stop_times.txt" 1342 "arrival_time" "15:05:00" "departure_time" "14:50:00"
"stop_times.txt" 1354 "arrival_time" "17:05:00" "departure_time" "16:50:00"
"stop_times.txt" 1366 "arrival_time" "18:05:00" "departure_time" "17:50:00"
"stop_times.txt" 1378 "arrival_time" "19:05:00" "departure_time" "18:50:00"
"stop_times.txt" 1390 "arrival_time" "16:35:00" "departure_time" "16:20:00"
"stop_times.txt" 1402 "arrival_time" "17:35:00" "departure_time" "17:20:00"
"stop_times.txt" 1414 "arrival_time" "18:35:00" "departure_time" "18:20:00"
equal_shape_distance_same_coordinates WARNING 5

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`.
"71677" 1433 567.07 43 1432 567.07 42
"56285" 1211 2018.9 138 1210 2018.9 137
"56285" 1289 2840.6 216 1288 2840.6 215
"56281" 983 6153.09 390 982 6153.09 389
"56268" 4723 5889.82 239 4722 5889.82 238
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260505" "20260603" "20260604"
route_long_name_contains_short_name WARNING 1

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`.
"6488" 2 "1" "1 YK Connector"