You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2023. It is now read-only.
MTB single-track paths often make tight turns, especially when going up hills.
These are smoothed out by the Slide algorithm.
A possible solution would be to vary the tightness of the fit when the road is pre-defined. The algorhytm parameters could differ for a footpath, a residential road and a highway.
The text was updated successfully, but these errors were encountered:
Yes, this is definitely a problem I'd like to solve. It does tend to cut corners a bit in a general. I've tried messing with the parameters, but nothing has really worked. I'd like to aggregate direction from the Strava data to have that help the algorithm, but that is kind of a big project.
Forgot to mention, you can mess with the parameters here http://labs.strava.com/slide/google.html If you find something better, or better for specific cases, let me know.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
MTB single-track paths often make tight turns, especially when going up hills.
These are smoothed out by the Slide algorithm.
A possible solution would be to vary the tightness of the fit when the road is pre-defined. The algorhytm parameters could differ for a footpath, a residential road and a highway.
The text was updated successfully, but these errors were encountered: