point — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T16:58:46Z,
for the dataset file:///shared/point_342e701b.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-06-17
Feed End Date:
2026-07-18

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: 331
  • Trips: 151

Specification Compliance report

105 notices reported (0 errors, 101 warnings, 4 infos)

Notice Code Severity Total
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 "20260619" "20260718" "20260719"
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" 301
"stops.txt" "stop_name" "UWSP MCCH" 303
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" 1820 "83658" "Downtown Transfer Center" [44.52381542497046,-89.58233348076759] 1819 "83757" "Church & Main" [44.52327566213521,-89.58045300266038]
big_gap_in_service INFO 1

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"33020" "2026-03-08" "2026-03-27" 18
service_window_outside_feed_period INFO 3

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"33020" "2026-01-23" "2026-05-17" 145 0
"26125" "2025-01-28" "2025-05-16" 505 0
"31637" "2025-01-01" "2027-12-31" 532 531