Calgary’s downtown Free Fare Zone.

The 7 Avenue corridor where Calgary Transit has been free since 1981 is under active Council review. This page collects what’s actually been said and decided: the motion text, the City staff report, ridership counts, the full decision history since 1981, and the claims now circulating online — every number linked to the original document.

fig 04.a · transitoperating cost

/year

City staff’s May 7 review: “no significant operating or capital cost impacts to remove the Free Fare Zone.”(IP2026-0286 attach. 2)

established

1981

Introduced as a pilot project to encourage early adoption of the new CTrain service.(admin report IP2026-0286)

survey-based · best case

$5M/year

In a Nov 2025 survey, 23% of zone riders said they’d pay if removed; 34% would leave.(IP2026-0286 · projection)

zone ridership

9.8M·2024

Total riders inside the zone in 2024 (Open Calgary’s ridership dataset).(Open Calgary · annual)

verification

primary-verified

derivation

Hand-authored from primary sources read at 2026-05-07; hero block reorganised on 2026-05-08 to lead with the operating-cost finding from IP2026-0286 Attachment 2; on 2026-05-08 the overview page was retired (its content lived in geographic_scope, watch_state, and claims_links — all of which were dropped from this artefact when the overview route became a redirect to /history). The previous FeatureStat (9.8M ridership pulled from numbers.json) is now BentoStat #3 — the cross-artefact invariant that bound feature_stat.value to numbers.derived.hero_stat_value.value_display has been retired (data-model.md note added in the same change). FeatureStat (‘$0 / yr operating cost change’) sourced from IP2026-0286 Attachment 2 p. 24 ‘Costs’ key takeaways (‘Overall, there are no significant operating or capital cost impacts to remove the Free Fare Zone.’) and cross-checked against the p. 25 performance-snapshot table cell (Operating costs row → ‘No change’). The ‘$0’ rendering presents admin’s assessment as a number; admin frames the figure as a removal-impact delta (no change from removing the zone), which by direct implication entails the zone has no significant standalone operating cost today — that inference is admin’s own (their assessment names this as the cost picture). The verbatim ‘no significant’ qualifier lives in the foot. BentoStat #1 (‘established 1981’) quoted from IP2026-0286 main report p. 2 DISCUSSION (‘introduced in 1981 as a pilot project to encourage early adoption of the new CTrain service’). BentoStat #2 (‘survey-based · best case $5M /yr’) quotes the verbatim ‘up to’ qualifier from IP2026-0286 main report p. 4 Cost savings (‘would increase fare revenue by up to $5 million annually’); the kicker calls out the methodology weakness (self-report, ceiling) and the foot surfaces the 23%-pay / 34%-find-alternative split from the customer-intercept survey (Attach. 2 p. 7) so the reader sees the contingency the projection rests on. BentoStat #3 (‘9.8M ridership · 2024’) is the iema-jbc4 SUM(free_fare_zone_ridership) for 2024, demoted from FeatureStat — value matches numbers.json’s derived.hero_stat_value.value_display (re-tied by hand, no longer enforced).

sources

[02]

Annual ridership and system share

The Free Fare Zone’s annual ridership and the Calgary Transit system total it sits inside, from Open Calgary’s Calgary Transit Ridership dataset (iema-jbc4), summed by year from 2007 to the most recent year. The 2024 value — 9.8M on the FFZ column, 9.7%of the system — is also surfaced as a bento stat in the piece header above.

Free Fare Zone ridership · system total ridership · share % labels above each FFZ bar.

Hatched bars (2015–2019): estimate-fill plateau in the upstream dataset (identical 8,540,060 across all five years — not a measured year-over-year sequence). Striped bar (2025 partial year): January through Sep only; rendered honestly so a reader does not extrapolate it to a full year and excluded from the headline FeatureStat.

The 2024 share — 9.7%— is what the ‘loses money’ framing has to land against: the FFZ corridor is roughly one in ten trips on the system, and admin’s own up-to-$5M projected uplift is conditional on the 23%-would-pay survey response.

data · data.calgary.ca / iema-jbc4

Methodology

The series is the verbatim aggregate of two columns on dataset iema-jbc4 — free_fare_zone_ridership and ridership(the system total) — grouped by year and ordered by year, filtered to year>=2007. The verbatim SoQL is recorded in the artefact’s meta.derivation so it is re-runnable from the source URL below. Per-year ffz_share is computed once in scripts/transit/free_fare_zone/numbers.py at generate time as ffz_ridership / total_ridership so the rebuttal in claims.json reads from a single source of truth rather than re-implementing the division in TS prose.

The Socrata response envelope re-renders volatile keys per request even when the data is unchanged, so the source is hashed under hash_strategy: json-canonical — volatile top-level keys are dropped and the payload is serialised with sorted keys before hashing. A verify.py --refetch run that reports drift therefore measures real content change, not render noise.

Two–three upstream caveats are surfaced honestly rather than smoothed over: (1) 2015–2019 in the published dataset carry the identical FFZ value 8,540,060 across all five years — implausible as a measured year-over-year sequence, almost certainly a placeholder fill — so those bars are rendered with a hatched fill on the chart and flagged estimate_fill: true on their series rows. (2) The most recent year (2025) covers only 9 of 12 months at the time of retrieval; that row is rendered with a striped fill, flagged partial: true, and excluded from the headline FeatureStat so it does not jump downward each January. (3)The column’s unit is undocumented in the dataset’s column metadata — the most recent full-year total (9.8M) does not match the May 7 2026 IPC admin report’s “about 5.4 million trips per year” restatement, which likely reflects this column counting boardings rather than linked trips. The hero stat is labelled “ridership column · 2024” for that reason; readers should not promote it to a trips claim.

verification

primary-verified

Every figure here was confirmed verbatim against the primary documents below.

source

[1]
Calgary Transit Ridership (iema-jbc4) — annual SUM(free_fare_zone_ridership) and SUM(ridership), 2007-2025
City of Calgary — Open Calgary
verified 2026-05-08

derivation

SoQL aggregate of the `free_fare_zone_ridership` and `ridership` columns on dataset iema-jbc4 (Calgary Transit Ridership), grouped by year, ordered by year, filtered to year>=2007. Verbatim SoQL: `$select=year,sum(free_fare_zone_ridership) as ffz_ridership,sum(ridership) as total_ridership&$where=year>=2007&$group=year&$order=year`. Per-row `ffz_share` is computed in this generator at write time as ffz_ridership / total_ridership, rounded to 4 decimals. The most recent year's row is flagged `partial: true` (with `partial_through_month`) when it carries fewer than 12 monthly entries in iema-jbc4 — that row is rendered on the chart but excluded from `derived.hero_stat_value` and `derived.year_max`, so the FeatureStat does not jump downward in January each year. Years 2015-2019 are flagged `estimate_fill: true` because the iema-jbc4 column carries the identical value 8,540,060 across all five years — implausible as a measured year-over-year sequence, almost certainly a placeholder fill — and the chart marks them visibly so a reader does not promote the plateau to a measurement claim. The 2010-2014 plateau is similar but slightly noisier; it is not flagged because it falls inside the noise-floor of dataset estimate-fills generally. The column's unit is undocumented in the dataset's column metadata; the May 7 2026 IPC admin report (IP2026-0286, DocumentId 358241 attachment 2 page 1) cross-references the FFZ as 'about 5.4 million trips per year', which differs from this column's most-recent annual total — the discrepancy is unresolved and likely reflects the column counting boardings rather than linked trips. The hero-stat unit is labelled 'ridership column · 2024' rather than claiming 'trips'.