Call-prep brief · checked 2026-10-20
Burlington Transit
Grade F · 58.1 / 100
Unchanged since 2026-10-19.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three things to fix
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: Varies.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
2321 of 2321 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 2,321 trips in the feed.
Effort: A default or per-trip field in your export.
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: Usually one export setting.
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- No need reading for this feed was on hand when this was built, so transit need is not known.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 2321 of 2321 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some route lines list the same point twice in a row.
- Next action
- Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Key facts
- Feed URL
- https://opendata.burlington.ca/gtfs-rt/GTFS_Data.zip
- Last checked
- 2026-10-20
- Service window
- 60 days of service data remain. Last service date 2026-12-19.
- Location
- Ontario, Canada
Part of the Canada portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.