ETA in NL wrong in the daytime
iMark
Posts: 13 [Master Explorer]
This weekend we made two longer trips in the daytime in NL. The ETA's our GO 5100 gave were off quite a bit. Both times about 15 mins. This seems to be a problem when driving in the daytime when there's a blanket speed limit of 100 km/h in NL and the route planned is mainly on motorways that used to have a 120 or 130 km/h speed limit. Our GO 5100 does know all the speed limits.
It's very irritating to see the ETA creep up by a minute at the time during the journey and you arrive about 15 mins later than originally predicted.
Interestingly when you plan a trip on the My Drive Connect website you get a clear difference between day and night of about 15 mins for the trips we made this weekend.
It's very irritating to see the ETA creep up by a minute at the time during the journey and you arrive about 15 mins later than originally predicted.
Interestingly when you plan a trip on the My Drive Connect website you get a clear difference between day and night of about 15 mins for the trips we made this weekend.
0
Comments
Would you wish to share some information about the routes where you noticed this behaviour?
Perhaps we can forward that to our team to test and see what improvements are needed.
Thank you, Vikram
It is the normal way of calculating the ETA when you know the maximum speed. This problem is existing for a couple of months now!! Can anyone from TOMTOM look at it? It is very annoying!!
Or is this forum of discussions only for ventilating some grief?..... Thank you
We had this problem back in August. We drove from Dutch postcode 1251 RE to 9922 PJ. Planning in our TomTom 5100 gives a journey time of 1u47 mins. The actual journey time was 2h03.
What's really strange is that planning the journey on the TomTom website calculates according to the time of day. Here are two screenshots for the journey, one for departure at 20:00 and another one for leaving at 09:00.
I hope there will be fixed soon. The current situation is really annoying when driving longer journeys.
You would think it's not so difficult to correct when there's a blanket speed limit of 100 km/h in a whole country.
I would actually prefer to have correct data in the daytime and have early arrivals when driving between 19:00 and 07:00.
Superusers
This IQR data that is used on the online route planner might be more up to date than the one used in the PNDs.
I had the same issue on Nov 11th. I looked the evening before and it calculated for my route approx 1h. I was in startled the next morning when I started my journey and it said that the same route would last 1h15 and I would thus be too late.
Strange that it would miscalculate on a public holiday. If the IQR is to blame, it would a rather stupid algorithm when it doesn't take public holidays into account.
When will this be fixed?
Cheers,
Eddy
Superusers
If that's indeed the case, one gets not only the incorrect ETA, but also the routes are not calculated correctly. I was already wondering why the app sent me in my way back via these alternative route saying that would be the fastest route. Since it was a public holiday, there were to delays/traffic jams at all, so the normal route would have suited very fine.
Looking at the promo, it says "IQ Routes is the smart and efficient way to calculate routes ... This results in a faster route, and saves you money by significantly reducing travel time and fuel usage. ... whether you are traveling on a weekday or at the weekend."
It doesn't seem to be that smart nor efficient and it doesn't travel time.
Very disappointing.
Superusers
Perhaps a suggestion for improvement for TomTom
Superusers
I think we should, at the least, have a menu option to turn off IQ Routes like on the NAV3 devices....
During the 1st Covid-19 shutdown here in the UK the roads were more or less deserted....
On the days we did venture out... My GO 6200 was reporting ghost traffic queues....
Stay Safe... ATB YFM
Interesting news article, about Google and traffic in covid-19 times.
"As we saw with COVID-19, unprecedented events can drastically disrupt traffic patterns and throw off prediction models. Google saw up to a 50 percent decrease in worldwide traffic when lockdowns started early this year. The sudden change forced Google Maps to be more agile. It began prioritizing historical traffic patterns from the last two to four weeks and deprioritizing older patterns."
www.engadget.com/amp/google-maps-deep-mind-ai-accuracy-140005698.html
Superusers
@SteveFJR
I had a Ga*m*n once for a month
Stay Safe... ATB YFM
The penultimate point is really interesting. In order to prepare for your trips please download the new version of the map because it will calculate routes with new (ahem) speed limits in the daytime.
The other thing that I don't understand is that TomTom doesn't fix this obvious flaw for a situation in their home country! I'm sure people working at TomTom in Amsterdam must have encountered this annoying bug.
Superusers
Superusers
My suggestion is to do the calculations the other way round. Do them based on the 100km/h speed limit with correct ETA's in the daytime.
For travel at night you would then get ETA's that would give you early arrivals. Much less of a problem than late arrivals in the daytime.
On all three trips the ETAs were pretty accurate while driving at 100km/h. I don't know what has been fixed but it's definitely working properly again.
Still disappointing that nobody from TomTom ever replied in this thread since @VikramK 's comment on 24 September. That's now almost three months ago.
Superusers
I guess, as stated several times above....
The IQ route data, simply caught up with reality....
Stay Safe... ATB YFM
Is that also the case with eg public holiday and routes will be calculated on reality instead of IQ routes thinking that it isn't a public holiday?