Inside the lab / Neighbourhood intelligence
Context before conclusions.
Our neighbourhood intelligence work is part of the Ontario data hub. We connect supported location information to useful real estate experiences, beginning with Hamilton.
A proprietary platform. Source-aware data.
Our hub brings location records, relationships, and API contracts into a consistent platform. The platform is ours; underlying source data retains its own ownership, licence, and attribution requirements.
Hamilton, Oakville, Burlington and Mississauga.
The platform includes school-directory import support for Hamilton, Oakville, Burlington and Mississauga. Address resolution and planning context have separate coverage: Hamilton is the initial municipal integration; Burlington and Mississauga sources remain readiness-gated, and Oakville lower-level place coverage is not activated. Actual availability depends on approved, current imports. This is not a claim of province-wide availability.
Context for the conversations that matter.
Supported location information can enrich neighbourhood experiences, help explain a place, and support realtor content workflows. Availability and permitted uses are confirmed before integration.
Coverage and freshness stay visible.
An endpoint existing does not mean every dataset is populated. Modules depend on approved source imports, scope, permissions, and the current coverage record.
Explore Coverage and freshness stay visible.Questions, answered.
Is this an MLS or IDX feed?
No. The hub is a location-context platform, not an IDX integration or live property-listing feed.
Are schools and real-time transit available?
School-directory imports support Hamilton, Oakville, Burlington and Mississauga. Nearby matches require a synchronized, current dataset and a supported location; attendance assignments and school ratings are not provided. Hamilton HSR scheduled-transit context depends on an approved static GTFS import and never represents real-time arrival predictions.
How do I get access?
Request access with your intended use and coverage needs. API access requires an approved account and authenticated credentials; public documentation alone does not provide access.