Search
  1. Home
  2. United States Feeds
  3. boston-college
  4. Source Data Validation Report

boston-college — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-09T12:13:50Z,
for the dataset file:///shared/boston-college_e3501e26.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 0
  • Blocks: 62
  • Routes: 16
  • Shapes: 16
  • Stops: 110
  • Trips: 570

Specification Compliance report

48 notices reported (26 errors, 22 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 23

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.
93 "TL-4413" "TL-71" 86 "TL-6116" "TL-71" "BC/BO/WKDAY/A1" "20260402"
94 "TL-4414" "TL-71" 87 "TL-6117" "TL-71" "BC/BO/WKDAY/A1" "20260402"
92 "TL-6125" "TL-71" 95 "TL-4415" "TL-71" "BC/BO/WKDAY/A1" "20260402"
92 "TL-6125" "TL-71" 96 "TL-4416" "TL-71" "BC/BO/WKDAY/A1" "20260402"
92 "TL-6125" "TL-71" 81 "TL-4408" "TL-71" "BC/BO/WKDAY/A1" "20260402"
84 "TL-4411" "TL-71" 88 "TL-6118" "TL-71" "BC/BO/WKDAY/A1" "20260402"
85 "TL-4412" "TL-71" 91 "TL-6121" "TL-71" "BC/BO/WKDAY/A1" "20260402"
404 "TL-4754" "TL-88" 405 "TL-4755" "TL-88" "BC/NEW/WKDAY/A4" "20260406"
108 "TL-5441" "TL-73" 109 "TL-5442" "TL-73" "BC/BO/BREAK/LAW/WKDAY/ A3" "20260407"
116 "TL-5445" "TL-73" 112 "TL-4443" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
116 "TL-5445" "TL-73" 117 "TL-5446" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
117 "TL-5446" "TL-73" 113 "TL-4444" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
117 "TL-5446" "TL-73" 120 "TL-6122" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
113 "TL-4444" "TL-73" 120 "TL-6122" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
120 "TL-6122" "TL-73" 114 "TL-4445" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
114 "TL-4445" "TL-73" 121 "TL-6123" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
114 "TL-4445" "TL-73" 118 "TL-5447" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
121 "TL-6123" "TL-73" 118 "TL-5447" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
121 "TL-6123" "TL-73" 115 "TL-4446" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
118 "TL-5447" "TL-73" 115 "TL-4446" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
115 "TL-4446" "TL-73" 122 "TL-6124" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
115 "TL-4446" "TL-73" 119 "TL-5448" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
122 "TL-6124" "TL-73" 119 "TL-5448" "TL-73" "BC/BO/BREAK/LAW/WKDAY/A3" "20260407"
invalid_url ERROR 1

invalid_url

A field contains a malformed URL.

Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"agency.txt" 2 "agency_url" "bc.transloc.com"
stop_time_with_arrival_before_previous_departure_time ERROR 2

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
3061 3060 "TL-4864" "00:05:00" "23:59:00"
2933 2931 "TL-4848" "02:05:00" "02:13:00"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
stop_without_stop_time WARNING 17

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.
2 "TL-43" "St. Thomas More Apartments (2150)"
3 "TL-44" "Evergreen Cemetery"
4 "TL-45" "2000 Commonwealth Ave"
5 "TL-46" "Reservoir MBTA stop"
6 "TL-47" "Chestnut Hill Ave"
7 "TL-48" "Chiswick Road"
8 "TL-49" "Corner of Commonwealth Ave. and Chestnut Hill Ave"
9 "TL-50" "South Street"
10 "TL-51" "Greycliff Hall"
82 "TL-240" "Alumni House (Newton Campus)"
83 "TL-243" "College Road (Football)"
106 "TL-452" "Reservoir T Stop"
107 "TL-453" "Ashby Stop"
108 "TL-454" "South Dorms Stop"
109 "TL-455" "Reservoir T Stop"
110 "TL-457" "College Road (Football)"
111 "TL-458" "College Road (Football)"
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.
79 "TL-6" "TL-4406" 133 "TL-68" "Evergreen Cemetery" [42.339990000001855,-71.16125446316218] 132 "TL-67" "Conte Forum" [42.336050308914395,-71.16717917667403]
unused_shape WARNING 3

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"TL-47" 1345
"TL-20" 10059
"TL-19" 10363