GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T20:52:38Z,
for the dataset file:///shared/lawrencetransit.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:
2025-12-11
Feed End Date:
2026-01-11

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: 76
  • Routes: 20
  • Shapes: 40
  • Stops: 440
  • Trips: 1943

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 23

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`.
"53916" 7272 1964.82 122 7271 1964.82 121
"53916" 7273 1964.82 123 7272 1964.82 122
"53916" 7274 1964.82 124 7273 1964.82 123
"53916" 7275 1964.82 125 7274 1964.82 124
"53916" 7276 1964.82 126 7275 1964.82 125
"53916" 7283 1989.55 133 7282 1989.55 132
"53916" 7284 1989.55 134 7283 1989.55 133
"53916" 7285 1989.55 135 7284 1989.55 134
"53916" 7286 1989.55 136 7285 1989.55 135
"53916" 7287 1989.55 137 7286 1989.55 136
"53916" 7288 1989.55 138 7287 1989.55 137
"53916" 7289 1989.55 139 7288 1989.55 138
"53916" 7291 1994.4 141 7290 1994.4 140
"53916" 7292 1994.4 142 7291 1994.4 141
"53916" 7295 2002.51 145 7294 2002.51 144
"53916" 7302 2025.87 152 7301 2025.87 151
"53916" 7303 2025.87 153 7302 2025.87 152
"53916" 7304 2025.87 154 7303 2025.87 153
"53916" 7305 2025.87 155 7304 2025.87 154
"53916" 7306 2025.87 156 7305 2025.87 155
"53916" 7307 2025.87 157 7306 2025.87 156
"53916" 7308 2025.87 158 7307 2025.87 157
"53900" 1314 70.85 8 1313 70.85 7
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.
4 "53922.142039"
5 "53896.141840"
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 "20251212" "20260111" "20260111"
mixed_case_recommended_field WARNING 3

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" "349 - LCS" 234
"stops.txt" "stop_name" "62 - HINU" 409
"stops.txt" "stop_name" "63 - HINU" 410
stop_without_stop_time WARNING 11

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.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
39 "164594" "134 - N. Iowa @ Riverridge"
56 "164326" "155 - George Williams @ Rock Chalk"
186 "164650" "291 - University @ Crestline"
207 "164510" "318 - Clinton @ Lawrence"
228 "164484" "341 - Clinton @ Lawrence"
252 "164410" "367 - Indiana @ 11th NB"
265 "164289" "379 - Oliver Hall"
337 "164585" "445 - Iowa @ Harvard"
344 "164595" "451 - Iowa @ Riverridge"
352 "164593" "459 - Iowa @ Peterson NB"
354 "164596" "460 - Iowa @ Peterson"