TomTom 3 Calculation Errors

[jpfrost]

First I would like to say that TomTom 3 is the best PDA software I have ever purchased.

However, unless I have incorrect settings, I do believe their is something wrong with the routing engine. For example, if I calculate a route from
City: Collingtree(Northants.)
Street: A508
Crossing: A508 London Road

to:

City: Weston Turville
Street: Bedgrove HP21 9
Crossing: Anywhere

using STRICT i get a time of 1hr 7 mins

However if I set up an itinery to go through Stewkley Road, Soulbury (Buckinghamshire) i get a time of 1hr 5mins.

I realise this is only 2 mins but what is the point in checking 90000 roads if it cannot actually calculate the quickest route? And on longer distances/ other routes this time difference could be greater?

Anyone else seen this? Have I missed something?

[iancjc]

I think the problem is that strict is shortest rather than fastest.

Also for a routing program to check every possible combination of roads in a decent time you would need far more processing power than a pocket pc has (or will ever have).

The real point about sat nav is that the route given will get you to your destination (99.9% of the time with ttn2) without looking at maps or god forbid having to actually ask somebody the way.

No sat nav program will ever be as good as local knowledge (how many London black cabs have or their drivers need sat nav?).

Cheers

Ian

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!