Section 01
How to use the comparison
Choose up to three places. The table returns the same six attributes for each: the parent planning context, the plan type, the official adopted or consolidated document, the landform or open-space interface, the servicing and transportation questions the plan raises, and the per-address records to request.
Read across a row rather than down a column. The useful insight is almost always that two places generate different questions, not that one place scores higher than another on some invented measure.
Section 02
What the comparison is not
It is not a ranking, a rating, a shortlist generator or a recommendation, and it produces no best result. It contains no prices, no listing inventory, no sales data, no market direction and no travel times, and it makes no statement about the quality, prestige or desirability of any place.
It is also not parcel-level advice. Two properties inside the same plan area can differ completely in zoning, registered interests, condition and approval history, and this tool does not know about any address.
Plan attributes are drawn from a policy framework. They do not prove current zoning, built form, condition, views, access, amenity entitlement, price or market status for any parcel.
Section 03
Local-only by design
The comparison runs entirely in the page. There is no form, no submission, no network request, no analytics event and no browser storage, so selections vanish when the tab closes and nothing about your research reaches the atlas or anyone else.
Copy and print are provided because research belongs in your own file. Both act on the text already on screen.
Section 04
Why these six attributes
Parent context and plan type establish which documents govern and how they relate. The adopted or consolidated source establishes what you should actually read and cite. The landform interface identifies the constraint most likely to generate conditions on a parcel.
The servicing and transportation column captures what a plan contemplated and therefore what to ask the City about now, and the records column converts the whole comparison into a request list for a specific address. Nothing else was included, because every additional column would have required a judgement rather than a record.
Section 05
What to do with the output
Take the records column to the seller, the City and your lawyer, and take the servicing column to the City as a status enquiry. Read the underlying plan document for any place you are seriously considering rather than relying on a summary row.
Then, and only then, form a view. A plan comparison narrows research; it does not decide anything, and this atlas holds no listings to point you at afterwards.
Section 06
Where the attributes come from
Each row is authored from the corresponding official City plan document and from the City's own material on plans in effect and the development process. Every source is listed on this page with its retrieval date, and each place has its own record with fuller reasoning.
Where a plan document is silent on something, the comparison is silent too. Absence in a column means the plan does not settle it, not that the answer is negative.
The five places were chosen because each has its own adopted or consolidated City plan document with a distinct landform, servicing or planning-context angle, which is what makes a side-by-side reading useful rather than repetitive. No place was included or excluded on the basis of price, desirability, inventory or market activity, none of which appears anywhere in this atlas, and adding a sixth column would only be justified by another distinct official document rather than by demand for a longer list. If you are researching an area that is not represented here, the same method still applies: identify the statutory plan in effect, read it against the current zoning for the parcel, then request the title, permit, grading and survey records that describe the property itself.
Read the linked plan record for any place before relying on a single row of this table.