Stop added after previous occurence of same stop
Not sure whether this is a Bug or should be framed as a Feature Request.
ABRP does some effort to intelligently add a stop into the itinerary, which often works quite well. (e.g., if a stop D is added to a plan A → B → C I add a stop D, this might result in A → D → B → C if D is “between” A and B).
However, this does not work well if a stop is added a second time that is already present in the plan. For example if I want to plan my way to work and back, because I need to charge at some time during the day, but don’t care if on the way to or from work, the following happens:
Original plan: Home → Work
Actual state after adding “Home” a second time: Home → Home → Work
Desired state after adding “Home” a second time: Home → Work → Home
This might be sensible, since the actual result is probably the shortest route including “Home” twice and “Work” once, but I was wandering how often people would really want to drive 0 distance between stops and if it might be an option to push a duplicate stop to the end automatically?
Thanks for the support!
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments2
ABRP User #6560
Jun 9, 2025
You should prevent the same waypoint from being entered into the route by ABRP directly one after the other.
It should still be possible to drive to the same waypoint two or more times, but not directly one after the other, but only with one or more other waypoints in between.
Bo (ABRP)
Jun 9, 2025
Thanks for the detailed proposal! Agree we should not add the same waypoint twice - we will look into it and try to improve the behavior.