Feed status · checked 2026-09-05
Transit Windsor
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Ontario, Canada.
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.
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
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
14444 of 14444 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
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
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 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
- 14444 of 14444 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
- The feed contains no fare information.
- Next action
- 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.
- 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 stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
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.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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 86 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
- 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
The MobilityData validator flagged 5 kinds of issue across 40 instances (0 error, 40 warning, 0 informational).
Service data covers the next 86 days.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
47 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tecumseh Rd. at Eastpark Plaza", "Tecumseh @ Marentette", "Wyandotte at St. Louis", 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.
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 1473 stops.
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.
- 1A (teal)
- 1C (teal)
- 2 (teal)
- 3 (purple)
- 4 (purple)
- 10 (teal)
- 518X (orange)
- 605 (black)
- 418X (orange)
- 115 (teal)
- 305 (teal)
- 25 (black)
- 205 (purple)
- 135 (teal)
- 315 (teal)
- 240 (purple)
- 250 (purple)
- 1000 (orange)
| Route | Type | Line color |
|---|---|---|
| 1A TRANSWAY 1A | Bus | teal |
| 1C TRANSWAY 1C | Bus | teal |
| 2 CROSSTOWN 2 | Bus | teal |
| 3 CENTRAL 3 | Bus | purple |
| 4 OTTAWA 4 | Bus | purple |
| 10 LAUZON 10 | Bus | teal |
| 518X 518 EXPRESS | Bus | orange |
| 605 ROUTE 605 | Bus | black |
| 418X 418 EXPRESS | Bus | orange |
| 115 ROUTE 115 | Bus | teal |
| 305 ROUTE 305 | Bus | teal |
| 25 LASALLE 25 | Bus | black |
| 205 ROUTE 205 | Bus | purple |
| 135 ROUTE 135 | Bus | teal |
| 315 ROUTE 315 | Bus | teal |
| 240 ROUTE 240 | Bus | purple |
| 250 ROUTE 250 | Bus | purple |
| 1000 Route 1000 | Bus | orange |
List every stop
- Banwell at Palmetto
- Tecmseh Mall Rear Entrance
- Devonshire Mall at Cineplex
- St Clair College Front Entrance
- Devonshire Mall at Cineplex
- Spitfires Way at Darfield
- Lauzon at Tecumseh Mall East Ent
- Spitfires Way at Bowler
- Lauzon at McHugh
- Lauzon at Spitfires Way
- Spitfire Way at Darfield
- Cabana at Mount Royal
- Wyandotte at Huron Church
- Wyandotte at Ellrose
- Plymouth at Central
- Plymouth at Grand Marais
- Plymouth at Tourangeau
- Plymouth at Robert
- Pillette at Plymouth
- Pillette at Grand Marais
- College at Lena
- College at Huron Church
- College at California
- California at Union
- California at U of W Engineering
- Seminole at George
- George at Metcalfe
- George at Franklin
- George at Ontario
- South National at Pillette
- South National at Norman
- South National at Ford
- South National at Ford
- South National at Westminster
- South National at Norman
- South National at Pillette
- George at Wyandotte
- George at Ontario
- George at Franklin
- George at Metcalfe
- Seminole at Westcott
- Crawford at Giles
- Milloy at Drouillard
- Crawford at Giles
- Knobb Hill at Whelan
- Knobb Hill at McLellan
- Sandwich at Alma
- Sandwich at Maple
- Sandwich at Richmond
- Sandwich at Simcoe
- Sandwich at Pickering
- Sandwich at McCurdy
- Sandwich at Malden Hill
- Lowes Sideroad at Dalhousie
- Sandwich at Malden Hill
- Sandwich at McCurdy
- Sandwich at Pickering
- Simcoe at Sandwich
- Simcoe at Victoria
- Fryer at Gibb
- Fryer at Richmond
- Fryer at Military
- Alma at Victoria
- Alma at Balaclava
- Alma at Sandwich
- Knobb Hill at McClellan
- Whelan at Knobb Hill
- Front at Laurier
- Knobb Hill at Texas
- Knobb Hill at Texas
- ROSEVILLE GARDEN AND TECUMSEH
- Walker at Highway 401
- Provincial at Clarke
- Lauzon at Trinity Towers
- Lauzon Rd. at ABC Day Nursery
- Lauzon at Tranby
- Provincial at Monarch Basics
- Legacy Park at Provincial
- Dominion at McKay
- Dominion at McKay
- Dominion at Holy Names
- Dominion at Holy Names
- Rivard at Adstoll
- Howard at Hildegard
- Howard at McDougall
- Meadowbrook at Parkside Estates
- Howard at Charles
- Howard at Charles
- Clemenceau at Haig
- Wildwood at Apple
- Deziel at Mannheim
- Rivard at Ambassador Church
- Meadowbrook at Essex Way
- Dougall at Norfolk
- Marentette at Foster
- Marentette at Division
- Mount Royal at Cabana
- Rhodes at Electricity
- Rhodes at Jamieson
- Rhodes at Enwin
- Kingsbridge at Front
- Front at Middle Side Road
- Front at Middle Side Road
- Kingsbridge at Front
- Walker at U-Haul
- Rhodes at UPS
- Tecumseh @ Marentette
- Walker at 7th Concession
- Cousineau at Country Club
- Riverside at Dieppe
- Riverside at Shoreline Towers
- Riverside at Bayview Towers
- Riverside at Riverside Towers
- Riverside at St Clair Towers
- Riverside at Island View Towers
- Riverside at Solidarity Towers
- Riverside at Westchester
- Ouellette at Ouellette Manor
- Tecumseh at Metro Plaza
- Texas at Front
- Texas at Front
- Tecumseh at Penang
- Little River Acres at Abbey
- Sprucewood at Abbott
- Sprucewood at Abbott
- Cousineau at Casgrain
- Campbell at Adanac
- Campbell at Adanac
- Rivard at Adstoll
- Pillette at Adstoll
- Pillette at Adstoll
- Little River Acres at Aire
- Little River Acres at Aire
- Walker at Airport
- Wyandotte at Albert
- Seminole at Albert
- Seminole at Chandler
- Seminole at Chandler
- Northway at Algonquin
- Drouillard at Alice
- Drouillard at Alice
- George at Alice
- George at Alice
- Pillette at Alice
- Pillette at Alice
- Ambassador at Urgent Care
- Tecumseh at Annie
- Tecumseh at Annie
- Dominion at Arcadia
- Dominion at Arcadia
- Matchett at Armanda
- University at Askin
- Aylmer at Assumption
- Gladstone at Assumption
- Lincoln at Assumption
- Tecumseh at Aubin
- Wyandotte at Aylmer
- Riverside at Aylmer
- Little River at Banwell
- Ducharme at Periwinkle
- South at Wells
- Wildwood at Beachdale
- Esplanade at Beachdale
- Dominion at Beals
- Beals at Glenwood
- Dougall at Beals
- Dougall at Beals
- Little River at Chateau
- Wyandotte at Belleview
- Wyandotte at Belleview
- Tecumseh at Benjamin
- Ottawa at Benjamin
- Seminole at Bernard
- Walker at Best Buy
- Southdale at Southridge
- Southdale at Bramley
- Dougall at Jackson
- University at Bridge
- Wyandotte at Bridge
- Wyandotte at Bridge
- Tecumseh at Bridge
- Tecumseh at Bridge
- Matchett at Broadway
- Sandwich at Brock
- Sandwich at Brock
- University at Bruce
- University at Bruce
- Wyandotte at Bruce
- Wyandotte at Bruce
- Tecumseh at Buckingham
- North Talbot at Burke
- Tecumseh at Byng
- Dominion at Cabana
- Cabana at Howard
- Howard at Cabana
- Walker at Cabana
- Walker at Cabana
- College Ave. at Community Centre
- Tecumseh at Cadillac
- Walker at Calderwood
- Walker at Calderwood
- University at California
- Tecumseh at California
- Tecumseh at California
- Labelle at California
- Dougall at Ouellette Place
- Dougall at Ouellette Place
- Spitfires Way at Bowler
- Wildwood and Forest Glade
- Wildwood at Hemlock
- Wildwood at Holly
- Wildwood at Deerbrook
- Wildwood at Soulliere
- Wildwood at Ancona
- Wildwood at Timber Bay
- University at Cameron
- University at Cameron
- Wyandotte at McKay
- University at Campbell
- University at Campbell
- Wyandotte at Campbell
- Wyandotte at Campbell
- Tecumseh at Campbell
- Tecumseh at Campbell
- Todd Lane at Canada
- Todd Lane at Canada
- Walker at Canada Post
- Tecumseh at Canadian Tire
- Tecumseh at Food Basics
- Walker at Canadian Tire
- Ducharme at Meridian
- Matchett at Carmichael
- Matchett at Carmichael
- University at Caron
- University at Caron
- Riverside at Caron
- Cousineau at Casgrain
- Cora Green at Castle Hill
- Gladstone at Cataraqui
- Lincoln at Cataraqui
- Lauzon at Cecile
- Lauzon at Cedarview
- Lauzon at Cedarview
- Riverdale at Cedarview
- Tecumseh at Central
- Tecumseh at Central
- N. Service at Central
- Seminole at Central
- Seminole at Central
- Tecumseh at Chandler
- and 1223 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
9 findings, ordered by severity.
Show every finding
- Warning14444 instances
14444 of 14444 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 (opens the GTFS Schedule reference on an external site)
- Warning40 instances
40 of 14444 trips have no headsign, the text that tells riders where the bus is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning26 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 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 (opens the validator rules on an external site)
- Warning2 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens GTFS Best Practices on an external site)
- 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 (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 100% 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 86 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 26 of 1473 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 86 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 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.
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/transit-windsor/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.