Prefer forward driving by active route re-calculation.

0709 shared this idea 7 days ago
Collecting votes

Add neglected return order to a 'penalty counter" into the reverse (shorter) drive direction.

Ignoring (multiple) return suggestions so promotes the (alternative) forward (longer) path.

My (cycling) settings: Alert distance: 75m. Recalculation distance: 100m.

Comments (7)

photo
1

Good day Willy,

we probably talk mainly about BRouter right? In case, there is any recalculation, Locus has the only option: specify to BRouter current users direction and also how long (in seconds), the user should stay in the current direction.

Current Locus Map has defined 3 seconds. From your personal experience, this time is too short?

In case of GraphHopper, there is only an option of "users direction", not the time.

photo
1

Are you really sure, because I can influence the start time of recalculation be the recalculation distance using brouter.

photo
1

May you describe more in detail what you wrote please?

To be true, I'm also not perfectly sure what Willy wants.

In case, I ride in the certain direction, which is for some reason out of originally planned route, what else should be important to me except parameter "how much time I need till I will be able to react on new computed instructions"?

photo
1

Ok I'll try to explain. See my settings. After deviating from the proposed route (for whatever reason) Locus generates multiple return commands until an alternative (shorter) new route path is generated. When ignoring (for whatever reason) "multiple" such returns commands Locus should fastly 'learn' and prefer route generation into the forward (driving) direction even when this results into longer total path distance. At least if a correct alternative path into the forward driving direction is available. By adding a penalizing (counter) system at the return path route generation, each time a successive return order is generated. So still at least a single return command is normally generated. So a (forward) alternative (even when longer) route so fastly becomes more and more favorised. Roger?

photo
1

Hmm roger, finally understand and agree it may be useful.

I also personally remember an experience, when riding a different path by intent and have to listen "recalculation success" every few seconds until routing decided that it will be better forward.

But I have absolutely no idea how to do this ...

photo
1

I am not really sure, I used for many years Brouter with Osmand. But it seems to me, that Brouter reacts different to loosing the intended route in this two apps. It is in the most cases in the first attempt a going forward solution in Osmand, in Locus it is mainly a going back solution.

photo
1

Okido, I do understand Menion.

By using only external routing sources, indeed probably not a simple task.

Keeping at least ONE single out of track alert before a new recalculation(s) occurs does warn a (distracted) user(s). I got inspired by some concurrent (routable maps) (auto)(cycle) gps nav softwares.

Anyway I prefer the Locus navigation compact discrete loud and clear tone commands ;-)

Compare by example video: https://youtu.be/LgOroLaG4Xw

Alternative path is short deviation, so here Locus generates limited number of track alerts and "return" recalcultion(s) result.

photo