Feed status · checked 2026-09-05
Codiac Transpo
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in New Brunswick, 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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
755 of 755 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
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
1555 of 1555 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
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
- 755 of 755 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
- Feed evidence
- 1555 of 1555 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
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_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.
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.
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 84 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
The MobilityData validator flagged 1 kind of issue across 31 instances (0 error, 31 warning, 0 informational).
Service data covers the next 84 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (61, 94A, 82, 67, 64, and more).
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.
297 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Paul / Régis", "Mapleton / Plaza", "Trinity / The Brick", 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 755 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.
- 16 (purple)
- 50 (red)
- 51 (green)
- 60 (pink)
- 61 (gray)
- 62 (pink)
- 63 (pink)
- 64 (brown)
- 65 (orange)
- 66 (gray)
- 67 (purple)
- 68 (teal)
- 81 (purple)
- 82 (purple)
- 85 (red)
- 86 (purple)
- 93 (green)
- 94 (purple)
- 94A (purple)
- 96 (orange)
- 96A (orange)
- 98 (teal)
| Route | Type | Line color |
|---|---|---|
| 16 Hennessey | Bus | purple |
| 50 Red Line - Ligne Rouge | Bus | red |
| 51 Green Line - Ligne Verte | Bus | green |
| 60 Bessborough | Bus | pink |
| 61 Elmwood | Bus | gray |
| 62 Hildegard | Bus | pink |
| 63 Lewisville | Bus | pink |
| 64 Hospitals - Hôpitaux | Bus | brown |
| 65 Killam | Bus | orange |
| 66 Caledonia | Bus | gray |
| 67 Edinburgh | Bus | purple |
| 68 Ch Salisbury Rd | Bus | teal |
| 81 Riverview | Bus | purple |
| 82 Place Riverview Place | Bus | purple |
| 85 Riverview Connector | Bus | red |
| 86 Pinewood | Bus | purple |
| 93 Champlain | Bus | green |
| 94 Centrale | Bus | purple |
| 94A Centrale | Bus | purple |
| 96 Orange | Bus | orange |
| 96A Orange | Bus | orange |
| 98 Chartersville | Bus | teal |
List every stop
- St George North / Nord
- Pôle Aquatique Hub
- 58 Lorette
- Chartersville/Bonaventure
- Chartersville/Amirault
- Centrale/Norbert
- Amirault/des Copains
- Chartersville/Juniper
- 360 Acadie
- Place Champlain Place
- 14 Champlain
- 450 Paul
- 9 Champlain
- 500 Régis
- 450 Acadie
- Hotel de Ville Dieppe
- 304 Champlain
- 400 Champlain
- 560 Champlain
- 712 Champlain
- 1064 Bourque
- 91 Thomas
- 411 Gauvin
- 331 Acadie
- 441 Acadie
- 513 Régis
- Adélard-Savoie / Dieppe
- 41 Pascal
- 159 Pascal
- Acadie / Alain-Gillette
- 295 Amirault
- 393 Amirault
- 517 Amirault
- Amirault / Jacques
- 185 Acadie
- Paul / Régis
- Dawson / Adélard-Savoie
- 487 Champlain
- 848 Amirault
- 684 Amirault
- 536 Amirault
- 312 Amirault
- 402 Amirault
- 388 Gauvin
- Gauvin / Bras D'or
- 590 Gauvin
- Thomas / Avalon
- 595 Centrale
- 281 Pascal
- 253 Acadie
- 787 Centrale
- Bourque / Tranquille
- 411 Chartersville
- 333 Chartersville
- Dieppe / Englehart
- 733 Chartersville
- 667 Chartersville
- 228 Gould
- 615 Champlain
- 387 Champlain
- 297 Gould
- 135 Gould
- 190 Thomas
- 92 Thomas
- 721 Centrale
- 13 Thomas
- 701 Gauvin
- 469 Gauvin
- 120 Champlain
- 673 Amirault
- 443 Fox Creek
- Melanson / Fidèle
- 391 Fox Creek
- Fox Creek / LeBlanc
- Fox Creek / Amirault
- 1710 Amirault
- 1330 Amirault
- 1060 Amirault
- 275 Amirault
- 461 Paul
- 144 Gould
- 777 Gauvin
- 901 Gauvin
- 268 Acadie
- 1500 Amirault
- Centrale / Norbert
- Gauvin / Blanchard
- CCNB
- 476 Champlain
- 820 Champlain
- 703 Chartersville
- Bourque / Desrosiers
- 275 Chartersville
- 155 Thomas
- 473 Amirault
- 855 Amirault
- Malenfant/Industrial
- 680 Malenfant
- 424 Adélard-Savoie
- 355 Dieppe
- 1127 Champlain
- 1067 Champlain
- Dieppe/Englehart
- 370 Dieppe
- Champlain/Dieppe
- 1140 Champlain
- Adélard-Savoie/Sylvio
- 431 Adélard-Savoie
- Malenfant/Dawson
- Malenfant/Dawson
- 679 Malenfant
- Malenfant/Industrial
- Dieppe/Lakeburn
- Lakeburn/Kedwick
- Lakeburn/Mélanie
- Lorette/Lakeburn
- Lorette/Chartersville
- Chartersville/Therrien
- 829 Chartersville
- 781 Chartersville
- Bourque / Chartersville
- Vanier/Jolicoeur
- Vanier/Gilbert-Finn
- Vanier/Centrale
- Centrale/Damien
- Chartersville/Alberta
- Chartersville/Bourque
- Chartersville/Keith
- 694 Chartersville
- 731 Gauvin
- Amirault/Melanson
- Amirault/Lafayette
- Amirault/Pointe-aux-Renards
- Fox Creek/Marguerite
- Fox Creek/Leblanc
- Dieppe/Nathalie
- Dieppe/Caleb
- Dieppe/Yvonne
- Dieppe/Lakeburn
- Champlain/Midland
- Champlain/Dawson
- 813 Champlain
- Champlain/Industrial
- Champlain/Ste-Croix
- Dieppe/Murray
- Dieppe/Nathalie
- Melanson/Fox Creek
- 976 Champlain
- Bourque/Tranquille
- Bourque/Desrosiers
- Bourque/Clarence-Cormier
- Melanson/Centrale
- Centrale/Clarence-Cormier
- Centrale/Tranquille
- Alain-Gillette/Normandie
- Alain-Gillette/Normandie
- Gauvin/Thomas
- 798 Gauvin
- 894 Gauvin
- Pascal/Meunier
- Pascal/Dolbeau
- Bourque/Melanson
- Fox Creek/Belle-Forêt
- Fox Creek/Doiron
- Melanson/Fox Creek
- 971 Melanson
- Dieppe/Aucoin
- Dieppe/Caleb
- Dieppe/Aucoin
- 964 Melanson
- Maison Doiron
- 760 Champlain
- Champlain/Dawson
- Bourque/Eunice
- Bourque/Nobert
- Bourque/Melanson
- Alain-Gillette/Gauvin
- 42 Pascal
- Adélard/Sylvio
- Lorette/Benoit
- Chartersville/Dieppe
- Chartersville/Pascal
- Chartersville/Rideau
- 251 Champlain
- 260 Champlain
- 205 Champlain
- Bourque / Clarence Cormier
- 290 Gould
- UNIplex
- 219 Lewisville
- 111 Lewisville
- 37 Lewisville
- 1365 Mountain
- 1360 Mountain
- 1234 Mountain
- 1192 Mountain
- 1144 Mountain
- 1062 Mountain
- 1036 Mountain
- 1000 Mountain
- 950 Mountain
- 900 Mountain
- 854 Mountain
- 814 Mountain
- 770 Mountain
- 700 Mountain
- 640 Mountain
- 350 Mountain
- 344 Mountain
- 124 Highfield
- 1111 Main
- 1167 Main
- Vaughan Harvey YMCA
- Vaughan Harvey / Edmonton
- 803 Mountain
- 845 Mountain
- 913 Mountain
- 1001 Mountain
- 1049 Mountain
- 1111 Mountain
- 1185 Mountain
- 1247 Mountain
- 1313 Mountain
- 77 Weldon
- 880 Main
- 770 Main
- 644 Main
- 11 Main
- 100 Main
- 233 Main
- 655 Main
- 859 Main
- 961 Main
- 1387 Main
- Main / Westmount
- 73 Chapman
- Chapman / Mount Royal
- 45 Milner
- Milner / Bessborough
- 105 Bennett
- Bessborough / St George
- People's Park Tower
- 666 St George
- 89 Douglas
- 97 Tenth
- 140 Millennium
- 12 Millennium
- 136 Cornhill
- Cornhill / Gordon
- Université
- and 505 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
5 findings, ordered by severity.
Show every finding
- Warning1555 instances
1555 of 1555 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)
- Warning755 instances
755 of 755 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 (opens the GTFS Schedule reference on an external site)
- Warning31 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)
- 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)
- Warning1 instance
1 of 1555 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)
Conformance mark Not yet
One requirement remains for this feed to earn 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 84 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 84 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 94 / 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.
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/codiac-transpo/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.