Is there a way to assign a percentage for the margin which you are willing to play with for the run? IE +/- 1% or +/- .3 miles?
If you made this app with a "margin of error" option and an ability to export (as you already have) to 3rd party programs, then people would probably buy this app (android or iphone).
(if this program also would not force itself to use the whole road length... if it had some sort of ability to turn on or off the "use of entire road length for small legs of the journey" that would be a plus).
So, can you explain what you mean here? For the first item, I assume you are saying that if someone chooses +- 0.3 miles then the program would not return a result that was outside that range, correct? So if someone asks for a 10 mile route, they would get one between 9.7 and 10.3 miles, but not outside that range.
What is the second one, exactly? Not using the entire road length? I'm not sure exactly what you are suggesting, so can you explain it in a little more detail please?
I think it is clear enough what he is suggesting. When we enter a desired distance, we want to have routes generated that are close to that distance, not 50% off like they can be in some cases. His suggestion is that we can enter a range that the distance must be within, either as a percentage og as an absolute distance in miles or kilometers.
10 miles +-5% will generate routes between 9.5 and 10.5 miles in length.
10 miles +-1 mile will generate routes between 9 miles and 11 miles in length.
Yes, I understand the comment about a margin. It's the comment about using the whole road length that I don't understand.
At any rate, I added a margin into the OSM version of the code. If someone wants to take a look and see if it's behaving as you'd like I'd appreciate it. If it is, I can move it into the Google Maps version of the code as well.