ABRP incorrectly displays estimated times when clicking on a segment of a trip.
- Done
|
E |
Evan Williams |
ABRP incorrectly displays estimated times when clicking on a segment of a trip. See the following route as an example:
abetterrouteplanner.com/?plan_uuid=f32832d3-719d-415a-94e9-64713d2ac226
Trip calls for a drive from Moncton, NB Canada, ending just before the United States Border. This trip would require one supercharger stop in Quispamsis, NB Canada.
The actual times listed for the waypoints on the lefthand side of the website / iOS app appear to *correctly* reflect expected timeframes, I.E:
- Leaving Moncton @ 12PM.
- Arriving at the Quispamsis Supercharger @ 1:18PM.
- Leaving the Quispamsis Supercharger @ 1:52PM.
- Arriving at destination (just before Canada/US (Maine) border @ 3:09PM.
However, there seems to be an issue with time calculations if one clicks into a particular segment of a route displayed on the map.
For example, if I click on the route segment between Moncton and Quispamsis (but just before arriving at the Quispamsis supercharger, see the yellow circle in the first screenshot) it accurately reflects the time at that point in the route would be approx. 1:17PM time as one would expect. This is in line with the estimated arrival time displayed in the waypoints for the Quispamsis supercharger (circled in green in the first attached screenshot).
The thing is, after having stopped at the supercharger for ~29 minutes, you'd be hitting the road again at around 1:52PM. The weird thing is my second screenshot shows the second leg of the trip onwards (I.E. IMMEDIATELY after hitting the road from the Quispamsis supercharger mentioned above), it estimates that the time at that position along the route would be 4:25PM (circled in red, again in the second attached screenshot).
This makes no sense - telling me at that section of the route it would be 4:25PM, even though the final destination of the trip was (correctly) predicting for us to arrive at 3:09PM according to the final waypoint.
Any thoughts on this? It makes it difficult (other than using the time estimations displayed in waypoint overview) to precisely determine what the time would be at a particular point along a route.
Activity Newest / Oldest
Manuel_ABRP
Status changed to: Done
Manuel_ABRP
HI Evan, thanks for reporting these issues. I just fixed the time bug, it will be part of our next release.
Evan Williams
That’s awesome - thanks for the heads up!
Bo_ABRP
Status changed to: In progress
Bo_ABRP
The main bug - not being able to click a charger on the plan - is being fixed now and will be out in the next release. The incorrect time on the callout will also be fixed (or removed, as it is not very useful). Thanks for reporting!
Evan Williams
Ahh, that’s a bit disappointing if that’s going to be removed as opposed to fixed.
The feature was useful for determining where I’d be at a particular time. For example, if the generated supercharger waypoints were at 11PM and 1AM (but I wanted to stop for the night in a hotel around midnight), I could mouse over the map to see where I’d be at midnight and search for a hotel in that area.
Bo_ABRP
OK, we will aim to fix it!
Evan Williams
Third screenshot (where the date&time would manually be applied to origin waypoint seemingly being ignored in the time calculation).
Evan Williams
For what it’s worth, I just realized the time I’m referring to being incorrect seems to be generated in relation to the *CURRENT* time on the device you access ABRP from.
It’s like this feature (clicking at any point along the route to see what the time would be at that point) is operating as though you’re leaving right now and therefor based on the current time. This as opposed to the expected behaviour where you’d think ABRP would take into account the manually-applied date&time you’ve assigned one to the first (origin) waypoint.
That seems to be the nature of where this bug is coming from.