Organised Editing/Activities/GetIt.
Rationale
GetIt. is a location-based reminder app. Users save places that matter to them personally, and some of those places are not yet on OpenStreetMap. This activity offers those places to OSM: a name the user typed themselves, a point they tapped themselves, and a category they chose, each one reviewed by a person before it goes anywhere. Volume is low and the intent is narrow, filling gaps in places our users already know first-hand.
Contact
LogicMind, the developer of the GetIt. app.
- Email: support@logicmind.com
- OSM account: LogicMind (on OSM · edits · contribs · heatmap · comments)
Changeset comments on this account are monitored, and we will respond there.
Community consultation
Before the first upload, a heads-up thread is posted for each region in scope on community.openstreetmap.org, explaining what will be added and how.
We will respond to questions on these threads and to comments on our changesets.
Hashtag
- getit, included in every changeset comment, so this activity can be tracked in OSMCha and similar tools.
Timeframe
Starting 2026-08-18. Ongoing, with no planned end date. Small batches, at most one changeset per review session.
Tools and data sources
Tools:
- An internal, localhost-only review dashboard that queues contributions, checks them against existing OSM data, and prepares nodes.
- JOSM, driven through remote control, for the actual edit. Every upload is performed by a person.
- Uploads carry
created_by,source=local knowledge, and a link to this page.
Data sources:
- The place name typed by the app user, and the coordinate they tapped, contributed from their own personal experience. The app asks each contributor to confirm this immediately before the contribution is made.
- A category the user selects from a fixed list of OSM tags.
- Standard OSM background imagery, used only to sanity-check a position before upload.
Contributors are never identified, in the data, in changeset comments, or in notes.
Participants
Measuring our success
- Nodes uploaded, tracked through #getit and the account's changeset history.
- How many contributed places turn out to already exist in OSM, which tells us how well-mapped our users' areas already are.
- Community feedback on changesets and on the consultation threads. Sustained objections would stop the activity.
Training/instructions
The activity is currently run by one operator following a written internal runbook. The workflow is enforced by the dashboard rather than by memory: only categories the pipeline supports can be selected, duplicate checks run before anything is batched, and the contributor's own POI name and coordinates are what we upload. A reviewer may correct a name that is unsuitable for the map, a personal note rather than the name on the sign; the original is kept and recorded against the contribution, and anything that is not plainly the same place is rejected instead.
Post-event clean-up
- Every contribution is reviewed by a person before upload. Nothing is uploaded automatically.
- Each one is checked against existing OSM data, by proximity and by name, plus a live check against the API at review time, so anything already mapped is dropped rather than duplicated.
- Positions are verified against imagery before upload.
- Anything we cannot verify is filed as a public OSM note for local mappers instead of being edited directly.
- If the community flags a problem, we will respond and revert.
Results
Progress and any issues are shared on the consultation threads and are available on request by email. Changeset comments are the primary channel and are monitored.