Twelve Canadian questions only a data join can answer

Asked (summary):

What important public-policy or business questions in Canada can only be answered by combining two or more open datasets — for example procurement plus corporate registries, grants plus lobbying records, or health data plus demographics? Give concrete examples naming the datasets involved.

Twelve concrete, sourced Canadian examples, each backed by its own independent source — 12 distinct hosts spanning government pages, academic research, policy research and public-data investigations. This is a curated portfolio of important examples, not an exhaustive universe. In every case one dataset records an action or outcome, the other supplies identity, population, exposure or context — the value comes from the join.

The data-combination opportunity map

Each row is one question: dataset 1 → join method → dataset 2, grouped by decision domain. Colour is the join pattern readers can reuse. Hover or tap a row for the decision it enables and its limitations; dashed-outline dataset boxes are searchable public registries rather than downloadable open files.

geographic overlay entity resolution temporal / contextual linkage searchable registry (not a download)

What the map cannot say alone

The highest-effort joins are entity resolution with no shared key: tracing ultimate owners of licensed child-care facilities took months of manual work through numbered corporations (policyalternatives.ca), and a national company dataset means fuzzy-matching names across fourteen registries with no public identifier (monetaiq.com).
Geographic overlay is the workhorse: seven of the twelve questions join on coordinates or standard census geography, from NPRI emitter buffers over dissemination areas (cell.com) to GTFS routing from census centroids (schoolofcities.utoronto.ca).
Public-integrity questions hinge on tenure: donations show who funds a party and contracts show who won — only keyed to who governed at the award date do they show the money around an office-holder's decisions (thepublicledger.ca).
Limitations travel with the join: broadband maps are published at reduced resolution for confidentiality (ised-isde.canada.ca), facility presence is only a proxy for exposure, and data wrangling can consume about 70% of a project's time (ijpds.org).

Three join patterns to reuse

Entity resolution

Names, addresses, owners

Match records on names, addresses, phone numbers or shared contacts when no public key exists — child-care licences to business registries, fourteen corporate registries into one dataset, open business attributes onto Corporations Canada, IBD suppliers to CanadaBuys tenders.

Geographic overlay

Coordinates and census geography

Overlay points, buffers or coverage areas on dissemination areas, subdivisions or economic regions — NPRI emitters on census demographics, broadband coverage on populations and labour outcomes, transit schedules on income quintiles.

Temporal / contextual linkage

Same entity, same period

Join on a shared entity and the relevant date or tenure — contracts, grants and lobbying contacts matched to a minister's department during their time in office; disease counts matched by jurisdiction and period to validate a century of records.

All twelve questions

#Question answered by the joinDataset 1Dataset 2 & additionalJoinDomainSource

Curated portfolio of 12 Canadian data-linkage questions, one row per question, each backed by a distinct source URL on a distinct host (government, academic, policy and public-data sources); compiled 2026. Columns record the named core datasets, publishers where identified, linkage method, decision value and stated limitations; long question, method and limitation texts are shortened on the page and shown in full on hover in the map. Join-pattern and domain groupings were assigned editorially from the stated linkage methods.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.

Keenable SELECTAsk your own question
Made with Keenable SELECT