Site intelligence,
on public record.

Type an address — get the answer, not a data dump. Zoning & permitted-use, flood and watercourse constraints, and council-records history across Canada.

One address → the whole picture in a single brief: supermarket permitted-use, flood & watercourse constraints, and recent council activity.

Highlights — full due-diligence on one site

Any address in a covered municipality → the supermarket permitted-use verdict, governing bylaw, and the traps.

Highlights — these reveal the traps

Or try any covered city — click to verify a real store

Regulated area, floodplain, watercourses & wetlands near the site — with the development implication. Ontario, Quebec, Alberta & Manitoba.

Examples

Did council or a committee approve a measure in a date window? Wording needn't be exact — it searches by meaning. Built for letter-of-credit releases.

Measure (pick or type) Street / property

From

Municipality

Committees to search

Sources — official municipal zoning GIS · conservation-authority & provincial flood layers · public council records
Decision-support only. Confirm with a zoning certificate / conservation authority before relying on results.

Report

Your report appears here

Pick a workflow, enter an address, and run it. The findings build on this side — verdict, the facts that matter, and the traps.

Generating report

Under the hood

How it actually works.

No screenshots, no clicking through a map, no pretending. Each workflow reads the same official databases the government's own map reads — directly, by API. Here's the exact path, end to end, with a live inspector so you can prove it on any address.

The map is a viewer. We read its database.

When you open Toronto's zoning map and click a parcel, the page doesn't "know" the zoning — it fires an HTTP request to an ArcGIS REST server behind it and draws the answer. That server is public. We call the same endpoint directly with a point-in-polygon query, and get the identical authoritative record — no pixels, no human clicking, no interpretation step.

What a person does

Open the viewer, pan/zoom to the address, click the parcel, read the popup. The hatched overlay = "former by-law lands" rendered as colored tiles.

map.toronto.ca/maps/map.jsp?app=ZBL_CONSULT

What the workflow does

Geocode → query the REST server the viewer itself calls, at the exact coordinate. Get back the raw attributes: zone, exception, the former-by-law label.

gis.toronto.ca/.../cot_geospatial11/FeatureServer/8/query?geometry=x,y&spatialRel=esriSpatialRelIntersects

↑ Same server · same data · the viewer is just one of its clients

Prove it — inspect a real address

Type any address. This runs the real zoning + flood pipeline and shows every government endpoint it actually hit — status, latency, and the live URL (click it: your browser gets the same raw JSON the server did). Then cross-check against the official viewer.

Hitting live government endpoints…

The three workflows, step by step

Every endpoint shown is public and live. Decision-support only — confirm with a zoning certificate / the conservation authority before relying on results.

Sign in to IntelliZone

Site intelligence,on public record.

Your report appears here

How it actually works.

The map is a viewer. We read its database.

Prove it — inspect a real address

Site intelligence,
on public record.