Feed status · checked 2026-09-05
Halifax Transit
Based on the official feed source on file
Service mode Bus + Ferry
First scorecard for this agency
Catalogued in Nova Scotia, 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.
Checked for changes 1 hours ago; last changed 1 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
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
2358 of 2358 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
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
- Equal shape distance diff coordinates (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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
- Feed evidence
- Invalid phone number (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_phone_number' 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
- Feed evidence
- 2358 of 2358 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.
Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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.
Review the rule documentation for 'invalid_phone_number' 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.
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.
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 85 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 2 routes · 412 trips
- Terminal structure
- 3 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 3 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 412 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 412 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 412 ferry trips publish cars_allowed.
- Fares
- Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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 13 kinds of issue across 14692 instances (7 error, 14683 warning, 2 informational).
Service data covers the next 85 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.
3 accessibility depth signals
60 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 10A, 10B, 10C, 2, 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.
2239 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Akerley Blvd At Civic 75 (6001)", "Akerley Blvd After Joseph Zatzman Dr (6002)", "Akerley Blvd After Joseph Zatzman Dr (6003)", 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.
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 2358 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.
- 1 (blue)
- 10A (blue)
- 10B (blue)
- 10C (blue)
- 123 (green)
- 127 (green)
- 135 (green)
- 136 (green)
- 137 (green)
- 138 (green)
- 158 (green)
- 159 (green)
- 161 (green)
- 165 (green)
- 168A (green)
- 168B (green)
- 182 (green)
- 183 (green)
- 185 (green)
- 186 (green)
- 192 (green)
- 194 (green)
- 196 (green)
- 2 (blue)
- 21 (blue)
- 22 (blue)
- 24 (blue)
- 25 (blue)
- 26 (blue)
- 28 (blue)
- 29 (blue)
- 3 (blue)
- 30A (blue)
- 30B (blue)
- 320 (blue)
- 330A (blue)
- 330B (blue)
- 370 (blue)
- 39 (blue)
- 4 (blue)
- 401 (blue)
- 415 (blue)
- 433 (blue)
- 5 (blue)
- 50 (blue)
- 51A (blue)
- 51B (blue)
- 53 (blue)
- 54 (blue)
- 55 (blue)
- 56 (blue)
- 58 (blue)
- 59 (blue)
- 61 (blue)
- 62 (blue)
- 63 (blue)
- 64 (blue)
- 65 (blue)
- 67 (blue)
- 68 (blue)
- 6A (blue)
- 6B (blue)
- 6C (blue)
- 72 (blue)
- 7A (blue)
- 7B (blue)
- 8 (blue)
- 82 (blue)
- 83 (blue)
- 84 (blue)
- 85 (blue)
- 86 (blue)
- 87 (blue)
- 88 (blue)
- 90 (blue)
- 91 (blue)
- 93 (blue)
- 9A (blue)
- 9B (blue)
- FerD (teal)
- FerW (teal)
| Route | Type | Line color |
|---|---|---|
| 1 Spring Garden | Bus | blue |
| 10A Dalhousie - Bridge Terminal | Bus | blue |
| 10B Dalhousie - Micmac Terminal | Bus | blue |
| 10C Dalhousie | Bus | blue |
| 123 Timberlea Express | Bus | green |
| 127 Cowie Hill Express | Bus | green |
| 135 Flamingo Express | Bus | green |
| 136 Farnham Gate Express | Bus | green |
| 137 Clayton Park Express | Bus | green |
| 138 Parkland Express | Bus | green |
| 158 Woodlawn Express | Bus | green |
| 159 Colby Express | Bus | green |
| 161 North Preston Express | Bus | green |
| 165 Caldwell Express | Bus | green |
| 168A Auburn Express | Bus | green |
| 168B Cherry Brook Express | Bus | green |
| 182 First Lake Express | Bus | green |
| 183 Springfield Express | Bus | green |
| 185 Millwood Express | Bus | green |
| 186 Beaver Bank Express | Bus | green |
| 192 Hemlock Ravine Express | Bus | green |
| 194 West Bedford Express | Bus | green |
| 196 Basinview Express | Bus | green |
| 2 Fairview | Bus | blue |
| 21 Lakeside - Timberlea | Bus | blue |
| 22 Armdale | Bus | blue |
| 24 Leiblin Park | Bus | blue |
| 25 Governors Brook | Bus | blue |
| 26 Springvale | Bus | blue |
| 28 Bayers Lake | Bus | blue |
| 29 Barrington | Bus | blue |
| 3 CrossTown | Bus | blue |
| 30A Parkland | Bus | blue |
| 30B Dunbrack | Bus | blue |
| 320 Airport - Fall River Regional Exp | Bus | blue |
| 330A Tantallon | Bus | blue |
| 330B Tantallon - Sheldrake Lake Reg Exp | Bus | blue |
| 370 Porters Lake Regional Express | Bus | blue |
| 39 Flamingo | Bus | blue |
| 4 Universities | Bus | blue |
| 401 Preston-Porters Lake-Grand Desert | Bus | blue |
| 415 Purcells Cove | Bus | blue |
| 433 Tantallon | Bus | blue |
| 5 Portland | Bus | blue |
| 50 Dockyard | Bus | blue |
| 51A Windmill | Bus | blue |
| 51B Windmill | Bus | blue |
| 53 Notting Park | Bus | blue |
| 54 Montebello | Bus | blue |
| 55 Port Wallace | Bus | blue |
| 56 Dartmouth Crossing | Bus | blue |
| 58 Woodlawn | Bus | blue |
| 59 Colby | Bus | blue |
| 61 North Preston | Bus | blue |
| 62 Grahams Grove | Bus | blue |
| 63 Mount Edward | Bus | blue |
| 64 Akerley | Bus | blue |
| 65 Caldwell | Bus | blue |
| 67 Baker | Bus | blue |
| 68 Cherry Brook | Bus | blue |
| 6A Woodside | Bus | blue |
| 6B Eastern Passage | Bus | blue |
| 6C Heritage Hills | Bus | blue |
| 72 Portland Hills | Bus | blue |
| 7A Peninsula | Bus | blue |
| 7B Peninsula | Bus | blue |
| 8 Sackville Corridor | Bus | blue |
| 82 First Lake | Bus | blue |
| 83 Springfield | Bus | blue |
| 84 Glendale Express | Bus | blue |
| 85 Millwood | Bus | blue |
| 86 Beaver Bank | Bus | blue |
| 87 Sackville-Dartmouth | Bus | blue |
| 88 Bedford Commons | Bus | blue |
| 90 Larry Uteck | Bus | blue |
| 91 Hemlock Ravine | Bus | blue |
| 93 Bedford Highway | Bus | blue |
| 9A Greystone | Bus | blue |
| 9B Herring Cove | Bus | blue |
| FerD Alderney Ferry | Ferry | teal |
| FerW Woodside Ferry | Ferry | teal |
List every stop
- Mumford Terminal
- Bridge Terminal
- Lacewood Terminal
- Portland Hills Terminal
- Woodside Ferry Terminal
- Cobequid Terminal
- Highfield Terminal
- Micmac Terminal
- Penhorn Terminal
- Sackville Terminal
- Water St Terminal
- Ferry Stop - Halifax (1073)
- Ferry Stop - Alderney (1074)
- Ferry Stop - Woodside (1075)
- Wentworth Dr Before Dunbrack St (2000)
- Wentworth Dr After Dunbrack St (2001)
- Wentworth Dr Before Eliza Ritchie Cr (2002)
- Wentworth Dr After Eliza Ritchie Cr (2003)
- Booth St Before Scotsburn Ave (2004)
- Knightsridge Dr After Flamingo Dr (2005)
- Knightsridge Dr Before Flamingo Dr (2006)
- Ruth Goldbloom Dr Before Dunbrack St (2007)
- Ruth Goldbloom Dr After Dunbrack St (2008)
- Main Ave Before Dunbrack St (2009)
- Charles Rd At Civic 119 (2010)
- Charles Rd At Civic 193 (2011)
- Charles Rd Before Dixon Ct (2012)
- Charles Rd At Charles Rd Park (2013)
- Knightsridge Dr Before Dunbrack St (2014)
- Windsor St Before Bayers Rd (2016)
- Wright Ave Before MacDonald Ave (2017)
- Hammonds Plains Rd After Lewis Dr (2019)
- Hammonds Plains Rd Opposite Lewis Dr (2020)
- Barrington St Before North St (2021)
- Main St Before Gordon Ave (2022)
- Broad St After Gary Martin Dr (2023)
- Broad St After Samaa Ct (2024)
- Broad St Before Rose Fortune Gate (2025)
- Broad St Before Serontina Ln (2026)
- Broad St Before Larry Uteck Blvd (2027)
- Broad St After Larry Uteck Blvd (2028)
- Broad St After Bramwell Ct (2029)
- Broad St After Tilbury Ave (2030)
- Broad St Before Samaa Ct (2031)
- Broad St Before Gary Martin Dr (2032)
- Starboard Dr After Peakview Way (2033)
- Marketplace Dr After Bancroft Ln Bay 3 (2034)
- St Margarets Bay Rd After Crescent Ave (2035)
- Old Sackville Rd After Twelve Mile House Ln (2036)
- Old Sackville Rd Before Lynn Ct (2037)
- Old Sackville Rd At Civic 167 (2038)
- Old Sackville Rd After Walker Service Rd (2039)
- Old Sackville Rd Before Hallmark Ave (2040)
- Old Sackville Rd After Madeline Ave (2041)
- Old Sackville Rd After Sackville Cross Rd (2042)
- Old Sackville Rd Before Walker Ave (2043)
- Walker Ave At Civic 130 (2044)
- Walker Ave At Civic 129 (2045)
- Old Sackville Rd Before Dresden Ct (2046)
- Old Sackville Rd After Sackville Cross Rd (2047)
- Old Sackville Rd Before Madeline Ave (2048)
- Old Sackville Rd After Hallmark Ave (2049)
- Old Sackville Rd After Walker Service Rd (2050)
- Old Sackville Rd At Civic 178 (2051)
- Old Sackville Rd Before Lynn Ct (2052)
- Old Sackville Rd Before Sackville Dr (2053)
- Old Sackville Rd After Beaver Bank Conn (2054)
- Old Sackville Rd After Wynn Castle Dr (2055)
- Old Sackville Rd After Connolly Rd (2056)
- Old Sackville Rd After First St (2057)
- Old Sackville Rd At Civic 1055 (2058)
- Old Sackville Rd After Lucasville Rd (2059)
- Old Sackville Rd Before Melham Dr (2060)
- Crossfield Rg After Melham Dr (2061)
- Crossfield Rg Before Sackville Dr (2062)
- Sackville Dr Before Beaconsfield Way (2063)
- Beaconsfield Way After Sackville Dr (2064)
- Beaconsfield Way Before Darlington Dr (2065)
- Hanwell Dr After Darlington Dr (2066)
- Hanwell Dr After Barnsley Ct (2067)
- Hanwell Dr Before Barnsley Ct (2068)
- Hanwell Dr Before Darlington Dr (2069)
- Darlington Dr Before Beaconsfield Way (2070)
- Crossfield Rg After Sackville Dr (2073)
- Crossfield Rg Before Melham Dr (2074)
- Old Sackville Rd After Melham Dr (2075)
- Old Sackville Rd After Lucasville Rd (2076)
- Old Sackville Rd At Civic 1048 (2077)
- Old Sackville Rd At Civic 984 (2078)
- Old Sackville Rd Before Connolly Rd (2079)
- Old Sackville Rd Before Meadowlands Park Dr (2080)
- Old Sackville Rd After Peter Buckley Dr (2081)
- Commodore Dr After Eileen Stubbs Ave (2082)
- John Savage Ave After Commodore Dr (2083)
- John Savage Ave Before Garland Ave (2084)
- Garland Ave After John Savage Ave (2085)
- Garland Ave Opposite Civic 110 (2086)
- Garland Ave Before Wright Ave (2087)
- Williams Ave After Dorey Ave (2088)
- Williams Ave Before Frazee Ave (2089)
- Frazee Ave After Dorey Ave (2090)
- John Savage Ave After Frazee Ave (2091)
- John Savage Ave Before Frazee Ave (2092)
- Frazee Ave After John Savage Ave (2093)
- Williams Ave At Civic 46 (2094)
- Williams Ave Opposite Civic 109 (2095)
- Garland Ave After Wright Ave (2096)
- Garland Ave At Civic 110 (2097)
- Garland Ave Before John Savage Ave (2098)
- John Savage Ave After Garland Ave (2099)
- John Savage Ave Before Commodore Dr (2100)
- Commodore Dr Before Eileen Stubbs Ave (2101)
- Eileen Stubbs Ave After Commodore Dr (2102)
- Eileen Stubbs Ave After MacLean Ave (2103)
- Brownlow Ave After Eileen Stubbs Ave (2104)
- Brownlow Ave Before MacLean Ave (2105)
- Brownlow Ave Before Commodore Dr (2106)
- Colford Ave After Akerley Blvd (2107)
- Colford Ave Before Gloria McCluskey Ave (2108)
- Gloria McCluskey Ave After Colford Ave (2109)
- Gloria McCluskey Ave Before Akerley Blvd (2110)
- Millwood Dr Before Jackladder Dr (2111)
- Jackladder Dr Before Slicers Ln (2112)
- Jackladder Dr Before Rossing Dr (2113)
- Rossing Dr At Civic 270 (2114)
- Rossing Dr After Larrigan Dr (2115)
- Rossing Dr At Civic 72 (2116)
- Rossing Dr Before Millwood Dr (2117)
- Beaver Bank Cross Rd At Civic 222 (2118)
- Beaver Bank Cross Rd At Civic 190 (2119)
- Beaver Bank Cross Rd Before Loggen Rd (2120)
- Sackville Dr After Jubilee Ln (2121)
- Mumford Rd Opposite Mumford Terminal Bay 4 (2122)
- Beaver Bank Rd before Kinsac Rd (2123)
- Starboard Dr At Civic 530 (2134)
- Starboard Dr After Friesian Ct (2135)
- Starboard Dr At Civic 350 (2136)
- Starboard Dr Before Sentry Ct (2137)
- Starboard Dr Before Helmsman Ct (2138)
- Starboard Dr Before Amirault Ct (2139)
- Starboard Dr After Amirault Ct (2140)
- Starboard Dr After Cutter Dr (2141)
- Starboard Dr After Sentry Ct (2142)
- Starboard Dr At Civic 357 (2143)
- Starboard Dr Before Friesian Ct (2144)
- Starboard Dr Opposite Civic 530 (2145)
- Hammonds Plains Rd After Bedford Hwy (2155)
- Williams Lake Rd After Purcells Cove Rd (2156)
- Williams Lake Rd After Wyndrock Dr (2157)
- Williams Lake Rd Before Sagewood Ln (2158)
- Williams Lake Rd After Clovis Ave (2159)
- Pine Grove Dr At Civic 29 (2160)
- Pine Grove Dr Before Theakston Ave (2161)
- Theakston Ave Before Danforth Rd (2162)
- Alabaster Way After Drysdale Rd (2163)
- Alabaster Way After Quartz Dr (2164)
- Alabaster Way After Mica Cr (2165)
- Alabaster Way After Lier Rg (2166)
- Alabaster Way At Civic 391 (2167)
- Alabaster Way At Civic 475 (2168)
- Titanium Cr After Travertine Ct (2169)
- Alabaster Way Before Lier Rg (2170)
- Alabaster Way Before Mica Cr (2171)
- Alabaster Way Before Quartz Dr (2172)
- Alabaster Way Before Drysdale Rd (2173)
- Theakston Ave After Danforth Rd (2174)
- Pine Grove Dr After Theakston Way (2175)
- Pine Grove Dr At Civic 24 (2176)
- Williams Lake Rd After Herring Cove Rd (2177)
- Williams Lake Rd Before Lyons Ave (2178)
- Williams Lake Rd Before Rainforth Ave (2179)
- Williams Lake Rd After Birchview Dr (2180)
- Williams Lake Rd Before Purcells Cove Rd (2181)
- Beaver Bank Rd At Civic 141 (2182)
- Beaver Bank Rd Before Stokil Dr (2183)
- Beaver Bank Rd At Civic 136 (2184)
- Beaver Bank Rd Before Civic 178 (2185)
- Beaver Bank Rd After Woodbine Dr (2186)
- Parkland Dr After Bethany Way (2188)
- Titanium Cr Before Alabaster Way (2189)
- Southgate Dr Before Ravines Dr (2190)
- Southgate Dr At Civic 204 (2191)
- Southgate Dr Before Bedford Highway (2192)
- Southgate Dr After Bedford Highway (2193)
- Southgate Dr Before Windstone Cl (2194)
- Southgate Dr Before Stockton Rg (2195)
- Southgate Dr Before Windridge Ln (2196)
- Hammonds Plains Rd Before Bedford Highway (2197)
- Breeze Dr after Castleton Ct (2198)
- Breeze Dr Before Pompano Ct (2199)
- Columbo Dr After Civic 33 (2200)
- Appian Way Before Colonna Pl (2201)
- Bedford Hwy at Civic 656 (2202)
- Charles Keating Dr after Waverley Rd (2203)
- Dorothea Dr After Topsail Blvd (2204)
- Astral Dr Before Grenadier Dr (2205)
- Cowie Hill Rd Before Peter Saulnier Dr (2206)
- Cowie Hill Rd After Peter Saulnier Dr (2207)
- Cowie Hill Rd After Civic 455 (2208)
- Cowie Hill Rd Before Hadley Cr (2209)
- Old Sambro Rd After Schnare Rd (2210)
- Novalea Dr Before Glebe St (2211)
- Glebe St Before Acadia St (2212)
- Kencrest Ave After Glebe St (2213)
- Kencrest Ave Opposite Newbery St (2214)
- Novalea Dr After Normandy Dr (2215)
- Craigburn Dr Before Hazelnut Ct (2216)
- Craigburn Dr After Civic 278 (2217)
- Caldwell Rd After Birchill Dr (2218)
- Caldwell Rd Opposite Kaleigh Dr (2219)
- Hornes Rd At Civic 12 (2221)
- Hornes Rd At Civic 42 (2222)
- Hornes Rd At Civic 74 (2223)
- Cowie Hill Rd After Dunbrack St (2225)
- Cowie Hill Rd Before Civic 455 (2226)
- Forest Hills Pky Before 2nd Flying Cloud Dr (2227)
- Forest Hills Pky Before Merrimac Dr (2228)
- Forest Hills Pky Before 1st Chameau Cr (2229)
- Forest Hills Pky After Main St (2230)
- Forest Hills Pky Before Flying Cloud Dr (2231)
- Forest Hills Pky Before 2nd Taranaki Dr (2232)
- Forest Hills Pky Before Main St (2233)
- West Bedford Park and Ride Bay 1 (2234)
- West Bedford Park and Ride Bay 2 (2235)
- West Bedford Park and Ride Bay 3 (2236)
- West Bedford Park and Ride Bay 4 (2237)
- Main St After Panavista Dr (2238)
- Main St Before Hillsboro Dr (2239)
- Main St After Montague Dr (2240)
- Main St Before Panavista Dr (2241)
- Flying Cloud Dr After Forest Hills Pky (2242)
- Flying Cloud Dr At Civic 268 (2243)
- Sherwood St After Carlisle Dr (2245)
- Sherwood St Before Woodbury Dr (2246)
- Sherwood St Before Shrewsbury Rd (2247)
- Albro Lake Rd Before Slayter St (2248)
- Albro Lake Rd After Sheridan St (2249)
- Leaman Dr Before Ambercrest Pl (2251)
- Crystal Dr Before Farthington Pl (2252)
- Crystal Dr Before Pinecrest Dr (2253)
- Flamingo Dr Before Oriole St (2254)
- Collins Grv After Regal Rd (2255)
- Collins Grv At Civic 70 (2256)
- Collins Grv Before Spring Ave (2257)
- Dorothea Dr After Spring Ave (2258)
- Dorothea Dr Before Donview Dr (2259)
- Lucien Dr After Dorothea Dr (2260)
- Lucien Dr Before Whynette Pl (2261)
- Windward Ave After Lucien Dr (2262)
- Lea St Before Topsail Blvd (2263)
- and 2108 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
18 findings, ordered by severity.
Show every finding
- Error6 instances
Equal shape distance diff coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9239 instances
9239 of 9239 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning9140 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)
- Warning4575 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 (opens the validator rules on an external site)
- Warning2358 instances
2358 of 2358 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)
- Warning412 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning382 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning106 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 (opens the validator rules on an external site)
- Warning60 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · 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
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 to link entrances, platforms, and elevators. Give each one a level. (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 (opens the GTFS Schedule reference on an external site)
- 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 (opens the validator rules 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
Two requirements remain for this feed to earn the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 85 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 85 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 7 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 6 / 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 38 / 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/halifax-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.