GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T18:53:19Z,
for the dataset file:///shared/brockton-area-transit-authority.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Brockton Area Transit Authority (Bat)

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2024-01-01
Feed End Date:
2026-12-31

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: 149
  • Routes: 14
  • Shapes: 28
  • Stops: 795
  • Trips: 1826

Specification Compliance report

19 notices reported (16 errors, 3 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 16

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
633 "103419-974504" "103419-23185.60111" 557 "103419-974527" "103419-14420" "40051" "20240107"
632 "103419-943224" "103419-23185.60111" 556 "103419-943225" "103419-14420" "40055" "20240107"
634 "103419-974505" "103419-23185.60111" 558 "103419-974528" "103419-14420" "40047" "20240107"
1797 "103419-943048" "103419-23185.120935" 1721 "103419-943056" "103419-23185.120935" "38488" "20240106"
653 "103419-974524" "103419-23185.60111" 576 "103419-974546" "103419-14420" "40440" "20240107"
651 "103419-974522" "103419-23185.60111" 574 "103419-974544" "103419-14420" "40431" "20240107"
652 "103419-974523" "103419-23185.60111" 575 "103419-974545" "103419-14420" "40439" "20240107"
654 "103419-974525" "103419-23185.60111" 577 "103419-974547" "103419-14420" "40438" "20240107"
2 "103419-192582" "103419-14447" 72 "103419-615045" "103419-14447" "22180" "20240101"
72 "103419-615045" "103419-14447" 185 "103419-615103" "103419-14447" "22180" "20240101"
197 "103419-615131" "103419-14447" 85 "103419-615076" "103419-14447" "30238" "20240101"
200 "103419-615141" "103419-14447" 86 "103419-615078" "103419-14447" "30238" "20240101"
125 "103419-322698" "103419-23185.120935" 12 "103419-204239" "103419-23185.120935" "22275" "20240106"
196 "103419-615130" "103419-14447" 112 "103419-703242" "103419-14447" "25305" "20240101"
199 "103419-615139" "103419-14447" 88 "103419-615087" "103419-14447" "25305" "20240101"
88 "103419-615087" "103419-14447" 977 "103419-703244" "103419-14447" "25305" "20240101"
stop_too_far_from_shape WARNING 1

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.
1535 "103419-31043" "103419-402818" 64702 "103419-39702" "Battles Farm Dr at Rental Office" [42.09779900000001,-71.028146] 112.59305873859202
stops_match_shape_out_of_order WARNING 2

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.
808 "103419-14485" "103419-193470" 37787 "103419-39302" "Torrey St and Brewster Rd" [42.07312467417653,-71.05030498008088] 37786 "103419-39301" "Torrey St at Bethel Medical" [42.07370155461708,-71.04699102618113]
1279 "103419-58273" "103419-828147" 53055 "103419-38943" "Belair St at Belair Hi Rise Ib" [42.091967167216644,-71.03680307831345] 53054 "103419-38944" "Belair St and Earle St Ib" [42.09323792665749,-71.03881808831643]