edgarw Posted October 18, 2021 Share Posted October 18, 2021 (edited) Description: Once I add a guidepoint to a route, it's arrival time slips by e.g. 53 minutes Type: Webpage, App (4.0.57, Android) Link to Plan: https://abetterrouteplanner.com/?plan_uuid=dd27c387-688b-4516-a21f-6b99e081f31f Replication Steps: choose random car chose random start- and endpoint (close enough so no recharge is needed, same with recharges though set start time to 00:00 set a guidepoint (not waypoint) somewhere on the expected route calculate route find that arrival time calculated is later than start time plus calculated travel time In my exaple, travel time is 1h28m, start time is 00:00 (12:00 AM), arrival time is 02:21 AM though. So magically, 53 minutes are added * With a waypoint rather than a guidpoint added, arrival time is correctly calculated as 01:28 AM https://abetterrouteplanner.com/?plan_uuid=b8ba9562-ea98-49e5-956e-129f2aefd4e5 * With NO waypoint nor guidepoint added, arrival time is correctly calculated as 01:26 AM (the detour on the service station for guide- and waypoint is calculated with 2 minutes loss it seems, which is not a problem, of course). https://abetterrouteplanner.com/?plan_uuid=dd940bbd-97c3-4da3-bca1-d65d2ae051a0 Guidepoints are points to have a preferred route being routed through, stops are not intended. For a planned stop, I'd be using a waypoint rather than a guidepoint and add a specific planned stop time. I'm sure this is a bug rather than a feature. Seen this for a long time, so I decided to post it here, because it always makes calculations difficult, when I use guidepoints. Edited October 18, 2021 by edgarw Link to comment Share on other sites More sharing options...
khorton Posted October 19, 2021 Share Posted October 19, 2021 Interesting! I see the same very strange behavior. Thanks for alerting us to this issue, while we wait for it to be fixed 1 Link to comment Share on other sites More sharing options...
edgarw Posted October 31, 2021 Author Share Posted October 31, 2021 Found the reason: Left (first) pic, using a guide point: ABRP uses the full time until the next charging stop (or way point) to be displayed as the time from the previous point to the guide point. Then ist adds the time from the guide point to the next stop another time. In my example, it's 1h28m from Hamburg to Hanover in total, but calculated as the time needed from Hamburg to Bispingen (guide point). Then, the calculated time from Bispingen to Hanover is calculated once again and added to the arival time. On the right (second), a way point is used instead, resulting in the first time from Hamburg to Bispingen to be calculated correctly (35min rather than the full 1h28m), thus the correct times for arrival are calculated here. Unfortunately, the ABRP team doesn't seem to have picked up on this topic yet. But I see the reason, as they're busy with the redesign (which mostly, I like). Link to comment Share on other sites More sharing options...
Samuel-ABRP Posted October 31, 2021 Share Posted October 31, 2021 Thanks for your detailed analysis, we'll have a look at it. 1 Link to comment Share on other sites More sharing options...
edgarw Posted October 31, 2021 Author Share Posted October 31, 2021 Great @Samuel-ABRP Link to comment Share on other sites More sharing options...
PhilS Posted December 6, 2021 Share Posted December 6, 2021 Just wanted to add that I'm also seeing this problem. Link to comment Share on other sites More sharing options...
