GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T17:29:33Z,
for the dataset file:///shared/point.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. 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: 8
  • Routes: 8
  • Shapes: 7
  • Stops: 330
  • Trips: 151

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 40

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`.
"58352" 283 6427.48 282 282 6427.48 281
"58352" 289 6621.85 288 288 6621.85 287
"58352" 392 8791.96 391 391 8791.96 390
"58352" 416 9103.07 415 415 9103.07 414
"58352" 419 9114.62 418 418 9114.62 417
"58352" 420 9114.62 419 419 9114.62 418
"58352" 421 9114.62 420 420 9114.62 419
"58352" 422 9114.62 421 421 9114.62 420
"58352" 423 9114.62 422 422 9114.62 421
"58352" 424 9114.62 423 423 9114.62 422
"58352" 425 9114.62 424 424 9114.62 423
"58352" 426 9114.62 425 425 9114.62 424
"58352" 427 9114.62 426 426 9114.62 425
"58352" 428 9114.62 427 427 9114.62 426
"58352" 429 9114.62 428 428 9114.62 427
"58352" 433 9128.97 432 432 9128.97 431
"58352" 434 9128.97 433 433 9128.97 432
"58352" 437 9137.2 436 436 9137.2 435
"58352" 438 9137.2 437 437 9137.2 436
"58352" 439 9137.2 438 438 9137.2 437
"58352" 446 9166.25 445 445 9166.25 444
"58352" 463 9320.82 462 462 9320.82 461
"58352" 464 9320.82 463 463 9320.82 462
"58352" 467 9335.81 466 466 9335.81 465
"58352" 468 9335.81 467 467 9335.81 466
"58352" 469 9335.81 468 468 9335.81 467
"33020" 3046 4210.02 119 3045 4210.02 118
"33020" 3049 4280.82 122 3048 4280.82 121
"33020" 3056 4386.87 129 3055 4386.87 128
"33020" 3201 9247.82 274 3200 9247.82 273
"58380" 2888 11006.41 344 2887 11006.41 343
"50884" 785 2662.02 90 784 2662.02 89
"50884" 805 3369.87 110 804 3369.87 109
"50884" 806 3369.87 111 805 3369.87 110
"50884" 1041 12946.79 346 1040 12946.79 345
"50884" 1049 13140.27 354 1048 13140.27 353
"50885" 1556 2711.16 105 1555 2711.16 104
"50885" 1557 2711.16 106 1556 2711.16 105
"50885" 1629 7511.51 178 1628 7511.51 177
"50885" 1630 7511.51 179 1629 7511.51 178
expired_calendar WARNING 2

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 "26125"
4 "33020"
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"
mixed_case_recommended_field WARNING 10

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "2nd & 4th" 10
"stops.txt" "stop_name" "300 2nd" 24
"stops.txt" "stop_name" "4th & 1st WB" 36
"stops.txt" "stop_name" "4th & 2nd" 37
"stops.txt" "stop_name" "4th & 3rd" 38
"stops.txt" "stop_name" "4th & 3rd WB" 39
"stops.txt" "stop_name" "4th & 5th" 40
"stops.txt" "stop_name" "4th LNT" 55
"stops.txt" "stop_name" "UWSP CCC" 300
"stops.txt" "stop_name" "UWSP MCCH" 302
route_long_name_contains_short_name WARNING 6

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`.
"7329" 2 "1" "1 Green Loop"
"3018" 3 "2" "2 Blue Loop"
"5466" 4 "3" "3 Red Loop"
"5496" 5 "4" "4 Yellow Loop"
"3016" 6 "5" "5 UWSP Purple Loop"
"5465" 7 "8" "8 Orange Loop"
stop_without_stop_time WARNING 81

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
4 "83755" "1450 Water"
8 "112472" "1st & Portage"
13 "186673" "2nd & Franklin"
37 "83883" "4th & 2nd"
41 "186618" "4th & Bukolt NB"
42 "83882" "4th & Frederick"
45 "84988" "4th & Isadore WB"
49 "186613" "4th & Pulaski WB"
55 "85446" "4th LNT"
60 "159118" "Academy & Division"
62 "151737" "ADRC SB Water St"
65 "83756" "Arlington & Elk"
69 "83816" "Brilowski & Clems"
70 "83824" "Brilowski & Ellis"
80 "83752" "CAP Services"
81 "89041" "Centerpoint & 3rd"
95 "83749" "Clark & Pearl"
105 "83797" "Division & 4th"
107 "83798" "Division & 6th"
108 "83799" "Division & Maria"
110 "83870" "Division & North Point"
118 "85445" "Dunham's Sports"
130 "83881" "Forest & 4th"
132 "83879" "Forest & 6th"
134 "83880" "Forest & Bukolt"
135 "155177" "Francis & Water"
137 "83873" "Frederick & Johns"
138 "83872" "Frederick & North Point"
140 "85448" "Freemont & Main LNT"
141 "140334" "Fremont & High LNT"
143 "84855" "Fremont & Main LNT"
147 "126631" "Goerke Park"
149 "88697" "HH & Hoover"
150 "140551" "HH & Hoover"
151 "88695" "HH & Olympia"
154 "126632" "Homecoming 2nd Street"
173 "83875" "Johns & 2nd"
174 "83874" "Johns & West"
175 "83832" "Jordan & Wilshire"
176 "112479" "KASH Park"
178 "83719" "Linden & Chestnut"
182 "152512" "Main & Country Club WB"
194 "186670" "Maria & Isadore WB"
196 "186636" "Maria & Minnesota WB"
197 "186638" "Maria & Reserve WB"
200 "88699" "McDill & Feltz WB"
201 "89043" "McDill & Hoover"
202 "83729" "McDill & Locust"
204 "88693" "McDill & School"
205 "105719" "McDill & Verril"
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.
48 "50884" "701879" 1797 "83658" "Downtown Transfer Center" [44.52381542497046,-89.58233348076759] 1796 "83757" "Church & Main" [44.52327566213521,-89.58045300266038]