GTFS Schedule Validation Report

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

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: 26
  • Routes: 20
  • Shapes: 46
  • Stops: 25
  • Trips: 294

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 25

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`.
"48686.115" 8906 2059.7 169 8905 2059.7 168
"48686.115" 8970 2842.72 233 8969 2842.72 232
"48686.115" 8971 2842.72 234 8970 2842.72 233
"48686.115" 9069 3758.84 332 9068 3758.84 331
"48688" 1177 3316.07 250 1176 3316.07 249
"48688" 1179 3362.67 252 1178 3362.67 251
"48688" 1298 5543.89 371 1297 5543.89 370
"48169" 3799 4600.58 314 3798 4600.58 313
"48688.429" 11094 3261.87 241 11093 3261.87 240
"48688.429" 11096 3308.47 243 11095 3308.47 242
"48688.429" 11215 5489.68 362 11214 5489.68 361
"48166.86" 8482 247.07 12 8481 247.07 11
"48167" 1442 718.06 42 1441 718.06 41
"48167" 1695 4079.33 295 1694 4079.33 294
"48167" 1696 4079.33 296 1695 4079.33 295
"48167" 1697 4079.33 297 1696 4079.33 296
"48167" 1698 4079.33 298 1697 4079.33 297
"48700.114" 10849 1825.66 130 10848 1825.66 129
"48168" 2611 526.21 34 2610 526.21 33
"48675" 3033 1067.95 61 3032 1067.95 60
"48675" 3290 4636.61 318 3289 4636.61 317
"48675" 3292 4639.93 320 3291 4639.93 319
"48675" 3318 5079.41 346 3317 5079.41 345
"48675" 3402 6310.25 430 3401 6310.25 429
"48167.64" 6110 718.52 37 6109 718.52 36
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" "20260110" "20260111"
mixed_case_recommended_field WARNING 1

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.
"routes.txt" "route_long_name" "1636'er" 2
stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
21 "48686.115" "670311" 237 "5048" "Widener Gate" [42.372147,-71.115678] 131.56840606838284
238 "48169.78" "661313" 2558 "5045" "Lamont Library" [42.372698,-71.116412] 116.92849942663241
stops_match_shape_out_of_order WARNING 3

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.
152 "48166.76" "661306" 1669 "5049" "Quad" [42.381846979478695,-71.12536798248179] 1668 "5050" "Mass and Garden" [42.37525273466314,-71.11941417020961]
175 "48166.86" "670201" 1848 "5049" "Quad" [42.38184641240535,-71.12536825337041] 1847 "5044" "Memorial Hall" [42.376445,-71.114428]
244 "48169.108" "670401" 2587 "5049" "Quad" [42.381806,-71.125333] 2586 "5048" "Widener Gate" [42.372848092478165,-71.11697035449944]