Route Length?

I don't have a specific answer but my gut feeling is that any GPS would choke on a recalc of a 10k-mile route, especially if it was near the beginning. Do you have a compelling reason to make such a long route in one file?

For some thoughts on long-distance route planning (more like 4k miles), see:

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=119351

-dan

Dan,

It would be easier to just load one long route and ride without having to stop and put in a new one. I turned off recalculation on the 276. I hope the Zumo allows that.

I'm trying to find out if the Zumo has route length constraints and work within them.

Thanks for the info.

Len

Len,

Forgive me if I am misunderstanding, but are you saying you plan to drive 10,000 miles nonstop? If not, the zumo will hold lots of routes and switching to a new one each day is not much more trouble than booting up each morning. And I'd wager that the time from a cold start to ready to ride with smaller routes would be dramatically shorter.

I'd also worry about the zumo choking on such a big route during import, at which time it looks to me as if some recalc (or just plain calc) is happening regardless of how you set the zumo's recalc preferences.

Another thing to consider is how you might want to edit a route while on your trip, due to changes in weather, plans, etc. I shudder to think how the zumo would react if you tried to add or re-arrange waypoints in a 10k-mile route.

-dan

No we don't have plans of 10K days. You say the Zumo will choke on loading or recalculating long routes. I need to define "long" in Zumo speak so I don't create a problem. Will a 1K route work or is 500 miles better?

The 276C, worked with MapSource, had a limit on the number of internal waypoints a route could handle before it truncated. The internal waypoints are what the software needed to follow the roads and link the waypoints I entered. There was no way to keep a count on the internal waypoint. They depended on the complexity of the route. The route truncation message didn't show until an attempt was made to load the 276. Then is was back to the drawing board to make shorter routes the 276 could handle.

If I go off route, usually to find lodging, I have the GPS route us there then to return to the route I view the route and designate a waypoint to go to and intersect the route. At that point I reload the preplanned route.

Thanks for your advice.

Len

Happy to help.

Unfortunately I can't hang a number on it for you. I don't recall ever pre-planning more than about 500 miles give or take in any one segment.

In your lodging example, I'd be worried about trying that with a huge route.

I hope someone here can supply better examples and numbers.

-dan

Dan,

I've posted this question on other forums also. No one replied. I've sent off to Garmin's e-mail support. I'll let you know what I hear.

Len

Here's the reply from Garmin support:
"I]Dear Len Parkin,
Thank you for contacting Garmin International. I will be happy to help you.
There is not a hard limit on the length of routes when using Basecamp/Mapsource. The limit is the amount of memory used when calculating the route. I would suggest breaking your trip up in similar 1,000 mi or less "legs" like you did when using MapSource.
Please let me know if you have any other questions.[/I]"

In MapSource they have an indicator showing the MB's the selected maps are using. I'll suggest they incorporate the same type indicator for route size.

Len

In the Mac-BC Beta there was a Route length limit (1500miles) but that has been removed and v3.3.1 is back to supporting as long a route as you would like to make. :D

When you select the Route in it's List (or My Collection) the status bar at the bottom of the screen shows the Route Distance and Total Time.

Cheers,