GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T12:43:10Z,
for the dataset file:///shared/duluth-transit_10c36b07.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2026-03-01
Feed End Date:
2026-08-29

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: 264
  • Routes: 17
  • Shapes: 47
  • Stops: 779
  • Trips: 3052

Specification Compliance report

15 notices reported (0 errors, 11 warnings, 4 infos)

Notice Code Severity Total
expired_calendar WARNING 3

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.
2 "382-220.0.1"
3 "382-220.0.2"
4 "382-220.0.3"
stop_too_far_from_shape WARNING 6

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.
41 "382-47831" "382-478719" 870 "382-2615" "Grand Ave & 59 Aw" [46.73786,-92.17049000000002] 105.30719442412891
765 "382-47862" "382-478340" 28390 "382-2126" "Minnesota Ave & 49 St" [46.73214900000001,-92.053789] 108.86206910690036
2867 "382-48095" "382-483769" 104366 "382-1791" "Superior St & Garfield Av" [46.77078618546232,-92.11685533528203] 148.3452923478976
2883 "382-48096" "382-483780" 105962 "382-2224" "Superior & Garfield" [46.7709,-92.11645] 150.7777946235933
2883 "382-48096" "382-483780" 106005 "382-2-7167" "Glenwood St & Woodbury La" [46.836309,-92.055329] 101.66865384925063
1918 "382-48093" "382-488294" 69588 "382-2615" "Grand Ave & 59 Aw" [46.73786,-92.17049000000002] 105.30719442412891
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.
611 "382-47851" "382-477848" 22356 "382-2486" "Boundary Ave @ Kwik Trip" [46.74086100015067,-92.217129] 22355 "382-2092" "Foxtail Ave & Arbutus Dr" [46.74164013463259,-92.21125465276756]
2219 "382-47851" "382-484336" 80378 "382-2486" "Boundary Ave @ Kwik Trip" [46.74086100015067,-92.217129] 80377 "382-2092" "Foxtail Ave & Arbutus Dr" [46.74164013463259,-92.21125465276756]
trip_headsign_matches_intermediate_stop INFO 4

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
611 "382-477848" "Boundary Ave @ Kwik Trip" "382-2486" 20 "382-2486"
611 "382-477848" "Boundary Ave @ Kwik Trip" "382-2500" 28 "382-2486"
2219 "382-484336" "Boundary Ave @ Kwik Trip" "382-2486" 20 "382-2486"
2219 "382-484336" "Boundary Ave @ Kwik Trip" "382-2500" 28 "382-2486"