GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T02:11:11Z,
for the dataset file:///shared/connecticut2_c4916f0b.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-05-03
Feed End Date:
2026-06-03

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: 0
  • Routes: 41
  • Shapes: 36
  • Stops: 223
  • Trips: 782

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 7

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

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 small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"55162" 21379 3627.62 74 21378 3627.62 73 0.008289414533942044
"55162" 21383 3627.65 78 21382 3627.65 77 0.0020616989103038074
"55162" 21384 3627.65 79 21383 3627.65 78 0.0010156295360322007
"55162" 21385 3627.65 80 21384 3627.65 79 5.45430316146835E-4
"55162" 21386 3627.65 81 21385 3627.65 80 2.7271400011232233E-4
"55162" 21387 3627.65 82 21386 3627.65 81 1.660103418052465E-4
"55162" 21389 3627.65 84 21388 3627.65 83 8.300569890854483E-5
equal_shape_distance_same_coordinates WARNING 68

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 68 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`.
"67781.427" 28390 315.01 23 28389 315.01 22
"67781.427" 28759 10863.72 392 28758 10863.72 391
"67781.427" 28854 13014.73 487 28853 13014.73 486
"67781.427" 30666 56251.99 2299 30665 56251.99 2298
"60909" 1288 3827.04 251 1287 3827.04 250
"72453" 27823 10501.05 585 27822 10501.05 584
"55162" 21388 3627.65 83 21387 3627.65 82
"55162" 21390 3627.65 85 21389 3627.65 84
"55162" 21391 3627.65 86 21390 3627.65 85
"55162" 21392 3627.65 87 21391 3627.65 86
"55162" 21393 3627.65 88 21392 3627.65 87
"55162" 21394 3627.65 89 21393 3627.65 88
"40449" 26512 1515.45 58 26511 1515.45 57
"60910" 3836 17071.35 751 3835 17071.35 750
"55166" 22383 1192.86 71 22382 1192.86 70
"55166" 22866 15943.48 554 22865 15943.48 553
"55166" 22867 15943.48 555 22866 15943.48 554
"55166" 22920 16849.04 608 22919 16849.04 607
"55166" 22921 16849.04 609 22920 16849.04 608
"55166" 22922 16849.04 610 22921 16849.04 609
"55166" 22923 16849.04 611 22922 16849.04 610
"55166" 22924 16849.04 612 22923 16849.04 611
"55166" 22925 16849.04 613 22924 16849.04 612
"55166" 22926 16849.04 614 22925 16849.04 613
"55166" 22962 17435.98 650 22961 17435.98 649
"55166" 22964 17447.81 652 22963 17447.81 651
"55166" 23004 18188.21 692 23003 18188.21 691
"55166" 23010 18257.24 698 23009 18257.24 697
"55166" 23011 18257.24 699 23010 18257.24 698
"55166" 23039 18638.2 727 23038 18638.2 726
"60894" 4445 9293.72 348 4444 9293.72 347
"61000" 7998 29250.06 977 7997 29250.06 976
"67781" 10418 8141.69 259 10417 8141.69 258
"67256" 18671 1989.64 86 18670 1989.64 85
"67256" 18763 3610.88 178 18762 3610.88 177
"41287" 5158 35.63 6 5157 35.63 5
"41287" 5160 41.73 8 5159 41.73 7
"41287" 5201 500.17 49 5200 500.17 48
"41287" 5390 3103.89 238 5389 3103.89 237
"41287" 5414 3467.43 262 5413 3467.43 261
"41287" 5433 3664.07 281 5432 3664.07 280
"41287" 5467 4266.82 315 5466 4266.82 314
"41287" 5495 4508.2 343 5494 4508.2 342
"41287" 5545 5019.16 393 5544 5019.16 392
"41287" 5552 5067.48 400 5551 5067.48 399
"41287" 5582 5428.38 430 5581 5428.38 429
"41287" 5703 6593.51 551 5702 6593.51 550
"41287" 5704 6593.51 552 5703 6593.51 551
"41287" 5801 8473.58 649 5800 8473.58 648
"41287" 5803 8486.79 651 5802 8486.79 650
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 "20260505" "20260603" "20260604"
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" "NZTC NE" 139
"routes.txt" "route_long_name" "NEW BLUE LINE" 16
"routes.txt" "route_long_name" "NEW W674 E BLUE 3 CLOSING" 17
route_long_name_contains_short_name WARNING 4

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`.
"60894" 6 "675" "675 Hunting Lodge Depot Combined"
"60908" 7 "676" "676 Hunting Lodge Summer/Breaks"
"40450" 18 "Orange" "Orange Line"
"40449" 32 "Yellow" "Yellow Line"
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.
541 "55167" "769911" 11451 "18897" "Bookstore" [41.806414209,-72.254709679] 220.49753608881164
538 "55173" "769976" 11353 "18897" "Bookstore" [41.8061707,-72.2543109] 179.129896980116
stops_match_shape_out_of_order WARNING 5

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.
258 "67781.427" "1002125" 6627 "179436" "Pistol Pete's Bar and Grill" [41.51915612347036,-72.05650488366848] 6626 "84939" "Norwich Transportation Center" [41.5243876025768,-72.0820742010746]
649 "72453" "1104010" 12790 "18919" "Fieldhouse" [41.80643103543284,-72.25472390974636] 12789 "18921" "Foundation" [41.80819420294709,-72.25777776759253]
128 "41287" "690987" 3358 "21000" "Lot K" [41.8188093045672,-72.26435550879526] 3357 "18904" "Central Warehouse (NB)" [41.81193495221763,-72.2609941268438]
129 "41287" "690988" 3366 "18958" "Transportation/Parking Services" [41.811309627645564,-72.26197049647293] 3365 "18955" "Tennis Courts" [41.814184781847,-72.26456152823215]
542 "55177" "771110" 11476 "18946" "Northwood Apartments" [41.804063,-72.271281] 11475 "84954" "S. Frontage at Ash (EB)" [41.72943596587898,-72.21067345435505]