GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:32:49Z,
for the dataset file:///shared/north.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-01-21
Feed End Date:
2026-02-21

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: 4
  • Routes: 3
  • Shapes: 4
  • Stops: 74
  • Trips: 96

Specification Compliance report

131 notices reported (24 errors, 107 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 24

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
1930 1929 "359726" "10:39:00" "10:42:00"
1955 1954 "359727" "11:39:00" "11:42:00"
1980 1979 "359728" "12:39:00" "12:42:00"
2005 2004 "359729" "13:39:00" "13:42:00"
1830 1829 "359722" "06:39:00" "06:42:00"
1855 1854 "359723" "07:39:00" "07:42:00"
1880 1879 "359724" "08:39:00" "08:42:00"
1905 1904 "359725" "09:39:00" "09:42:00"
1555 1554 "359410" "08:09:00" "08:12:00"
1580 1579 "359411" "09:09:00" "09:12:00"
2030 2029 "359730" "14:39:00" "14:42:00"
1605 1604 "359412" "10:09:00" "10:12:00"
2055 2054 "359731" "15:39:00" "15:42:00"
1630 1629 "359413" "11:09:00" "11:12:00"
2080 2079 "359732" "16:39:00" "16:42:00"
1530 1529 "359254" "07:09:00" "07:12:00"
1755 1754 "359418" "16:09:00" "16:12:00"
1780 1779 "359419" "17:09:00" "17:12:00"
1655 1654 "359414" "12:09:00" "12:12:00"
2105 2104 "359733" "17:39:00" "17:42:00"
1680 1679 "359415" "13:09:00" "13:12:00"
1705 1704 "359416" "14:09:00" "14:12:00"
1730 1729 "359417" "15:09:00" "15:12:00"
1805 1804 "359420" "18:09:00" "18:12:00"
equal_shape_distance_same_coordinates WARNING 104

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.

Only the first 50 of 104 affected records are displayed below.

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`.
"26969" 1408 13338.05 338 1407 13338.05 337
"26968" 94 2609.45 93 93 2609.45 92
"26968" 126 4020.22 125 125 4020.22 124
"26967" 382 3154.23 81 381 3154.23 80
"26967" 383 3154.23 82 382 3154.23 81
"26967" 498 7880.51 197 497 7880.51 196
"26970" 550 629.43 33 549 629.43 32
"26970" 553 661.02 36 552 661.02 35
"26970" 556 699.93 39 555 699.93 38
"26970" 558 723.08 41 557 723.08 40
"26970" 560 742.93 43 559 742.93 42
"26970" 562 765.25 45 561 765.25 44
"26970" 566 947.17 49 565 947.17 48
"26970" 568 1007.53 51 567 1007.53 50
"26970" 571 1089.41 54 570 1089.41 53
"26970" 573 1128.29 56 572 1128.29 55
"26970" 576 1205.71 59 575 1205.71 58
"26970" 579 1295.69 62 578 1295.69 61
"26970" 580 1295.69 63 579 1295.69 62
"26970" 584 1631.61 67 583 1631.61 66
"26970" 586 1651.93 69 585 1651.93 68
"26970" 589 1669.82 72 588 1669.82 71
"26970" 593 1696.45 76 592 1696.45 75
"26970" 597 1836.05 80 596 1836.05 79
"26970" 599 1853.17 82 598 1853.17 81
"26970" 601 1875.44 84 600 1875.44 83
"26970" 621 2160.92 104 620 2160.92 103
"26970" 622 2160.92 105 621 2160.92 104
"26970" 639 2562.81 122 638 2562.81 121
"26970" 725 5488.95 208 724 5488.95 207
"26970" 740 6149.73 223 739 6149.73 222
"26970" 741 6149.73 224 740 6149.73 223
"26970" 750 6228.26 233 749 6228.26 232
"26970" 751 6228.26 234 750 6228.26 233
"26970" 752 6228.26 235 751 6228.26 234
"26970" 753 6228.26 236 752 6228.26 235
"26970" 759 6255.33 242 758 6255.33 241
"26970" 762 6282.06 245 761 6282.06 244
"26970" 768 6325.31 251 767 6325.31 250
"26970" 771 6342.2 254 770 6342.2 253
"26970" 772 6342.2 255 771 6342.2 254
"26970" 776 6360.37 259 775 6360.37 258
"26970" 777 6360.37 260 776 6360.37 259
"26970" 786 6441.12 269 785 6441.12 268
"26970" 787 6441.12 270 786 6441.12 269
"26970" 806 7272.38 289 805 7272.38 288
"26970" 808 7272.71 291 807 7272.71 290
"26970" 809 7272.71 292 808 7272.71 291
"26970" 812 7316.13 295 811 7316.13 294
"26970" 813 7316.13 296 812 7316.13 295
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 "20260123" "20260221" "20260222"
stops_match_shape_out_of_order WARNING 2

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.
74 "26969" "359254" 1530 "85759" "On Pasewalk at 12th WB" [42.025880000001045,-97.4229418800766] 1529 "85775" "HyVee (West) WB on Pasewalk" [42.02670551336508,-97.44160126972777]
2 "26968" "359341" 12 "120777" "On 13th at Pasewalk NB" [42.02616660000215,-97.4264] 11 "120778" "On 13th at Madison NB" [42.03134850003173,-97.42636]