GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Barrie Transit (Ontario)

Based on the feed this agency publishes

Service mode Bus

72.3 / 100

unchanged since 2026-07-31

Catalogued in Ontario, Canada.

Covers 91 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 81 minutes ago; last changed 30 days ago.

Measured 3 of 4 score categories from the agency's own feed.

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 agency's own URL.

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

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

566 of 566 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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

2295 of 2295 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

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 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
566 of 566 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.

  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. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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 91 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
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

Correctness76.0 / 100

The MobilityData validator flagged 4 kinds of issue across 391 instances (0 error, 391 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 91 days.

Rider experience45.0 / 100

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

Accessibility0 / 100

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

3 accessibility depth signals

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (101, 15A).

    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.

  • 12 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bell Farm at St Vincent", "St. Vincent Street", "St. Vincent Street", and more).

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

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

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.

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

  • 10 (brown)
  • 100 (red)
  • 101 (teal)
  • 11 (yellow)
  • 12A (white)
  • 12B (white)
  • 15A (teal)
  • 15B (black)
  • 2A (green)
  • 2B (green)
  • 400 (teal)
  • 7A (orange)
  • 7B (orange)
  • 8A (black)
  • 8B (black)
  • KP1 (black)
Routes in Barrie Transit (Ontario)'s feed
RouteTypeLine color
10 NORTH LOOPBusbrown
100 REDBusred
101 BLUEBusteal
11 NORTH LOOPBusyellow
12A GEORGIAN MALLBuswhite
12B BARRIE SOUTH GOBuswhite
15A Mapleview Construction ShuttleBusteal
15B Mapleview Construction ShuttleBusblack
2A DUNLOPBusgreen
2B PARK PLACEBusgreen
400 EXPRESSBusteal
7A GROVEBusorange
7B BEAR CREEKBusorange
8A RVH/YONGEBusblack
8B Crosstown/EssaBusblack
KP1 Kempenfest ShuttleBusblack
List every stop
  • Downtown Hub
  • Bayview at Mollard
  • Layover
  • Lakeshore at Minets
  • Lakeshore at Southshore
  • Allandale Waterfront Station
  • Clapperton at H-Block
  • Bayfield at Simcoe
  • Burton at Huronia
  • Springhome Road
  • Bayview at Burton
  • Bayview at Little
  • Alliance Boulevard
  • Alliance Boulevard
  • Alliance Boulevard
  • Bell Farm at St Vincent
  • 115 Bell Farm
  • 130 Bell Farm
  • Willow Landing School
  • Brock at Innisfil
  • Brock at Innisfil
  • Huronia Road
  • Hurst Drive
  • Loon Avenue
  • Big Bay at Prince William Way
  • Portageview Public School
  • Big Bay Point at Pine
  • Royal Park Side Drive
  • Big Bay at Sandringham
  • Welham Road
  • Birchwood at Stanley
  • Springdale Drive
  • Birchwood Drive
  • 17 Blake Street
  • Blake at Johnson
  • Castle Drive
  • Collier Street
  • Parkview Center
  • Parkview Center
  • Rodney Street
  • Rodney Street
  • Essa at Gowan
  • St. Vincent Street
  • St. Vincent Street
  • Vancouver Street
  • Vancouver Street
  • Barrie By the Bay Plaza
  • Brock Street
  • Brock Street
  • John Street
  • John Street
  • Anne at Cundles
  • Bradford at Simcoe
  • Victoria Street
  • Victoria Street
  • Lakeshore at Centennial
  • Lakeshore at Centennial
  • Lakeshore at Victoria
  • Lakeshore at Victoria
  • Lakeshore at Simcoe
  • Lakeshore at Marina
  • Cundles at Anne
  • Mill Road
  • Bryne Drive
  • Burton at Bayview
  • Burton at Bayview
  • Garden Drive
  • Granville Street
  • Granville Street
  • Edgehill Drive
  • Peartree Court
  • Robinson Street
  • Robinson Street
  • Anne at Edgehill Drive
  • Blake at Huron
  • Steel Street
  • 429 Blake Street
  • Collier at Berczy
  • Albert Street
  • Collier at Clapperton
  • Collier at Clapperton
  • Collier at Mulcaster
  • Collier at Mulcaster
  • Owen Street
  • Owen Street
  • Poyntz Street
  • Poyntz Street
  • 112 Commerce Park Drive
  • 121 Commerce Park Drive
  • Downtown Hub
  • Norris Drive
  • Norris Drive
  • Anne at John Street
  • Cundles at J.C. Massie Way
  • Cundles at J.C. Massie Way
  • Janine Street
  • Anne at John Street
  • Cundles at Bluejay
  • Cundles at Daphne
  • Lions Gate
  • Lions Gate
  • Cundles at Livingstone
  • Shelly Lane
  • Burns Circle
  • Burns Circle
  • Cundles at Lillian
  • Cundles at Kozlov
  • Coleman Health Care Centre
  • Cundles at Sunnidale
  • Shirley Avenue
  • Cundles at Livingstone
  • Cundles at Livingstone
  • Longman Drive
  • Longman Drive
  • Cundles at Sunnidale
  • Emma King Elementary School
  • Emma King Elementary School
  • Donald at Anne
  • Anne Street
  • Shirley Avenue
  • Rose Street
  • Duckworth at Grove
  • Anne at Donald
  • Ferndale at Barrie Operations
  • Ferndale at Barrie Operations
  • Dunlop at Anne
  • Dunlop at Anne
  • Boys Street
  • Eccles Street
  • Anne at Donald
  • Eccles Street
  • Dunlop at Ferndale
  • Frances Street
  • Dunlop at High Street
  • Dunlop at Eccles
  • Sarjeant Drive
  • Valley Drive
  • Engel Crescent
  • Ferndale at Edgehill
  • Edgehill at Ferndale
  • Jagges Drive
  • Jagges Drive
  • Pringle at Ruffet
  • Anne at Vespra Street
  • Roberta Place
  • Roberta Place
  • Ecole Romeo Dallaire
  • Essa at Anne
  • Essa at Ardagh
  • Beacon Road
  • Bryne Drive
  • Dunn Street
  • Dyer Boulevard
  • Ecole Catholique
  • Anne at Victoria Street
  • Essa at Fairview
  • Essa at Fairview
  • Harvie Road
  • Harvie Road
  • Loggers Run
  • Loggers Run
  • Essa at Mapleview
  • Essa at Veteran's
  • Essa at Veteran's
  • Eaglestone Lane
  • Lewis Lane
  • Eden Drive
  • 314 Georgian Drive
  • 322 Georgian Drive
  • Grizzlies Way at Duckworth
  • Grizzlies Way at Duckworth
  • Georgian at Govenors
  • Georgian College
  • Georgian College
  • Gallie Court at Quarry Ridge
  • RVH Main Entrance
  • Georgian College
  • Bothwell Crescent
  • Barrie North Collegiate
  • Ardagh at Ferndale
  • Grove at Davidson
  • Steel at Blake
  • Maple Grove Public School
  • Oak Street
  • Owen Street
  • Owen Street
  • Ardagh at Ferndale
  • Grove at St. Vincent
  • Grove at St. Vincent
  • Grant's Way
  • Hawkins Drive
  • Snowshoe Trail
  • Adelaide Street
  • Innisfil at Essa
  • Snowshoe Trail
  • Johnson at Blake
  • Austen Lane
  • Wildflower Court
  • Johnson at Napier
  • Cheltenham Road
  • Cheltenham Road
  • Grove at Nelson
  • Johnson at Georgian
  • Johnson at Georgian
  • Johnson at Grove
  • Nelson at Grove
  • Johnson at Hickling Trail
  • Wildflower Court
  • Johnson at Mayor
  • Hickling Trail
  • Steel Street
  • Johnson at Steel
  • Kozlov at Cundles
  • Heather Street
  • Lampman plaza
  • Wright Drive
  • Browning Trail
  • Edgehill Drive
  • Georgian Mall
  • Georgian Mall
  • Celeste Drive
  • Margaret Drive
  • Meyer Avenue
  • Michael Crescent
  • East Bayfield Community Centre
  • Livingstone at Stanley
  • Stanley Street
  • Athabaska at Essa
  • Livingstone at Anne
  • Livingstone at Anne
  • Balliston Crescent
  • Wal-Mart Plaza
  • Wal-Mart Plaza
  • Livingstone at Bayfield
  • Delaney Crescent
  • Delaney Crescent
  • Athabaska at Essa
  • Ford Street
  • Ford Street
  • Kozlov Street
  • Kozlov Street
  • McDougall Drive
  • Milne Court
  • Neelands Street
  • Livingstone at Sunnidale
  • Lougheed Road
  • Livingstone at Sunnidale
  • Lougheed at Mapleview
  • Lougheed at Mapleview
  • Lougheed Road
  • and 316 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 72.32026-07-30: 72.32026-07-31: 72.32026-08-01: 72.3
Show the numbers
CheckScoreChange
2026-07-2572.3 first check
2026-07-3072.3 no change
2026-07-3172.3 no change
2026-08-0172.3 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

8 findings, ordered by severity.

Show every finding
  • Warning2295 instances

    2295 of 2295 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

  • Warning566 instances

    566 of 566 stops don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

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

  • Warning289 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

  • Warning98 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

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

  • Warning3 instances

    Same name and description for route (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules

  • Warning1 instance

    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

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

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

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)

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

Who this service reaches

In the areas this feed serves, the Canadian Index of Multiple Deprivation reads as moderate need, a within-Canada measure of economic dependency and situational vulnerability. Current, complete data matters most where need is highest.

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 91 days.
Accessible Not yet
States wheelchair access on 0% 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 91 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

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 76 / 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 100 / 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 45 / 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.

Barrie Transit (Ontario) GTFS data quality grade: C

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/barrie-transit/2026-08-01.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-08-01. 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.