RoundTrip
Gathering feedback
Hello.
Does Locus Map has a RunTrip-Function ( similar Garmin RoundTrip ) or is something like that planned ?
THX
Christian
Hello.
Does Locus Map has a RunTrip-Function ( similar Garmin RoundTrip ) or is something like that planned ?
THX
Christian
I like this idea 
Good day Christian,
currently as I know, BRouter ( main offline router ) does not support this feature. Because Locus Map does not have own routing system, it more depend on 3rd party solutions, which probably currently does not exists. Anyway I also find such tool useful for riding in unknown terrain or just for fun. So maybe number of votes may convince developer of BRouter to implement such feature on it's side ( so we will be able to implement this in Locus as well ).
Good day Christian,
currently as I know, BRouter ( main offline router ) does not support this feature. Because Locus Map does not have own routing system, it more depend on 3rd party solutions, which probably currently does not exists. Anyway I also find such tool useful for riding in unknown terrain or just for fun. So maybe number of votes may convince developer of BRouter to implement such feature on it's side ( so we will be able to implement this in Locus as well ).
I do not personally know the Garmin and its features. I just guess a user chooses the same start and destinations and the target route length, with given or implied tolerance.
But I expect such high level features are supposed to be implemented at high level software solutions. I.e. either web-applications serving as route planners, either local front end applications offering route planning. The back end routing services ( online or offline ) just generate route points between provided points.
But asking Arndt ( the Brouter author ) is free,
For LocusMap + BRouter combination, there is disadvantage they are not integrated at data level, so LocusMap cannot easily suggest automatically chosen viapoints to shoot trial routing to meet the target length.
One crazy idea would be to estimate the turning point in distance cca 1/3 of total target route lengths and shooting random routes to this 1/3 circle there and back, avoiding the same route back.
One realistic manual idea is to choose such a 1/3 turning point manually, looking at map, together with 1 viapoint there and 1 back..
I do not personally know the Garmin and its features. I just guess a user chooses the same start and destinations and the target route length, with given or implied tolerance.
But I expect such high level features are supposed to be implemented at high level software solutions. I.e. either web-applications serving as route planners, either local front end applications offering route planning. The back end routing services ( online or offline ) just generate route points between provided points.
But asking Arndt ( the Brouter author ) is free,
For LocusMap + BRouter combination, there is disadvantage they are not integrated at data level, so LocusMap cannot easily suggest automatically chosen viapoints to shoot trial routing to meet the target length.
One crazy idea would be to estimate the turning point in distance cca 1/3 of total target route lengths and shooting random routes to this 1/3 circle there and back, avoiding the same route back.
One realistic manual idea is to choose such a 1/3 turning point manually, looking at map, together with 1 viapoint there and 1 back..
What I see as a possible algorithmic way to suggest for a BRouter, is providing a viapoint set not in viapoint meaning, but as potential points of interest. BRouter could then perform something similar as the Salesman problem. Diference would be, not visiting all points, but visit as many points as possible before returning home, not to break the max route limit.
The distinguishing between standard multiviapoint route and Salesman-like round trip could be the diferent or the same start and destination point.
The route limit could be implied as the 3 times air distance to the farthest point.
I have raised the reformulated suggestion at BRouter discussion group/maillist at Google groups.
What I see as a possible algorithmic way to suggest for a BRouter, is providing a viapoint set not in viapoint meaning, but as potential points of interest. BRouter could then perform something similar as the Salesman problem. Diference would be, not visiting all points, but visit as many points as possible before returning home, not to break the max route limit.
The distinguishing between standard multiviapoint route and Salesman-like round trip could be the diferent or the same start and destination point.
The route limit could be implied as the 3 times air distance to the farthest point.
I have raised the reformulated suggestion at BRouter discussion group/maillist at Google groups.
Replies have been locked on this page!