Thunder Bay/Address Import

From OpenStreetMap Wiki
Jump to navigation Jump to search

Template:Map of imports

Status

  • Stage: Proposed. Community review open from 2026-11-08 to 2026-11-22; nothing has been uploaded.
  • Last revised: 2026-11-09
  • Contact: toronto@comentality.com
  • OSM import account: skfd imports, dedicated to imports; the maintainer's personal account (skfd) uploads nothing from this tooling.
  • Discussion: forum thread on the OSM Community Forum, tagged import.
  • Tooling: thunder-bay-address-import (this city's configuration) on the engine address-importer-friend, the same engine that imported Toronto (~449,000 addresses, 2026) and maintains Guelph.

This proposal follows the OSM Import Guidelines. The 14-day review window opened with the forum post on 2026-11-08; no upload happens before it closes on 2026-11-22.

Land acknowledgement

Thunder Bay is on the traditional lands of the Anishinaabe peoples, including Fort William First Nation, within the Robinson-Superior Treaty territory, and is part of the historic Métis homeland. First Nations should have more say in, and more ownership of, how their traditional lands beyond their reserves are developed, including the land Thunder Bay stands on.

The first sentence adapts the City of Thunder Bay's Deepening Understanding page.

The 378 addresses on Fort William First Nation reserve land wait until the Nation has answered our letter, and are left out if it has not answered within 30 days; see § Fort William First Nation.

Summary

Human-reviewed import of missing civic address points from the City of Thunder Bay's municipal address layer. Each address is checked against a fresh OSM snapshot, so only addresses OSM does not already have are created. Every run is reviewed by a person in a local web UI before it is uploaded. Every upload is its own tagged changeset, and every decision is logged.

Thunder Bay's addresses in OSM today are almost entirely CanVec 6.0 interpolation: 6,604 addr:interpolation ways (odd/even block ranges), whose endpoints are 12,763 of the 12,950 address nodes in the city (2026-11-06 Geofabrik extract). Apart from those there are about 190 standalone address nodes and 390 address-bearing ways. There are no import tags, no import page and little recent address activity; the last broad change was a 2018 retag.

Geographic scope: the City of Thunder Bay, Ontario, plus Fort William First Nation land in a separate phase. The City's 7 wards (Westfort, McIntyre, Neebing, Red River, Northwood, McKellar, Current River) split the work into review tiles.

Scope numbers (source snapshot #18, 2026-11-07):

Rows Count Disposition
City of Thunder Bay (CITY = THUNDER BAY) 44,722 Candidates, phases 1–2.
Fort William First Nation (CITY = FWFN) 378 Phase 3, gated. 8 have no civic number and are dropped.
No CITY value 2 Reviewed by hand.
Total 45,102 Before conflation.

Baseline conflation (2026-11-08) against the 2026-11-06 Geofabrik extract: 322 already in OSM, 27 near-matches for review, 44,740 missing (44,379 in the City, 361 on Fort William First Nation land); 9 rows with no civic number are skipped. Only the missing ones are candidates for upload. The near-total gap is what the CanVec situation below predicts.

Goals and non-goals

Goals

  • Add the civic addresses OSM is missing in Thunder Bay, from the City's authoritative roster.
  • Create no duplicates of addresses already in OSM, and change no existing address data.
  • Keep a per-address audit trail (source row → verdict → reviewer decision → changeset → OSM id) anyone can inspect.

Non-goals

  • No deletions, no edits to existing objects, no geometry edits, no buildings and no addr:interpolation cleanup. Create-only, exactly as Toronto's.
  • The CanVec interpolation ways stay untouched during the import. Their cleanup is a separate, later effort; see § CanVec interpolation.

Schedule

Contacts and reviewers

  • Maintainer and first reviewer: toronto@comentality.com
  • Local mappers contacted before this page went up: Matthew Darwin, eireidium. Both are invited to review.
  • Fort William First Nation: Lands & Governance, by letter on 2026-11-08. See below.
  • Upload rule: nothing uploads without a reviewer's approval in the web UI.

Phases

Each phase can ship on its own and be reverted on its own.

  • Phase 0 — community review. This page, a forum post tagged import, and a 14-day feedback window.
  • Phase 1 — pilot, one tile. mckellar-sw-sw-ne in downtown Fort William: 495 candidates, 493 of them missing, fully reviewed by hand. One-week hold before Phase 2.
  • Phase 2 — the City, ward by ward. One tile per changeset, 250–750 source addresses each, at most one changeset a minute by manual cadence.
  • Phase 3 — Fort William First Nation. Only after the Nation has answered, or after the wait in § Fort William First Nation. Its own tiles and changesets, never mixed with City tiles.
  • Phase 4 — closeout and upkeep. A closing report here and on the forum thread. After that the City's new addresses are added monthly under the same rules, as for Toronto.

Fort William First Nation

The City's address layer includes 378 points on Fort William First Nation land, a separate jurisdiction from the City. They have no City parcel number. The City publishes them under the same open licence, so the licence permits importing them. But we must ask the Nation, since it is a separate jurisdiction. There is no Canadian OSM import precedent we could find either way.

  • A letter went to FWFN Lands & Governance on 2026-11-08 asking: whether the Nation is comfortable with the addresses being in OSM; who assigns them; and whether there is a process to follow.
  • If the Nation says no, Phase 3 does not happen, and this page says so.
  • If the Nation asks for changes (names, spellings, a subset), we make them.
  • If there is no reply after 30 days, we skip Phase 3.

CanVec interpolation

Almost all of Thunder Bay's existing OSM addressing is CanVec block ranges: an odd and an even addr:interpolation way along each block face, with a numbered node at each end. The endpoints carry real-looking addr:housenumber/addr:street tags, but they are range limits placed along the road, not buildings. The ranges imply up to ~127,000 numbers for a city of ~45,000 addresses.

Like Toronto's, the engine does not count interpolation endpoints as existing addresses, so nearly every City address will be a candidate, and for a while the City's real points will sit alongside CanVec's synthetic ranges.

This import does not touch the interpolation ways or their endpoint nodes. Retiring them is a separate effort, done the way Toronto's was: against-interpolation generates one MapRoulette task per interpolation line once the City's points are in, showing the house numbers the City has for that block. A mapper checks them, then removes the line, keeping any endpoint that is part of a building or carries other tags. Lines with no City points on them get no task. That work is human-reviewed line by line and will get its own forum post before it starts.

Import data

Source

Licence

Type and volume

  • Points only: civic number, street, municipality (THUNDER BAY or FWFN), parcel id, property type. No unit field (14 units are written into the civic number; see Conflation), no postcodes, no ranges.

Freshness

  • OSM side: Geofabrik Ontario extract, refreshed before each session. If more than 24 h pass between conflation and upload, re-conflate first.

Tagging plan

All uploads are nodes.

Tag From Notes
addr:housenumber ADDRESS The full civic number with its qualifier: 688B, 963 1/2. The City's integer column drops qualifiers on 338 rows, so it is not used.
addr:street ROOT The City publishes abbreviated capitals (JAMES ST S); expanded and title-cased on the way out: James Street South, 103rd Street.
addr:unit ADDRESS Only on the 14 Caribou Crescent doors whose number the City writes as 270-1.
source:addr static City of Thunder Bay Open Data. Changed 2026-11-09, before any upload, from addr:source: source:addr is the established spelling (the wiki's source:<key> form, 13.3M uses on taginfo against 98k for addr:source, whose wiki page only redirects to historic).
addr:postcode OSM Only copied from a same-address POI already in OSM. The City publishes no postcodes, and none are invented.

Not written: addr:city (redundant inside the city; for FWFN, ask the Nation first), addr:province, addr:country, addr:unit except the 14 Caribou Crescent doors, ward, parcel id, property type.

Changeset tags

Tag Value
comment Thunder Bay Open Data address import, run=<run name>
source City of Thunder Bay Open Data
import / bot yes / no
import_plan this page
created_by address-importer-friend
import:client_token random per run, for safe retry after a dropped connection

Conflation

The same as Toronto's; see Toronto § Conflation. In short: MATCH when OSM has the same number and street within 15 m; MATCH_FAR (15–100 m), always reviewed by a person; MISSING otherwise. Pure address nodes and address-bearing polygons are match targets, POIs are not.

Thunder Bay specifics:

  • The street name is matched on the City's ROOT (BAILEY AVE), expanded the same way on both sides.
  • 14 numbers carry a unit after a hyphen (270-1 … 276-4, three townhouse blocks on Caribou Crescent). They are split: addr:housenumber=270 + addr:unit=1, one node per door. The City places each unit about 6 m apart.
  • Duplicates within the source (same number and street within 3 m) are flagged for review.

Workflow and QA

The same pipeline, checks, review queue, audit log and upload manifest as Toronto. Checks enabled for Thunder Bay: match_far, city_duplicate, missing_sample (every 50th MISSING is reviewed by hand), nearby_street_mismatch. No suffix_range: the source has no ranges. An upload manifest (source row → OSM node → changeset) is published per tile.

Risks and mitigations

Risk Mitigation
New points alongside CanVec ranges describing the same block Expected and temporary; the ranges are retired afterwards line by line by mappers, through against-interpolation (§ CanVec interpolation).
A standalone address already in OSM in another spelling nearby_street_mismatch surfaces spelling variants; the pilot is reviewed by hand.
Adding addresses a First Nation did not want added Phase 3 is gated on the letter and wait above; no FWFN address is ever in a City changeset.
An offensive street name copied from the source Street names are reviewed per tile; "Squaw Bay Road" is held for the Nation's answer.
Community unaware This page, the forum thread, local mappers contacted directly, and a run name in every changeset comment.

Revert plan

As Toronto's: one changeset per run, tagged, so any run can be reverted with the JOSM Reverter. Uploads pause on any reasonable stop request from the forum thread, a local mapper or the Nation, within one business day. Good-faith reverts by local mappers are not contested.

Open questions for the community

  1. addr:city. Not written inside the city. Does the local community want addr:city=Thunder Bay?
  2. Monitoring. 90 days after the last bulk upload, as for Toronto?

References