Rip
Well-known member
- Thread starter
- #1
After reading a lot of good stuff in these forums, I got a dongle and sprang for ABRP Pro. I like it, but I have a couple of observations. One, I would like it even better if it had some method for pulling all my saved destinations from Google Maps. Two, I have noticed that its initial time-to-destination estimates always turn out to be pretty optimistic. I thought it was just my imagination. After using Google Maps for years, I had always been impressed by how precise the arrival estimates turned out to be. With ABRP, it seems that every time, I watch the arrival time slowly tick up.
I thought I would check it this morning. I had a 57-mile drive this morning from Southwest Harbor, ME to Bangor, ME. When I entered the destination, Google Maps said I would arrive at 10:39. ABRP said I'd be there at 10:22. Sure enough, by the time I had left the island it was up to 10:28. I finally arrived at (you guessed it) 10:39 on the dot. Now, I recognize that this is only one actual recorded data point, but I intend to run this test every time I go somewhere for the next few weeks, to see if the difference is consistent.
It makes a difference if you need to be somewhere at a certain time. The uncertainty is always going to grow with distance, but a 17-minute error over 60 miles might mean a late arrival or missed appointment. I have to think that maybe ABRP doesn't have all the near-real-time updates to traffic, construction, etc., or they are not figured into the calculations in the algorithm. Anyone else seen this difference?
I thought I would check it this morning. I had a 57-mile drive this morning from Southwest Harbor, ME to Bangor, ME. When I entered the destination, Google Maps said I would arrive at 10:39. ABRP said I'd be there at 10:22. Sure enough, by the time I had left the island it was up to 10:28. I finally arrived at (you guessed it) 10:39 on the dot. Now, I recognize that this is only one actual recorded data point, but I intend to run this test every time I go somewhere for the next few weeks, to see if the difference is consistent.
It makes a difference if you need to be somewhere at a certain time. The uncertainty is always going to grow with distance, but a 17-minute error over 60 miles might mean a late arrival or missed appointment. I have to think that maybe ABRP doesn't have all the near-real-time updates to traffic, construction, etc., or they are not figured into the calculations in the algorithm. Anyone else seen this difference?
Sponsored