Calculation Method on SPIII

What calculation method do U use on the SPIII & why?

  • Quickest Calculation

    Votes: 1 14.3%
  • Quick Calculation

    Votes: 1 14.3%
  • Better Route

    Votes: 0 0.0%
  • Best Route

    Votes: 3 42.9%
  • I havent a clue wot UR talking about!

    Votes: 2 28.6%

  • Total voters
    7
  • Poll closed .
I can only assume this is a software upgrade since I sold mine? Options were only 'Quickest'; 'Shortest' or 'Off Road (or something like that - straight line basically) when I had mine...

Mike:confused:
 
Obvoiusly you didn't play with it enough Mike!!
In routing options you can select one of the above

I haven't found a lot of difference to be honest BTBR if you select best it still does stupid things like going down an off ramp to come back up the on ramp 'cos thats marginally shorter than using the motorway.
Still, for all its little idiosincrossies (that cant be right!) its still better than a map by a long way
Sherps;)
 
i have to use quickest other wise it takes too long.

I assume you mean to re-calculate after you've gone off route ?

i find my sp3 is a bit slow in the city, you've gone the wrong way before its told you - or you've lost reception etc.
Open roads are great

overall its a good thing, i just find it a bit too slow.
 
Mike O said:
I can only assume this is a software upgrade since I sold mine? Options were only 'Quickest'; 'Shortest' or 'Off Road (or something like that - straight line basically) when I had mine...

Mike:confused:

I think that that is Route Preference, btbr refers to Calculation Method

Greg
 
I used "best" when I first got the unit but i found that it took an age to calculate. It would also route up green lanes etc. . Which was fun on a road bike.
I changed to using "quick" which is far quicker and better.
 
Sherps:

If the GPSR sends you down a ramp, then back up the same ramp again, that's a continuity error in the cartography - there is an unwanted break (perhaps only an inch long, so to speak, but a break nonetheless) in the electronic depiction of the roadway.

If you are running the latest version of the cartography (version 6 of CN, CS, or MetroGuide), then send a bug report into Garmin and they will pass it on to Navteq so it is fixed in the next release. The easiest way to document map defects like this is to make a file with MapSource that has two waypoints on either side of the defect, and a route between the two waypoints that illustrates the defect. The waypoints only need to be a few hundred feet either side of the defect.

It seems that a few of these get into every release. My private theory is that they happen when the cartographer assembling the data sneezes, or something like that, and their cursor jumps... :D

PanEuropean
 
PanEuropean said:
Sherps:

then send a bug report into Garmin and they will pass it on to Navteq so it is fixed in the next release.

Yeah! I've done this a few times......didn't get offered a free update to v6. Good job too because the things I sent them had not been corrected!!!
 


Back
Top Bottom