Methodology
How this site is built, what each figure means, what is derived rather than published, and the rules the generator enforces.
- Buildings
- 11,078
- Sources
- 11
- Derived fields
- 2
- Estimated fields
- 0
The central claim
The Calgary and Edmonton datasets used here do not establish bay counts, bay dimensions, clear heights or loading doors. Each record describes an assessment account, address or parcel. Bay specifications require a separately identified source.
Everything else on this site follows from that. The evidence layer publishes buildings. The reference layer teaches how bays are generally built. The featured layer publishes bay facts that a named person has asserted. The three are never mixed.
What is published, and by whom
Two municipal assessment rolls, two permit and development systems, and two business licence registers. Calgary records are matched across years by exact assessment roll number; Edmonton by exact municipal account number. Permits, development applications and licences are matched to properties by exact normalised civic address.
Exact matching means some real relationships are missed. That is deliberate: a missed match leaves a gap, whereas a fuzzy match invents a fact. We would rather under-report than mislead.
The two derived figures
Address record score
The higher of two counts: the number of separately assessed accounts at a civic address, and the number of current business licences citing that address. It is a research score, not an occupant count or a bay count.
It can overstate or understate the number of occupants. A building can be demised into ten bays whose occupants need no municipal licence and which sit on a single assessment account, and it will show as one. Equally, several licences can belong to one occupant.
Occupancy tiers
Address record score grouped into four bands, so the record can be screened. The thresholds are arbitrary but fixed and published:
| Tier | Address record score | Buildings |
|---|---|---|
| One address record score | 1–1 | 9,401 |
| Two or three address records | 2–3 | 1,278 |
| Four to seven address records | 4–7 | 296 |
| Eight or more address records | 8 or more | 103 |
Fields that are reported, not interpreted
Calgary publishes sub-property use codes such as I101 and I102 without a public dictionary. They are reproduced verbatim and explicitly not interpreted. Edmonton publishes a gross building area figure without asserting its unit of measure; it is reproduced as published, labelled as such, and never converted or used in a calculation.
Rules the generator enforces
- A source record is an observation at a retrieval time, never a property fact.
- Absence is never a zero. No published year built means unknown. No matching permit means no matching record, not that nothing happened.
- Nothing is estimated, modelled or imputed. No rent, vacancy, availability, absorption, owner, tenant or transaction value appears anywhere, because none is in the sources.
- No bay-level field may enter the evidence dataset. The data build fails if one does.
- No personal information from licence registers is published — counts and category strings only. The data build fails if an identity field reaches the output.
- No MLS® System or CREA DDF content, in any form. Enforced by a scan over the built site.
- Every route collision fails the build, so no page can silently overwrite another.
The reference layer
Specification ranges on this site describe how industrial bays are commonly built in Western Canada. They are teaching figures, not a measurement of any particular building, and never a substitute for a site inspection or a measured drawing. It contains no market data of any kind. Where an answer depends on a code requirement, an approval or a lease term, the guide says who to ask instead of guessing.
The featured layer
Featured bay details are supplied by the landlord, owner or listing party named on the record and are reproduced as supplied. They are not drawn from the public record and are not verified by measurement. Confirm every dimension, service, cost and availability date in writing before you rely on it.
Each entry must name the authority under which it is published and record explicit consent, with the date the details were supplied. Entries failing validation are dropped from the build rather than rendered as placeholders.