Skip to content

Gapwise Data

Gapwise Data is the canonical public source for campus facts and geometry across 13 supported Canadian universities (15 campus models) used throughout the Gapwise ecosystem. Building identity, footprints, and metadata cover all supported institutions; additional reviewed exterior entrance registries and routing graphs are maintained for institutions like UTM and Carleton.

  • Portal: https://data.gapwise.ca
  • Entrance contributor (UTM): https://data.gapwise.ca/contribute
  • Canonical repository: GapwiseHQ/data
  • Raw UTM distribution: https://data.gapwise.ca/datasets/utm/latest/
  • UTM distribution manifest: https://data.gapwise.ca/datasets/utm/latest/manifest.json
  • Stable application API: https://api.gapwise.ca/v1

GapwiseHQ/data owns public campus facts: building identity, coordinates and footprints, entrances, routing graph inputs, available indoor data, provenance, evidence, uncertainty, and generated data audits.

The main gapwise repository owns deterministic behavior: route calculation, timetable semantics, gap planning, API orchestration, SDK contracts, and product presentation.

Gapwise Data owns campus facts. Gapwise owns product behavior.

No. Gapwise web and API builds contain a tested snapshot of the canonical dataset. That means an outage of data.gapwise.ca or GitHub does not make a student’s campus routing fail.

The relationship is:

GapwiseHQ/data canonical tree
↓ validate / pin
Gapwise build snapshot
↓
web app + API + deterministic engine

External developers can use the first-party Data distribution directly when raw artifacts are appropriate.

Need Use
Stable building/routing/gap semantics Public API or official SDK
Raw GeoJSON / graph / audit artifacts Gapwise Data distribution
Provenance and uncertainty explanation These docs + Data portal
Add or correct a UTM entrance Visual entrance contributor
Change validators, schemas, canonical tooling, or other campus facts GapwiseHQ/data
Permissioned private student context Gapwise AI / MCP

Entrance submissions from the visual contributor are review evidence; they do not write directly to canonical routing data. See Contributing campus data for the evidence and review workflow.

Start with Dataset catalog or Distribution and versioning.