Tools that compare what the City of Guelph publishes against what OpenStreetMap already knows — and hand mappers the difference, in the editor, where the work actually happens.
Guelph is not a blank map. The gap is rarely the features; it is almost always the attributes.
Tile layers you add to iD or JOSM as a background, each with a gap page listing what OSM is missing, misnaming, or leaving unnamed.
|
guelph-parks-layer 126 City parks against OSM · gaps · code100 match cleanly · 16 missing · 7 named differently · 3 unnamed in OSM |
More in progress: pitches, transit stops, stormwater basins, bike facilities, truck routes, trails, community gardens. |
Where the City data itself needs judgment — placeholder points, stale rows, records that were never real — a layer is not enough. These keep a per-record history and somewhere to write down what a human decided.
guelph-address-import — continuous gap-fill and QA over Guelph's completed 2025 address import · guelph-pitches-beholder — 191 courts and sports fields, 162 of them unnamed in OSM
guelph-boundaries — BIA and neighbourhood boundaries, with the Overpass queries behind them
Nothing here is bulk-imported. Every layer is compared against OSM first, and where OSM already has the object, the City data is a reference — it goes in front of a mapper, not into the database. Edits are made by people, one at a time, under the OSM import guidelines and automated edits code of conduct.
Not affiliated with the City of Guelph. Source data is the City's open data, used under its licence:
Contains information licensed under the Open Government Licence – City of Guelph.
Maintained by @skfd · OSM user skfd
