Currently, alternate route choices are assessed purely on distance differences.
What is more realistic is to assess them by the probable time it would take you to run the alternate legs.
This is the 'go over the hill or around the hill', decision. The application has the elevations of the route points, so it should be fairly straightforward to factor this into the RouteChoiceScorer logic.
Currently, alternate route choices are assessed purely on distance differences.
What is more realistic is to assess them by the probable time it would take you to run the alternate legs.
This is the 'go over the hill or around the hill', decision. The application has the elevations of the route points, so it should be fairly straightforward to factor this into the RouteChoiceScorer logic.