Organised Editing/Activities/TrackViewer

Organisation	TrackViewer (https://trackviewer.cc)
Contact	TrackViewer, osm@trackviewer.cc
Changeset hashtag	#trackviewer
Timeframe	From November 2026, ongoing
Tools	The TrackViewer app (OSM API 0.6, OAuth 2). No other data sources.

What

TrackViewer is a GPS track app for cycling, MTB and hiking (iOS and Android) built on OpenStreetMap data. We are adding a small, opt-in way for our users to send back what they see on the trail. Every edit is made by the user, with their own OSM account (OAuth 2), never by a shared or bot account.

What users can send

• Notes (e.g. a closed path, a fence across a trail, a missing path) for local mappers to review.
• GPS traces of their own recordings, uploaded as "trackable", with the first and last 300 m cut off.
• Tags on existing paths and tracks, answering simple questions: surface, smoothness, tracktype, mtb:scale, sac_scale, trail_visibility, bicycle. Only on highway=path, footway, bridleway, cycleway, track, steps and minor roads; never on major roads.
• Simple points of interest: drinking water, spring, viewpoint, shelter, huts, bench, picnic table, toilets, bicycle repair station and parking, guidepost, information board, waste basket. Correcting a few of their tags or adding new ones.

No geometry editing: users cannot draw, move, split or delete anything. To add a missing path we upload the trace and open iD with it, so it is drawn with proper tools.

Safeguards

• Users must confirm they surveyed it on the ground; the app warns when they are far from the point. Changesets carry source=survey.
• Only data the user observed: nothing is copied from other maps or from our other sources.
• Before uploading, every element is read again from the API. If someone changed a tag since the user saw it, our change to that tag is skipped, never overwritten.
• Edits made offline are grouped into one changeset per upload, with a descriptive comment, created_by=TrackViewer x.y and hashtags=#trackviewer.
• Temporary conditions (mud, flooding, fallen trees) stay in our app and are not sent to OSM.

Review

We review changesets with the #trackviewer hashtag on OSMCha weekly during the first months and fix or revert problems ourselves. Report any issue to the contact above or by changeset comment; we answer within two working days.

Results

To be updated monthly.