I am recording tracks during rides with my cycling group to eventually create a library of rides for tourists in and around Melbourne, Victoria, Australia. It would be good if Viking could snap waypoints and trackpoints to the nearest thoroughfare, be it a road, private road or drive, cycling path, etc. This would make it much easier to create route maps from the often inaccurate trackpoints and considerably redue hand editing.
I believe OSMR has an API that can be used to perform this function but, being a non-programmer, it is way beyond my capacity to understand and use it!
Oh yes, I second that request! In fact, I had planned to post something similar last weekend, but then the weather was just too nice... ;-)
I actually don't understand the coding details either, but I would imagine two possible implementations of this function. And if it was double-Christmas, both implemented for the user to chose ;-)
Manual Snap: The user moves a trackpoint (a) towards a road/trail/younameit (b) and, when (a) is getting closer than a certain distance from (b), it will automatically snap to (b) perpendicularly. This function could be checked / unchecked in the track submenu under "Track Snapping". Possibly, a snapping radius (that minimum distance from (b)) could be defined in metres or another useful measure under "Track Snapping - Snapping Configuration".
Auto-Snap: When clicked in the track submenu under "Track Snapping - Auto-Snap Track", Viking will attempt to snap all trackpoints (a_i) of a selected track perpendicularly to the nearest road/trail/younameit (b). Defining a snapping cutoff as the maximum distance an (a_i) is allowed to have from (b) to be snapped would be useful either.
Unfortunately, I can't offer much help aside from a German translation of menu entries and messages and discussing possible ideas and concepts for the implementation of the function. And I would be willing to donate some EUR worth of beer / coffee / pizza.
Cheers,
rooots
Last edit: rooots 2017-03-29
This issue is similar to #142. Sorry about that.
This feature will be tracked in #144.