GTFS Scorecard
← All agencies

Feed status · checked 2026-09-05

Burlington Transit

Based on the official feed source on file

Service mode Bus

56.2 / 100

First scorecard for this agency

Catalogued in Ontario, Canada.

Covers 56 daysAccessibility gapsRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 2 hours ago; last changed 2 hours ago.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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.

⏱ Varies.worth about +24 points in its category

Fix 02

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

2806 of 2806 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool

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.

⏱ Usually one export setting.worth about +8 points in its category

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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. 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.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 56 days.
Published accessibility data
Accessibility information is stated for 100% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness30.5 / 100

The MobilityData validator flagged 11 kinds of issue across 8460 instances (872 error, 7584 warning, 4 informational).

Freshness93.3 / 100

Service data covers the next 56 days.

Rider experience62.5 / 100

100% of stops state wheelchair accessibility (90% marked accessible, 10% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility62.5 / 100

100% of stops state accessibility (90% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (48, 50, 51, 52).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 26 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("WARWICK DR AT WARWICK CRT", "REXWAY DR AT CUMBERLAND", "REXWAY DR AT CUMBERLAND", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 787 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1 (red)
  • 10 (red)
  • 11 (red)
  • 12 (teal)
  • 2 (red)
  • 25 (red)
  • 3 (red)
  • 4 (teal)
  • 48 (green)
  • 50 (teal)
  • 51 (teal)
  • 52 (teal)
  • 6 (teal)
  • 80 (teal)
  • 81 (teal)
  • 87 (teal)
Routes in Burlington Transit's feed
RouteTypeLine color
1 Plains-FairviewBusred
10 New-MapleBusred
11 Sutton-AltonBusred
12 Upper MiddleBusteal
2 BrantBusred
25 WalkersBusred
3 GuelphBusred
4 CentralBusteal
48 MillcroftBusgreen
50 Burlington SouthBusteal
51 Burlington NortheastBusteal
52 Burlington NorthwestBusteal
6 HeadonBusteal
80 HarvesterBusteal
81 North ServiceBusteal
87 North Service-AldershotBusteal
List every stop
  • MAPLE AT THORPE
  • FAIRVIEW AT DRURY
  • 5255 LAKESHORE
  • LAKESHORE AT WHITE PINES
  • LAKESHORE AT PINELAND
  • LAKESHORE AT KENWOOD
  • 5255 LAKESHORE
  • LAKESHORE AT WHITE PINES
  • LAKESHORE AT COLONIAL
  • APPLEBY AT SPRUCE
  • BERTON AT DARIEN
  • CUMBERLAND AT PROSPECT
  • FAIRVIEW AT BURLINGTON GO
  • FAIRVIEW AT BURLINGTON GO
  • CUMBERLAND AT FAIRVIEW
  • 4330 MAINWAY
  • SUTTON AT JOHN LUCAS
  • SUTTON AT CLAY
  • MAINWAY AT JOHN LUCAS
  • 5500 NORTH SERVICE
  • 1220 BRANT
  • 5515 NORTH SERVICE
  • MAINWAY AT JOHN LUCAS
  • 1375 KERNS
  • KERNS AT VILLAGE GREEN
  • TYANDAGA PARK AT FAIRWAY
  • NEW AT DYNES
  • 2025 UPPER MIDDLE
  • LAKESHORE AT PEARL
  • SUTTON AT UPPER MIDDLE
  • NEW AT DYNES
  • 649 NORTH SERVICE
  • NORTH SERVICE AT KING
  • NORTH SERVICE AT YORKTON
  • 201 NORTH SERVICE
  • NORTH SERVICE AT KERNS
  • NORTH SERVICE AT HUNTLY
  • 201 NORTH SERVICE
  • NORTH SERVICE AT YORKTON
  • NORTH SERVICE AT SKYVIEW
  • PROSPECT AT WESLEY
  • NORTH SERVICE AT HUNTLY
  • LASALLE PARK AT NORTH SHORE
  • GUELPH AT DUNDAS
  • 2340 FAIRVIEW
  • GUELPH AT DUNDAS
  • NORTH SERVICE AT BURLINGTON POWER CENTRE
  • DUNDAS AT APPLEBY
  • DUNDAS AT APPLEBY
  • GUELPH AT THIRD
  • WILSON AT JOHN
  • CATHARINE AT KING WILLIAM
  • PLAINS AT WATERDOWN
  • 2321 FAIRVIEW
  • WALKERS AT FAIRVIEW
  • WALKERS AT FAIRVIEW
  • FAIRVIEW AT BURLINGTON CENTRE
  • FAIRVIEW AT CANADIAN TIRE
  • FAIRVIEW AT CUMBERLAND
  • FAIRVIEW AT CUMBERLAND
  • 1259 BRANT
  • FAIRVIEW AT CANADIAN TIRE
  • FAIRVIEW AT BURLINGTON CENTRE
  • SURREY AT KING
  • 695 SURREY
  • TOWNSEND AT SHADELAND
  • TOWNSEND AT GLENVIEW P.S.
  • TOWNSEND AT LASALLE PARK
  • LASALLE PARK AT TOWNSEND
  • TOWNSEND AT GLENVIEW P.S.
  • TOWNSEND AT SHADELAND
  • LAKESHORE AT SMITH
  • BRANT AT NORTH SERVICE
  • FAIRWOOD AT ALDERSHOT SCHOOL
  • FAIRWOOD AT ALDERSHOT SCHOOL
  • 80 FAIRWOOD
  • 80 FAIRWOOD
  • FAIRWOOD AT NORTH SHORE
  • NORTH SHORE AT FAIRWOOD
  • LASALLE PARK AT NORTH SHORE
  • GUELPH AT CARNCASTLE
  • GUELPH AT COVENTRY
  • MAPLE AT FAIRVIEW
  • WATERDOWN AT PLAINS
  • DUNDAS AT ROTARY
  • DUNDAS AT BERWICK
  • WALKERS AT FLEMISH
  • WALKERS AT HENSHAW
  • WARWICK DR AT WARWICK CRT
  • 1235 FAIRVIEW
  • PROSPECT AT PERRY
  • PROSPECT AT CUMBERLAND
  • SUTTON AT DOWNEY
  • GUELPH AT PROSPECT
  • GUELPH AT PROSPECT
  • PROSPECT AT PERRY
  • BRANT AT MOUNT FOREST
  • PROSPECT AT GUELPH
  • NEW AT CUMBERLAND
  • PROSPECT AT GUELPH
  • LAKESHORE AT SMITH
  • NEW AT CUMBERLAND
  • BRANT AT MOUNT FOREST
  • BRANT AT BLUEFIELDS
  • FAIRVIEW AT GUELPH
  • MOUNT FOREST AT BRANT
  • FAIRVIEW AT GUELPH
  • MOUNT FOREST AT MOUNTAINSIDE
  • LAKESHORE AT STRATHEDEN
  • GUELPH AT FAIRVIEW
  • GUELPH AT FAIRVIEW
  • PROSPECT AT REGENCY
  • PROSPECT AT REGENCY
  • MOUNT FOREST AT TYRRELL
  • NEW AT GUILDWOOD
  • NEW AT WOODVIEW
  • PROSPECT AT DYNES
  • BRANT AT ESTER
  • NEW AT MARTHA
  • PROSPECT AT DYNES
  • REXWAY DR AT CUMBERLAND
  • REXWAY DR AT CUMBERLAND
  • BRANT AT AMHERST HEIGHTS
  • GUELPH AT HARVESTER
  • GUELPH AT HARVESTER
  • CUMBERLAND AT WOODWARD
  • NEW AT HOLTBY
  • HARVESTER AT GUELPH
  • CUMBERLAND AT NORTHGATE
  • BRANT AT TYANDAGA PARK
  • MOUNT FOREST AT ROYAL
  • BRANT AT TYANDAGA PARK
  • PROSPECT AT CENTENNIAL TRAIL
  • MOUNT FOREST AT ROYAL
  • BRANT AT BALDWIN
  • 3027 HARVESTER
  • NEW AT ELWOOD
  • NEW AT ELWOOD
  • PROSPECT AT CENTENNIAL TRAIL
  • 3050 HARVESTER
  • REXWAY DR AT WOODVIEW
  • BRANT AT FAVERSHAM
  • FAIRVIEW AT MAPLE
  • REXWAY DR AT WOODVIEW
  • NORTH SERVICE AT GUELPH
  • HARVESTER AT SOUTH SERVICE
  • NEW AT WALKERS
  • NEW AT WALKERS
  • GUELPH AT NORTH SERVICE
  • REXWAY DR AT REXWAY CRT
  • WALKERS AT NEW
  • 3155 HARVESTER
  • 3155 HARVESTER
  • WALKERS AT NEW
  • REXWAY DR AT THORNWOOD
  • MOUNT FOREST AT FISHER AVE
  • NEW AT LONGMOOR
  • MOUNT FOREST AT FISHER AVE
  • NEW AT LONGMOOR
  • BRANT AT DAWLISH
  • LAKESHORE AT OLD LAKESHORE
  • LAKESHORE AT SENECA
  • BRANT AT HAVENDALE
  • WALKERS AT CENTENNIAL TRAIL
  • WALKERS AT CENTENNIAL TRAIL
  • GUELPH AT MOUNTAINSIDE
  • FAIRVIEW AT WOODVIEW
  • FAIRVIEW AT WOODVIEW
  • GUELPH AT DAVIDSON
  • BRANT AT UPPER MIDDLE
  • REXWAY DR AT WALKERS
  • LAKESHORE AT DELAWARE
  • FISHER AVE AT ST MARY'S
  • FISHER AVE AT ST MARY'S
  • REXWAY DR AT WALKERS
  • LONGMOOR AT STEPHANIE
  • LONGMOOR AT STEPHANIE
  • TEEN TOUR WAY AT DRURY
  • HARVESTER AT CUMBERLAND
  • BRANT AT UPPER MIDDLE
  • 3167 NORTH SERVICE
  • GUELPH AT MAINWAY
  • 2211 BRANT
  • FAIRVIEW AT COMMERCE
  • MAINWAY AT GUELPH
  • 4100 LONGMOOR
  • NEW AT BELVENIA
  • HARVESTER AT CUMBERLAND
  • NEW AT BELVENIA
  • GUELPH AT MAINWAY
  • FISHER AVE AT PARKWAY
  • LAKESHORE AT GREEN
  • MAINWAY AT GUELPH
  • FISHER AVE AT FISHER PL
  • 3455 FAIRVIEW
  • 3332 HARVESTER
  • 3332 HARVESTER
  • 3500 FAIRVIEW
  • BRANT AT COTTONTREE
  • 3100 MAINWAY
  • UPPER MIDDLE AT CAVENDISH
  • UPPER MIDDLE AT MOUNTAIN GROVE
  • LAKESHORE AT GREEN
  • 422 GUELPH
  • BRANT AT BARLOW
  • 3097 MAINWAY
  • LONGMOOR AT CLARE
  • GUELPH AT CENTENNIAL
  • GUELPH AT CENTENNIAL
  • LONGMOOR AT CLARE
  • UPPER MIDDLE AT CAVENDISH
  • UPPER MIDDLE AT MOUNTAIN GROVE
  • 3255 NORTH SERVICE
  • NEW AT LORNE
  • CAVENDISH AT UPPER MIDDLE
  • FISHER AVE AT AUGUSTINE
  • NEW AT SHOREACRES
  • HARVESTER AT HARRINGTON
  • HARVESTER AT HARRINGTON
  • FAIRVIEW AT WALKERS
  • AUGUSTINE AT FISHER AVE
  • CAVENDISH AT PAULINE
  • NEW AT SHOREACRES
  • UPPER MIDDLE AT AUGUSTINE
  • LONGMOOR AT BELVENIA
  • UPPER MIDDLE AT AUGUSTINE
  • 3450 HARVESTER
  • BRANT AT GREENBANK
  • FAIRVIEW AT WALKERS
  • HARVESTER AT SOUTH SERVICE
  • BRANT AT HAZELTON
  • NEW AT BRIDGMAN
  • LONGMOOR AT FLEMISH
  • CAVENDISH AT LONGSHIRE
  • GUELPH AT PALMER
  • MAINWAY AT NORTHSIDE
  • CAVENDISH AT LONGSHIRE
  • GUELPH AT PALMER
  • MAINWAY AT NORTHSIDE
  • 3486 HARVESTER
  • LAKESHORE AT MARKET
  • 3485 HARVESTER
  • NEW AT WILSON
  • LONGMOOR AT AUBURN
  • NEW AT WILSON
  • GUELPH AT ST FRANCES
  • CAVENDISH AT BRANT
  • GUELPH AT ST FRANCES
  • 3375 NORTH SERVICE
  • HARVESTER AT WALKERS
  • and 537 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

14 findings, ordered by severity.

Show every finding
  • Error872 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    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. (Varies.)

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning4826 instances

    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.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2806 instances

    2806 of 2806 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning1923 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning787 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning28 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning18 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Info786 instances

    About 786 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info2 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    Future calendar (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_calendar · See MobilityData GTFS Validator rules

  • Info1 instance

    Future feed (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_feed · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 56 days.
Accessible Not yet
States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 56 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 872 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 30 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 93 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 62 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Burlington Transit GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/burlington-transit/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.