t2 address import OSM extract Streets Toronto Open Data ranges Multi-addresses Corners OSM not in source Data GitHub · OSM discussion · MIT · Toronto Open Data & © OSM
Static snapshot of run high-park-swansea-sw-se-2026-05-13 as of 2026-05-13 — pilot evidence for the Toronto address import proposal. Interactive actions (stages, review decisions, uploads) are disabled. Run the live tool to exercise them.

Corner-lot & multi-street-name addresses 0

Source: C:\Users\kk\Code\toronto-2-address-import\data\osm\toronto-addresses.json · ← back to summary

A building on a corner lot often has two valid street addresses — one off each street. OSM encodes this by packing both street names into addr:street separated by ;, with matching numbers in addr:housenumber (also ;-separated). Example: addr:street=Rowatson Road;Fareham Crescent with addr:housenumber=55;50.

Comma in addr:street is a different signal. It usually means a single address where trailing bits (city, suite, unit) were dumped into the street tag instead of their own tag — not a real multi-street case.

Clue: this page simply enumerates every element in the clipped extract whose addr:street contains ; or ,. Click any row to open it on openstreetmap.org.

Corner lots (; in addr:street) 0

Canonical multi-value addresses: both a semicolon-separated street tag and (usually) a matching semicolon-separated housenumber.

none

Comma in street (likely malformed, not corner lots) 0

These are typically single addresses where the mapper stuffed extra locality/suite information into addr:street. The fix is usually to move that suffix to addr:city, addr:unit, or drop it entirely.

none