Quest - Route Truncated problem

Joe Bar

Too old to die young.
UKGSer Subscriber
Joined
Mar 28, 2006
Messages
558
Reaction score
73
Location
Not far away.
Hi, I'm looking for some help with a recently bought Quest.

I have loaded the street detail maps of UK and Northern France, total 200mb. I have a route I'm taking through France, using hotels and stop off points as waypoints.

I downloaded this to the unit no problem. I then realised that the route had automatically taken me down the motorways. I changed the preferences, recalculated the route and saved it.

I then deleted the motorway route off the Quest and tried to re-load the re-calculated non motorway route onto the Quest, but at 71% transfer it shows an error message "Route Truncated" and the last section of my route is missing.


I have reduced the amount of street detail area on the unit, and re-tried but the same message comes up at the same point of transfer.

Any help gratefully received. Thanks.
 
Does the recalculated route on the pc take you outside the map areas you transferred to the Quest, even a very small section? Maybe try reloading the map data by selecting maps around the route (right click the route, then 'Select Maps Around Route')

Andy.
 
metro said:
Does the recalculated route on the pc take you outside the map areas you transferred to the Quest, even a very small section? Maybe try reloading the map data by selecting maps around the route (right click the route, then 'Select Maps Around Route')

Andy.

No, the route doesn't take me outside the map areas.

I have also re-loaded the map data around the route as suggested, but the problem remains. If I re-calculate the route to take in the Motorways, it loads up no problem.

After messing for an hour, I read the manual but can't find a reference to the message.
 
Have found a few possible reasons...

One

Two #42

Three page 2

Page 61 of the 2610 manual says : Route Truncated - The route has been truncated because it was too long. There are turns missing prior to the destination.

They don't necessarily relate specifically to the Quest, but all refer to problems with waypoints and truncated routes.

Andy.
 
metro said:
Have found a few possible reasons...

One

Two #42

Three page 2

Page 61 of the 2610 manual says : Route Truncated - The route has been truncated because it was too long. There are turns missing prior to the destination.

They don't necessarily relate specifically to the Quest, but all refer to problems with waypoints and truncated routes.

Andy.

Thanks for your efforts Andy, I'll take a more detailed look at those links and have another play.

Cheers.
 
No probs, thinking about again, is your route one big route around France - in which case try splitting it into sections. I can't remember if I got the same message, but for some reason ended up splitting a single 3000mile route into shorter sections last year (on the 2610). This also made it more flexible - I split the route into the daily legs. Maybe the non-motorway route is a bit longer (in terms of turns in the route, more likely off-motorway) and pushes the route over the edge, so to speak?

Andy.
 
There seems to be several undocumented limitations of the number & size of routes that can be stored in the unit. These limitations are very different for different units.

- Limited number of routes.
- Limited number of waypoints in a route.
- Limited number of routewaypoints in a route.
- Limited total length of all routes.
- Limited total number of routewaypoints.
- etc.

The memory requirement for routes is also extremely dependent on what country they are in. Example - in an SP3 you can only fit in 15 half-day routes running in Italy but over 45 similar routes if running in Sweden. I don't know why this difference but I guess it has to do with how the map is vectorized.

A few days ago I e-mailed 29 half-day routes in France to a friend with a Quest2. He could only load 24 of them before he got the message "Roadwaypoint memory full". All 29 routes fits into my 276C without problem.

Maybe Pan knows more about this?
 
metro said:
No probs, thinking about again, is your route one big route around France - in which case try splitting it into sections. I can't remember if I got the same message, but for some reason ended up splitting a single 3000mile route into shorter sections last year (on the 2610). This also made it more flexible - I split the route into the daily legs. Maybe the non-motorway route is a bit longer (in terms of turns in the route, more likely off-motorway) and pushes the route over the edge, so to speak?

Andy.
I remember seeing a similar problem with my SP3. I got the feeling that it was the longest route that decided how much memory each route required. Thus one very long route and several short routes would be very inefficient while many medium length routes would be better.

I don't know if this is true - just got that feeling and I never dug deeper into it. All problems with waypoint, route and track sizes disappeared when I upgraded to a 276C. ;)
 
Route too long?

I found this in a FAQ here http://www.gpsinformation.us/quest/questrev.html.

Then exactly how do you figure out how many "turns" can be in one route? Garmin says: There is not a limit to the number of turns per se. Along a route -- there are several types of points that are "dropped". The first being via points. The second are "guidance points" - where a user basically has to make a decision on which way to go (keep left, etc.), and the third are "nodes". Nodes are dropped along a route every time a road classification, name change, turn, etc.... There are a max of 1200 "nodes". If you are creating a route along an interstate, there won't be very many "nodes" dropped, because all the attributes of the road stay the same (for the most part). But, once you begin adding in lots of via points, where the detail of the map gets very complex, then there are more and more "nodes" dropped. "Nodes" are not seen by the user. Basically, they do show up if a person were writing third party software and sucks out the Position data, but that is the only place a user would see it.

HTH
TC
 


Back
Top Bottom