Brampton Transit

What changed since the last check

No category changes since the last check.

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   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.

   Effort: Often a bulk fix in your scheduling software.

3. Review the flagged fields and fill in the ones your riders would use.

   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.

   Effort: A field at a time; not urgent.

Ready to send to the agency

Hi Brampton Transit team, Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/brampton-transit/

Copy this note from the full scorecard.

Key facts

Feed URL

https://www.arcgis.com/sharing/rest/content/items/a355aabd5a8c490186bdce559c9c75fb/data

Last checked

2026-07-20

Service window

13 days of service data remain. Last service date 2026-08-02.

Feed version

20260629

Location

Ontario, Canada