Pilot evidence site · OSM community discussion · Wiki page · MIT licensed
The Toronto city checkout of the address-import family: the import
proposal and its evidence, Toronto's config.toml, and (locally, gitignored)
the living tool.db recording everything this import has pushed to OSM.
The pipeline itself — conflation, review UI, upload, maintenance — lives in
the engine repo, address-importer-friend,
which was forked from this repo on 2026-08-13 with full history. This repo
was then slimmed to the Toronto-specific remainder. Milestones of the import
are tagged here: import-start (2026-05-13), import-complete (2026-05-28),
maint-1 (2026-06), maint-2 (2026-07).
cd ../address-importer-friend
python run.py --city-dir ../toronto-2-address-import # dev sandbox
python run.py --city-dir ../toronto-2-address-import --prod # real OSMSetup (OAuth apps, .env.dev / .env.prod from the .example files) is
documented in the engine's README; the credential files and all working state
live here: config.toml, .env.*, data/toronto/tool.db, data/osm/
(the cached Ontario extract), tiles, and run caches.
| Stage | State |
|---|---|
| Draft proposal | Complete (last revised 2026-08-27 — declares the import continuously maintained) |
Wiki page (Toronto/Import/AddressPoints) |
Published 2026-05-01 |
| OSM Community Forum announcement | Posted 2026-05-01 — thread (tagged import; the Import Guidelines route announcements through the forum now, not the deprecated imports@ list) |
| 14-day feedback window | Closed 2026-05-15 (measured from wiki publication; discussion resolved) |
| Phase 1 pilot upload (production) | Completed 2026-05-13 — changeset 182585291 (tile high-park-swansea-sw-se, 176 uploaded, 72 skipped, 4 rejected) |
| Phases 2 + 3 (citywide rollout) | Completed 2026-05-28 — all 1,297 tiles processed; 1,297 changesets (182585291 … 183305851) on the skfd imports account; ~449k addresses uploaded, ~311k skipped (mostly already in OSM), ~9.2k operator-rejected. Day-by-day notes in blog.md. |
| Phase 4 — closeout | Completed 2026-08-26. Cumulative upload manifest published; the 90-day post-import monitoring window closed with no community-raised issues. |
| Phase 5 — continuous maintenance | Ongoing since 2026-06-05, no end date. 4 changesets, 103 addresses so far: maint-snap56 (183717565, 2026-06-05), maint-catchup-snap45-56 (183758255, 2026-06-06), maint-snap90 (186209651, 2026-07-23), maint-snap113 (188123936, 2026-08-28; 22 retirements deleted by hand). Account total 1,301 changesets. Run from the engine's maintenance page against this checkout. Batches are not individually announced on the forum thread — see § Continuous maintenance in the proposal. |
| Post-import follow-ups (separate proposals) | (a) source → addr:source tag rewrite. (b) MapRoulette challenge for ~1,580 OSM buildings with addr:housenumber but no street anchor. (c) Interpolation-cleanup mapping party — separate forum thread, organized by Toronto local mappers. Sketches live in the engine repo's future-work/. |
The Phase 5 row is the run-by-run ledger of record. The wiki proposal carries the rules and deliberately does not duplicate it: a changeset already publishes its own id, date and counts, so a table on that page could only be stale or retyped (proposal changelog, 2026-08-29). Add the run here when you close a month; paste the proposal onto the wiki when a rule changes.
Production uploads were made from the dedicated
skfd imports OSM
account (not the maintainer's personal account).
There is one living canonical tool.db (~2 GiB, data/toronto/tool.db,
gitignored): the pilot + citywide import plus every monthly-maintenance run
folded in — 1,300 runs, 768,927 candidates, 1,299 uploaded changesets, and
the full human-review record. It is published periodically as a dated,
credential-scrubbed release asset on this repo
(tool-db-<YYYYMMDD>.db.xz) via the /publish-db command.
gh release download tool-db-<YYYYMMDD>
xz -d tool-db-<YYYYMMDD>.db.xz
sqlite3 -readonly tool-db-<YYYYMMDD>.db \
"SELECT run_id, changeset_id FROM runs WHERE upload_status='uploaded' LIMIT 5;"- Toronto Open Data — "Address Points (Municipal) – Toronto One Address
Repository", published under the
Open Government Licence – Toronto.
Consumed indirectly via the sibling
ontario-address-changestracker. - OpenStreetMap — © OpenStreetMap contributors, ODbL.
MIT for everything in this repo (docs, config, pilot site).