Profiles keep back and forth detours via points #879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Otherwise some waypoints may not really be routed to (Brouter would remove
route sections that go forward and then backwards on the same ways).
This is visible with the Brouter service on Android, not in brouter-web.
The engine default used to be hard coded to 40 but was then set to 0 (disable)
in 901dd3a. This commit was then merged in c72fc5f (PR #764).
This change sets correctMisplacedViaPoints (set as the default: true) and
correctMisplacedViaPointsDistance as profile global parameters so that they
can be changed in an easy way by the user.
Should address issue #825.