So doesn't the drawn route follow the road exactly?

squid

Well-known member
UKGSer Subscriber
Joined
Jul 3, 2007
Messages
4,310
Reaction score
3,163
Location
north staffs
I thought at first this was related to using 2008 on my Quest1 but having looked closely at a route on mapsource it doesn't accurately follow the path of the road?

Showed up after the Quest displayed an error when testing a loaded route by saying 'rute does not match map, would you like to re-calculate.

If you say yes it comes up with a silly route.

The weird thing is when I highlighted the route and did a re-cal it appeared to come out more accurate the next time?

I have both V9 and 2008 on the PC but use 2008 as default and its a new route on a new file so I don't think I've mixed the two?

Edit. I'm running 13.7 if I recall. I removed the later verion as it wouldn't run O/S maps.
 
Different map versions - in computer - in the Quest unit
IMHO

Sounds right to me, maybe there's a wrong version map tile in that's burgering things up :nenau

Saying that, mu zumo occasionally throws a wobbly, especially up by Tebay, but that might have something to do with the physical location.
 
Quite possibly different map versions, that's most likely, but also make sure that you haven't got a via point dotted in on the wrong side of a dual carriageway for example.....that can cause all sorts of funny effects when calculating a route :)
 
The Quest says the map is 2008 as does the saved file when I re-open it in mapsource.

I've re-set the defaults in the Quest too but the problem is deffinately from mapsource prior to the transfer.


The route strays from the road in many places so its as if there are two layers.

I wonder if having both sets of mapping on the PC is causing an issue. That or when I removed the later version of mapsource and put 6.13.7 back.

I did this via a system restore due to the complications of removing the later version.

I'll re enter the routes and see if it does it again.
 
Are you 100% sure you have downloaded every mapset that you need for the downloaded route? :nenau

Yeah, the ones required are on there plus those all around too.

The problem is from mapsource though as I can clearly see where the track wonders off line from the roads.
 
I have used Mapsource 6.15.4 for some time and have just upgraded to 6.15.6. I have never had a problem with 15.4, too early to tell with 15.6. I also use 2008 maps as well as OS maps. The OS maps suggest you use your Quest for off road stuff some times. You haven't left Mapsource set to "Direct Route" rather than "Auto", have you? (Edit-Preferences-Routing). Similarly, the Quest may need to be switched back to "Road Lock" (Menu-Settings-Map Setup-Map tab). Just a guess. If not, I'd go to latest version of Mapsource and reload mapset to unit. Have you kept your unit software up to date? I'm on version 4.1...not sure if there's a more recent version. Must check.
 
The problem is from mapsource though as I can clearly see where the track wonders off line from the roads.

In Mapsource when you see a part of the route thats not on the road zoom right in on it. Is it still off the road and if so by how much, a few metres or 100 metres or more?
 
In Mapsource when you see a part of the route thats not on the road zoom right in on it. Is it still off the road and if so by how much, a few metres or 100 metres or more?

I would say it was out by 50m or more in places and others it was bang on for a mile then would take another wander.

I've gone through all 8 routes in the file now and done a re-calculate. They all appear to be correct when zoomed in this time. Transfered again and the Quest will navigate on indoor use without the previous error.

I don't know what the heck it was all about but had I not tested a route I'd have been stuffed once I'd got over the channel:confused:
 
Just thought, I might have opened a file someone else had sent to me at some point during creating my file. Whether that was from an older version but I'm fairly sure I re-opened my own file rather than adding data to theirs.

I'll be checking carefully for the same error in future.
 


Back
Top Bottom